Well, I've seen no objections. It looks like James is probably going to continue to support Twisted 1.* in his code for now. However, I am going to begin dropping support for it 'as of now'. Going to make for a much emptier src/tlib. =D
Daniel On Nov 14, 2005, at 11:21 AM, Daniel Henninger wrote: > I think I'd lean towards indicating in the readme/install/whatever > that the transport is known to work with upon release, perhaps with > some message indicating that we do not know if it will work with > other versions. That said, James and I are in communication with > the Twisted Jabber community and were kept in the loop about > changes. This was just the first opportunity I got to really test > the new stuff. ;D We'll see what happened. It's possible that > the changes in the new release were not intentional. > > Daniel > > On Nov 14, 2005, at 10:59 AM, Andreas van Cranenburgh wrote: > >> I'd also say let's prefer to support newer versions, but I don't know >> how many people run the old version of twisted. >> >> Maybe there should also be communication / co-operation with the >> twisted >> team, so that new releases won't break the transports anymore. >> >> Or the transports should state more clearly with which Twisted >> version >> they work (like a dependency in package managers). >> >> -- >> Andreas [ http://unstable.nl | >> xmpp:[EMAIL PROTECTED] ] >> [ callto:ils.seconix.com/ >> [EMAIL PROTECTED] ] >> _______________________________________________ >> py-transports mailing list >> py-transports@blathersource.org >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >> >> > > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > >