On Apr 2, 1:27 pm, "Paul Boddie" <[EMAIL PROTECTED]> wrote: > On 2 Apr, 13:05, [EMAIL PROTECTED] wrote: > > > > > There is some possibility that Python 3.1 will have what you ask > > for:http://www.python.org/dev/peps/pep-3108/ > > Prior to that PEP being written/published, I made this proposal: > > http://wiki.python.org/moin/CodingProjectIdeas/StandardLibrary/Restru... > > After being brought to the attention of the PEP's author, it seems to > have been swept under the carpet on the Wiki, but it's a more radical > proposal in a number of ways than the PEP seems to be. > > Paul
Note that the conflict of putting modules on top level or better within separate packages is not an either-or decision from a programmers point of view who just wants to access those modules. A top level module like lib or std can be pretty virtual since you can create modules at runtime whenever you try to import them. I used this strategy for a project where editing objects in separate files leaded to a better overview compared to one large file containing all definitions. However I created one module at runtime that served as a common access point for all these particular definitions that were tedious to import separately and would have required file system lookups quite often. This might even allow multiple classifications but I haven't experimented with them yet. Kay -- http://mail.python.org/mailman/listinfo/python-list
