Looks like you have a good start. I like how you used generators for the streaming API. In my library I went with a callback. So looks like your are going 3->2 instead of the usual 2->3. It's good you are support python 3. For me I believe right now python 2 is in bigger demand and for me porting 2->3 was easier. I know there was a 3to2 tool in the works, not sure if that ever got done. May I ask why you are supporting both json and xml? I really don't think most developers care which data stream is being used for the transport from twitter to the library. I mainly went with json because its easy to parse in python and uses up less bandwidth. Good work and best of luck with your development of this library.
Josh On Fri, Aug 14, 2009 at 3:46 AM, sovnarkom <sovnar...@somebugs.com> wrote: > > Hello there, > http://github.com/sovnarkom/instwitter-py/ > > This is our lightweight, but scalable library for python 3, that > supports: > > — REST and Search API > — *Retweeting API preview > — OAuth > — Streaming API > > You can use this to implement both server and client applications. > > Mini roadmap: > > Versions 1.0 and Milestones < 1.5: > — Testing and bugfixing > — Backporting to python 2.5 and 2.6 > — (?) Atom and RSS formats support > > Milestones 1.6 and Version 2.0: > — High level object wrappers > — Multithreading (in Streaming API) > — Integration with some third party services > > Thanks. > -- Josh
