➜

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 vstinner
Recipients Jim Fasarakis-Hilliard, Mariatta, chortos, eric.araujo, jesstess, macpherson.scott, ned.deily, python-dev, ronaldoussoren, serhiy.storchaka, vstinner, yan12125
Date 2017-05-10.22:59:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494457185.04.0.386781731532.issue9850@psf.upfronthosting.co.za>
In-reply-to
Content 
> Bump, any update on what to do with this issue?

I updated and completed Chi Hsuan Yen's 3.6-deprecate-macpath.patch to create a pull request. I suggest to start by deprecating macpath in 3.7, and remove it from Python 3.8.

This module is here for years. macOS 9 is now dead, all macOS users migrated to OS X nowadays. I don't think that there is an urgency to *remove* macpath.

The title says "obsolete macpath module dangerously broken": is "dangerous" still up to date after the following fix?

New changeset 54987723de99 by Serhiy Storchaka in branch '3.4':
Issue #9850: Fixed macpath.join() for empty first component.  Patch by
https://hg.python.org/cpython/rev/54987723de99

If yes, we may also warn users in the macpath documentation that the module is dangerous, especially in the documentation of Python < 3.7.
History
Date User Action Args
2017-05-10 22:59:45vstinnersetrecipients: + vstinner, ronaldoussoren, ned.deily, eric.araujo, jesstess, chortos, python-dev, serhiy.storchaka, yan12125, Jim Fasarakis-Hilliard, macpherson.scott, Mariatta
2017-05-10 22:59:45vstinnersetmessageid: <1494457185.04.0.386781731532.issue9850@psf.upfronthosting.co.za>
2017-05-10 22:59:45vstinnerlinkissue9850 messages
2017-05-10 22:59:44vstinnercreate