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 pitrou
Recipients neologix, pitrou, rosslagerwall, vstinner
Date 2011-08-20.21:00:02
SpamBayes Score 0.030146958
Marked as misclassified No
Message-id <1313874003.0.0.755289779326.issue12797@psf.upfronthosting.co.za>
In-reply-to
Content
Right now it is painful to integrate openat() with the normal IO classes. You have to figure out the low-level flags yourself (i.e. replicate the logic and error handling from the FileIO constructor), then replicate the open() logic yourself (because you want to set the name attribute on the FileIO object before wrapping it).

Therefore it would be nice if the FileIO constructor and the open() function supported openat natively. I see two possibilities:
- allow a (dirfd, name) tuple for the first "file" argument
- allow an optional dirfd argument at the end of the arglist
History
Date User Action Args
2011-08-20 21:00:03pitrousetrecipients: + pitrou, vstinner, neologix, rosslagerwall
2011-08-20 21:00:02pitrousetmessageid: <1313874003.0.0.755289779326.issue12797@psf.upfronthosting.co.za>
2011-08-20 21:00:02pitroulinkissue12797 messages
2011-08-20 21:00:02pitroucreate