On Wed, Mar 4, 2009 at 10:14 AM, Sidnei da Silva <sidnei.da.silva@gmail.com> wrote:
On Wed, Mar 4, 2009 at 3:04 PM, Guido van Rossum <guido@python.org> wrote:
Sounds like it's not so much the code that's future proof but the process used for evolving it. That seems to be missing for asyncore. :-(
Turning the issue around a bit, has anyone considered polishing up the current fix to restore it's backwards compatibility, instead of starting a discussion about a full-blown replacement?
I think that would be enough for most asyncore users (or even the couple few affected) for the moment, and then we can think about a possible future replacement.
If it can be done while maintaining backwards compatibility with both the 2.6 version and the pre-2.6 version, that would be great of course! But can it? -- --Guido van Rossum (home page: http://www.python.org/~guido/)