Renaming platform path modules

[benjaminp]

BPO	1828
Nosy	@gvanrossum, @brettcannon, @tiran, @benjaminp

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2008-01-15.01:44:21.428>
created_at = <Date 2008-01-15.01:02:29.076>
labels = ['type-feature', 'library']
title = 'Renaming platform path modules'
updated_at = <Date 2008-01-15.04:08:33.801>
user = 'https://github.com/benjaminp'

bugs.python.org fields:

activity = <Date 2008-01-15.04:08:33.801>
actor = 'gvanrossum'
assignee = 'none'
closed = True
closed_date = <Date 2008-01-15.01:44:21.428>
closer = 'gvanrossum'
components = ['Library (Lib)']
creation = <Date 2008-01-15.01:02:29.076>
creator = 'benjamin.peterson'
dependencies = []
files = []
hgrepos = []
issue_num = 1828
keywords = []
message_count = 7.0
messages = ['59942', '59946', '59947', '59948', '59950', '59952', '59953']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'brett.cannon', 'christian.heimes', 'benjamin.peterson']
pr_nums = []
priority = 'low'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue1828'
versions = ['Python 3.0']

[benjaminp]

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.

[tiran]

Brett, it sounds like a good idea for the 3.0 stdlib reorg.

[brettcannon]

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.

[gvanrossum]

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.

[benjaminp]

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__.

[gvanrossum]

And guess what, in 3.0 __builtin__ is renamed to builtin.

[benjaminp]

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\>

---