[Python-ideas] Moving development out of the standard library

Nick Coghlan ncoghlan at gmail.com
Tue Jun 8 22:56:35 CEST 2010

On 09/06/10 05:33, Terry Reedy wrote:
> On 6/7/2010 5:20 PM, Eric Smith wrote:
>> pip could use the new features in 3.4, and it could get the new features
>> in 2.x if the users were willing to install the updated library, since
>> it's not in the stdlib. But for 3.3 you'd be stuck.
> I see no reason why 3.3 users could not also download the 3.4 version of
> something just as well as user of earlier versions (who well might
> already have the 3.3 version).

I believe Eric was pointing out the fact that, by default, there is no 
directory on sys.path that will override the standard library versions 
of a module or package for all applications using that interpreter 

So you're forced to either resort to destructive replacement (actually 
overwriting the standard library module on disk) or else tinkering with 
sys.path in each app or a library to insert an "override" directory 
before the normal standard library paths.

It sometimes seems to me that, for the advocates of a more granular 
standard library, proposing standardisation of such an override 
directory would be an interesting way to test the waters (since it would 
make it much easier to drop in backported updates to standard library 


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-ideas mailing list