This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients brian.curtin, christian.heimes, eckhardt, ezio.melotti, jongfoster, jorend, mhammond, terry.reedy, tim.golden
Date 2011-06-12.19:41:41
SpamBayes Score 0.0
Marked as misclassified No
Message-id <1307907702.36.0.776512325897.issue1669539@psf.upfronthosting.co.za>
In-reply-to
Content
A bug for tracker purposes is a discrepancy between doc and code. That can be fixed in current versions. A design change is a feature request and can only go in future versions. A deprecation warning for one cycle is desirable when appropriate.

"os.path.isabs(path) 
Return True if path is an absolute pathname. On Unix, that means it begins with a slash, on Windows that it begins with a (back)slash after chopping off a potential drive letter."

From what you report, the code does just that, so there is no bug.
Breaking code just because you do not like the current definition is very unlikely to be accepted.

Adding a .isrelative(path) that seems to be equivalent to 'not .ispath' is unlikely to accepted. People who care about the presence of a drive letter can write "path[1]==':'"

"os.path.join(path1[, path2[, ...]]) 
Join one or more path components intelligently. If any component is an absolute path, all previous components (on Windows, including the previous drive letter, if there was one) are thrown away, and joining continues."

>>> import os
>>> os.path.join('foo', 'a:bar')
'foo\\a:bar'

Producing a non-path does not seem intelligent, so I agree that this a bug. I am not sure what this should produce. 'foo/bar', 'a:foo/bar', and raising an exception would be candidates. All would be better than the current useless return. In any case, a bug fix patch can only fix bugs and should not be intermixed with feature patches.

As to the second sentence: your proposal to change documented and inplemented semantics is, again, a feature request, not a bug fix.

If you want to continue with your feature requests, you can if you wish reclassify this issue, retitle again, and open a new behavior issue for the path bug and upload a bugfix-only patch. Before or along with doing so, I would suggest discussion on the python-ideas list.
History
Date User Action Args
2011-06-12 19:41:42terry.reedysetrecipients: + terry.reedy, mhammond, jorend, christian.heimes, jongfoster, tim.golden, ezio.melotti, eckhardt, brian.curtin
2011-06-12 19:41:42terry.reedysetmessageid: <1307907702.36.0.776512325897.issue1669539@psf.upfronthosting.co.za>
2011-06-12 19:41:41terry.reedylinkissue1669539 messages
2011-06-12 19:41:41terry.reedycreate