Tarek Ziadé wrote: > Hello, > > Since the addition of PEP 370, (per-user site packages), site.py and > distutils/command/install.py are *both* providing the various > installation directories for Python, > depending on the system and the Python version. > > We have also started to discuss lately in various Mailing Lists the > addition of new schemes for IronPython and Jython, meaning that we > might add some more in both places. > > I would like to suggest a simplification by adding a dedicated module > to manage these installation schemes in one single place in the > stdlib. > > This new independant module would be used by site.py and distutils and > would also make it easier for third party code to work with these > schemes. > Of course this new module would be rather simple and not add any new > import statement to avoid any overhead when Python starts and loads > site.py +1 -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Oct 28 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
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