➜

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 ronaldoussoren
Recipients Arfrever, Jim.Jewett, Michael.Felt, benjamin.peterson, christian.heimes, georg.brandl, giampaolo.rodola, hynek, larry, milko.krachounov, neologix, pitrou, ronaldoussoren, serhiy.storchaka, tarek, terry.reedy
Date 2018-08-16.15:34:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534433665.35.0.56676864532.issue17180@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't understand this clarification:

> Clarification: while Mac/OS falls under "posix" in python terms - maybe
> "breakage" will need to be accepted,
> or, for "back-ports" Mac/OS will be "as if root or super-user" and use
> an additional (optional) argument in 3.8 and beyond
> to keep backwards compatibility.

AFAIK macOS should behave just like other posix-y platforms here.  In particular, I've verified that cp(1) behaves the same as on other platforms: the SUID bit is stripped when copying a setuid file.

Do you have a reason to assume that macOS is special here?


P.S. macOS is spelled macOS, not Mac/OS
History
Date User Action Args
2018-08-16 15:34:25ronaldoussorensetrecipients: + ronaldoussoren, georg.brandl, terry.reedy, pitrou, larry, giampaolo.rodola, christian.heimes, benjamin.peterson, tarek, Arfrever, milko.krachounov, neologix, hynek, Jim.Jewett, serhiy.storchaka, Michael.Felt
2018-08-16 15:34:25ronaldoussorensetmessageid: <1534433665.35.0.56676864532.issue17180@psf.upfronthosting.co.za>
2018-08-16 15:34:25ronaldoussorenlinkissue17180 messages
2018-08-16 15:34:25ronaldoussorencreate