Arc,
Twisted Core has just the basic
stuff. They broke the extra functionality
out into separate packages a looong time
ago.
Complaining about something one doesn't
understand makes little sense, IMO.
I ended up going back to twisted 1.3. The threadedselectreactor in 2.2 just wont play nice (the interleaved iterator blocks randomly, forever), and is the only documented way to get interaction with my own event loop.
Just thought I'd interject: twisted doesn't suck. Write your own darn framework, sure. But making something as powerful as twisted in python is going to be hard - you will fail.
Also, it's a bold (and ignorant) statement to say twisted sucks considering it's been used in simulations software by NASA, RFID-tracking applications, and (ahem) has been chosen as the new default web server for zope3 - something entirely unrelated to Twisted (which evidences just how generalized it is). I might respect your opinion if you just said: "I don't have time to grok twisted.", or "I'm a doze programmer, and Twisted's reactor is too slow on doze." Well ... take back the doze programmer thing - that's hard to respect.
Don't worry, I hated twisted before too - in my younger days. You'll learn eventually that your "awesome" framework only does a subset of what twisted can do for you, only better ;)
Yeah socket is available on all platforms, but behaves differently in various circumstances on win32 and unix. Hence the need for another layer of abstraction, to provide a common behavior.
it's good more people are starting to understand that having code for interacting with newsgroups and irc is not needed for network gaming!
I ended up going back to twisted 1.3. The threadedselectreactor in 2.2 just wont play nice (the interleaved iterator blocks randomly, forever), and is the only documented way to get interaction with my own event loop.
Just thought I'd interject: twisted doesn't suck. Write your own darn framework, sure. But making something as powerful as twisted in python is going to be hard - you will fail.
Also, it's a bold (and ignorant) statement to say twisted sucks considering it's been used in simulations software by NASA, RFID-tracking applications, and (ahem) has been chosen as the new default web server for zope3 - something entirely unrelated to Twisted (which evidences just how generalized it is). I might respect your opinion if you just said: "I don't have time to grok twisted.", or "I'm a doze programmer, and Twisted's reactor is too slow on doze." Well ... take back the doze programmer thing - that's hard to respect.
Don't worry, I hated twisted before too - in my younger days. You'll learn eventually that your "awesome" framework only does a subset of what twisted can do for you, only better ;)
Integration of Twisted 2.2 with foreign event loops is borked. It doesn't work, as the documentation states it should work.
This sucks, because existing code bases can't integrate easily. It seems one has to do it the twisted way, or not at all.
I just want cross platform sockets. I dont need twisted for anything else. After pyweek, I'm going to examine SDL_net, and see if it will suit.