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 davidmrdavid
Recipients RJ722, christian.heimes, davidmrdavid, eryksun, giampaolo.rodola, noctiflore
Date 2021-01-06.04:52:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1609908771.09.0.395204050157.issue30044@roundup.psfhosted.org>
In-reply-to
Content
Hi folks,
I'd be interested in contributing to this issue, since it seems "easy" enough, but I'm unsure that consensus was reached about the right solution.

From what I gathered from Giampaolo's comments, we have solutions that should work for Unix-y systems and MacOS. So that's clear.

For Windows though, I'm unsure. It appears, we'd need kernel-mode-enabled clients to do this and maybe that's enough to discourage this effort altogether.

So it appears we have 3 options then:
1. Implement a new function that copies ownership in linux+mac but not in Windows. Then to document that difference.
2. Implement a new function that copies ownership in linux+mac, then use the native NT API to achieve the same result in Windows. Document the limitations
3. Just document the existing limitations.

Do we have a preference? I do not, just excited to potentially contribute something :) 

Thanks!
History
Date User Action Args
2021-01-06 04:52:51davidmrdavidsetrecipients: + davidmrdavid, giampaolo.rodola, christian.heimes, eryksun, noctiflore, RJ722
2021-01-06 04:52:51davidmrdavidsetmessageid: <1609908771.09.0.395204050157.issue30044@roundup.psfhosted.org>
2021-01-06 04:52:51davidmrdavidlinkissue30044 messages
2021-01-06 04:52:50davidmrdavidcreate