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 docs@python, martin.panter, socketpair, vstinner
Date 2016-05-29.09:11:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZJbB8pT68y0QC+GRb2VN1c5R6jO9CpB=A79TGrZE8DMQ@mail.gmail.com>
In-reply-to <1464509427.68.0.396436938394.issue27150@psf.upfronthosting.co.za>
Content
I don't think that it's possible nor worth it to wrap all fcntl() and all
ioctl() calls. I see these functions as very low-level APIs and so I
consider that the caller is responsible of what he/she does.

If you want to change something, explian in fcntl module doc that the PEP
466 is not implemented in this module znd it's a deliberate choice.

I agree with Martin, it's the responsability of the dev to use the right
command depending on the use case.
History
Date User Action Args
2016-05-29 09:11:49vstinnersetrecipients: + vstinner, docs@python, socketpair, martin.panter
2016-05-29 09:11:49vstinnerlinkissue27150 messages
2016-05-29 09:11:49vstinnercreate