| msg59942 - (view) |
Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2008-01-15 01:02 |
| Currently, all the platform-specific path modules (ntpath, macpath, etc) have normal module names. Since they are implementation details, they should have a "_" prepended to their names. I doubt this would break much code: I've never written witnessed any code outside of the os module that uses the modules. |
|
|
| msg59946 - (view) |
Author: Christian Heimes (christian.heimes) * |
Date: 2008-01-15 01:12 |
| Brett, it sounds like a good idea for the 3.0 stdlib reorg. |
|
|
| msg59947 - (view) |
Author: Brett Cannon (brett.cannon) * |
Date: 2008-01-15 01:14 |
| On Jan 14, 2008 5:12 PM, Christian Heimes <report@bugs.python.org> wrote: > > Christian Heimes added the comment: > > Brett, it sounds like a good idea for the 3.0 stdlib reorg. > Yep, it does. |
|
|
| msg59948 - (view) |
Author: Guido van Rossum (gvanrossum) * |
Date: 2008-01-15 01:16 |
| > Since they are implementation details, they > should have a "_" prepended to their names. No, they are not, and they should not. There are legitimate use cases for importing these directly. E.g. I could be on a Windows box but have a desire to manipulate posix paths. |
|
|
| msg59950 - (view) |
Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2008-01-15 01:25 |
| Well, yes but I think that it's rare enough that in the name of keeping the stdlib clean, it's reasonable to say: import _posixpath and posixpath This also occurs when somone wants to modify __builtin__. |
|
|
| msg59952 - (view) |
Author: Guido van Rossum (gvanrossum) * |
Date: 2008-01-15 01:44 |
| And guess what, in 3.0 __builtin__ is renamed to builtin. |
|
|
| msg59953 - (view) |
Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2008-01-15 01:46 |
| On Jan 14, 2008 7:44 PM, Guido van Rossum <report@bugs.python.org> wrote: > > Guido van Rossum added the comment: > > And guess what, in 3.0 __builtin__ is renamed to builtin. point taken > > > ---------- > resolution: -> rejected > > __________________________________ > Tracker <report@bugs.python.org> > <http://bugs.python.org/issue1828> > __________________________________ > |
|
|