> Guido van Rossum wrote: > > > The cure for the pain is the same as for any other third-party > > > module: tie newer releases to newer Python versions. > > > > But that's exactly what's unacceptable in theis case: newer versions > > of PyXML provide new PyXML features, and Python users who wish to use > > the new PyXML features should *not* have to upgrade to the latest and > > greatest Python. > > I still don't see how this is any different than any other Python > module. It's probably painful keeping NumPy compatible with old versions > of Python also. How is PyXML unique in this? > > Paul Prescod I didn't say that. NumPy has exactly the same issues. You proposed to tie newer versions of 3rd party modules to newer Python releases. I think it's wise to stay at least 1 or 2 releases behind. You don't want to lose your users because you forced them into a bad upgrade of the rest of their Python installation. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4