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 ned.deily, ronaldoussoren, vstinner
Date 2018-12-12.16:31:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544632284.12.0.788709270274.issue35471@psf.upfronthosting.co.za>
In-reply-to
Content
> I was against removing the module in the past because parts of the macOS API still used (on probably still use) classic MacOS style paths.  Most if not all APIs are by this time deprecated, which makes it less and less like that anyone will use macpath going forward.

bpo-9850 has a scary title: "obsolete macpath module dangerously broken and should be removed". Extract:

   "Even if one did have a need to use the obsolete old-style paths, the macpath module is currently practically unusable for anything other than simple character manipulations of the path.  Nearly all of the functions that actually call OS routines are broken in one or more ways."
History
Date User Action Args
2018-12-12 16:31:24vstinnersetrecipients: + vstinner, ronaldoussoren, ned.deily
2018-12-12 16:31:24vstinnersetmessageid: <1544632284.12.0.788709270274.issue35471@psf.upfronthosting.co.za>
2018-12-12 16:31:24vstinnerlinkissue35471 messages
2018-12-12 16:31:23vstinnercreate