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
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