[Python-Dev] Deprecating modules (python-dev summary for early
Dec, 2004)
Jim Jewett
jimjjewett at gmail.com
Wed Jan 26 00:26:58 CET 2005
On Tue, 25 Jan 2005 16:21:34 -0600, Skip Montanaro <skip at pobox.com> wrote:
>
> Jim> Would it make sense to add an attic (or even "deprecated")
> Jim> directory to the end of sys.path, and move old modules there? This
> Jim> would make the search for non-deprecated modules a bit faster, and
> Jim> would make it easier to verify that new code isn't depending
> Jim> (perhaps indirectly) on any deprecated features.
> That's what lib-old is for. All people have to do is append it to sys.path
> to get access to its contents:
That seems to be for "obsolete" modules.
Should deprecated modules be moved there as well?
I had proposed a middle ground, where they were moved to a separate directory,
but that directory was (by default) included on the search path.
Moving deprecated modules to lib-old (not on the search path at all) seems to
risk breaking code.
-jJ
More information about the Python-Dev
mailing list