Martin v. Löwis wrote: > As for PEP 4: I don't know whether it needs to be listed there. It > appears that the PEP is largely unmaintained (I, personally, do not > really maintain it). So one option would be to just stop using PEP 4 > for recording deprecations, since we now have the warnings module. > If we want to keep PEP 4, we need to follow the procedures it > requires (or modify them if we don't like them). There is a need for a central place where deprecations are posted. You can't tell people to go hunt the standard lib for uses of the warning module in order for them to catch up with the current state of affairs. One thing that we shouldn't forget is that Python users do not necessarily upgrade to new Python releases every time there's a new release. Production users of Python will often skip a release or two depending on their needs, time frames and audit cycles. It is very important for them to know that module or other technology will be deprecated two releases down the road, so that they can accomodate for these changes today. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Dec 13 2004) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2004-12-06: Released eGenix mx Extensions for Python 2.4 ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
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