Laura Creighton wrote: > I am all for breaking up the stdlib logically, via tagging. I am > worried about physically breaking things up, though. How are we > going to guarantee that imports still work after the breakup?
I don't think CPython users will have to worry about this: the main distribution will still ship with all batteries included. However, Jython/IronPython/PyPy users will likely only see a subset. Creating those should be easy using a bit of distutils. We'd only need to put the tag information into some module that setup.py can import to easily get at the tags and module names. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 15 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/ _______________________________________________ stdlib-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/stdlib-sig
