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 Devin Jeanpierre
Recipients Arfrever, David.Townshend, Devin Jeanpierre, Julian, amaury.forgeotdarc, benjamin.peterson, cvrebert, docs@python, eric.araujo, neologix, pitrou, vstinner
Date 2011-12-30.22:07:18
SpamBayes Score 7.8195065e-08
Marked as misclassified No
Message-id <1325282838.91.0.688268261114.issue12760@psf.upfronthosting.co.za>
In-reply-to
Content
> Amaury did not suggest to use openat, but the new opener argument to open, which was especially added for use cases such as the one discussed here:

Sorry, yes. Wrong words, same thought. We can implement this using opener, but we could implement this with os.open before. What's changed, except that there's more ways to do it? (There is slightly more versatility with the opener method, but no more obviousness and no less typing).

My understanding from reading the other thread is that this is not the primary use-case of the new parameter for open(). In fact, this ticket was not really mentioned at all there.
History
Date User Action Args
2011-12-30 22:07:18Devin Jeanpierresetrecipients: + Devin Jeanpierre, amaury.forgeotdarc, pitrou, vstinner, benjamin.peterson, eric.araujo, Arfrever, cvrebert, neologix, docs@python, Julian, David.Townshend
2011-12-30 22:07:18Devin Jeanpierresetmessageid: <1325282838.91.0.688268261114.issue12760@psf.upfronthosting.co.za>
2011-12-30 22:07:18Devin Jeanpierrelinkissue12760 messages
2011-12-30 22:07:18Devin Jeanpierrecreate