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 ned.deily
Recipients BreamoreBoy, ezio.melotti, flox, joe.amenta, jvr, loewis, ned.deily, r.david.murray, ronaldoussoren, vstinner
Date 2010-09-13.22:07:21
SpamBayes Score 1.3263606e-08
Marked as misclassified No
Message-id <1284415643.76.0.871788838521.issue767645@psf.upfronthosting.co.za>
In-reply-to
Content
There seems to be some confusion about the macpath.py module.  I'm not sure why it even exists in Python 3.  Note it has to do with obsolete Classic MacOS-style paths (colon-separated paths) which are available on Mac OS X only through deprecated Carbon interfaces.  I'm not even sure that those style paths do support unicode.  More importantly, the underlying Carbon interfaces that macpath.py uses were removed for Python 3.  AFAIK, virtually nothing on OS X uses these style paths anymore and, with the removal of all the old Mac Carbon support in Python 3, I don't think there is any Python module that can use these paths other than macpath.  I think this module should be marked for deprecation and removed.  There is no reason to modify it nor add a NEWS note, even for 2.7.
History
Date User Action Args
2010-09-13 22:07:23ned.deilysetrecipients: + ned.deily, loewis, jvr, ronaldoussoren, vstinner, ezio.melotti, r.david.murray, joe.amenta, flox, BreamoreBoy
2010-09-13 22:07:23ned.deilysetmessageid: <1284415643.76.0.871788838521.issue767645@psf.upfronthosting.co.za>
2010-09-13 22:07:22ned.deilylinkissue767645 messages
2010-09-13 22:07:21ned.deilycreate