[issue25026] (FreeBSD/OSX) Fix fcntl module to accept 'unsigned long' type commands for ioctl(2).
koobs
report at bugs.python.org
Tue Sep 8 09:29:51 CEST 2015
koobs added the comment:
Thanks for the insight Serhiy. A few questions ..
Is clinic code updated based on *.c declarations at build time? If not when/how is the best place/method to run this for our ports/package builds?
Does your suggestion to switch unsigned_int to unsigned_long imply that the following lines are no longer necessary?
- if (PyArg_ParseTuple(args, "O&Iw#|i:ioctl",
+ if (PyArg_ParseTuple(args, "O&kw#|i:ioctl",
How do we get something like this fixed upstream for FreeBSD/OSX?
If left un-patched, what is the impact on the user/system? Just a warning on console?
----------
versions: +Python 3.6
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25026>
_______________________________________
More information about the Python-bugs-list
mailing list