This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author oubiwann
Recipients benjamin.peterson, drkjam, exarkun, giampaolo.rodola, gvanrossum, loewis, mattsmart, oubiwann, pitrou, pmoody, shields
Date 2009-01-03.18:46:49
SpamBayes Score 0.00272823
Marked as misclassified No
Message-id <>
>> As for shutting down any project that is chosen, does such an action 
>> leave older Python versions out in the cold? Shouldn't the project 
>> remain open to support Python versions < 2.7, with a highly visible 
>> that the code is included in 2.7/3.1+? 
> Of course - hence I said "eventually". The project could continue to
> maintain the external version as long as they please, provided it
> doesn't diverge from the in-core version (unless it is the in-core
> version itself that diverges). What I don't want to see happen is that
> the community recommends at some point to ignore the outdated crappy
> version in the core, and replace it with the more-powerful bug-fixed
> version available separately. This has happened in the past, so I'm
> extremely cautious here.

Fantastic! Thanks for the clarification.

David, in the event of netaddr's complete or partial inclusion, are you 
+1 with this and the maintenance of an ip/net library in Python?

Guido, what is your preference regarding feature set/size for an ip/net 
library in Python?
Date User Action Args
2009-01-03 18:46:51oubiwannsetrecipients: + oubiwann, gvanrossum, loewis, exarkun, pitrou, giampaolo.rodola, benjamin.peterson, mattsmart, shields, pmoody, drkjam
2009-01-03 18:46:51oubiwannsetmessageid: <>
2009-01-03 18:46:49oubiwannlinkissue3959 messages
2009-01-03 18:46:49oubiwanncreate