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 loewis
Recipients
Date 2002-02-25.17:36:44
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=21627

On your system, 'unsigned long' is the same type as
'unsigned int'. Furthermore, passing a negative number -n is
the same as passing 2**32-n, atleast on a 32-bit
architecture. So even if your driver processes unsigned
ints, you will be able to pass the correct value using the
corresponding negative number.

Furthermore, if you use the hex notation, it will work even
on 64-bit ports unmodified: unsigned long will be 64 bit,
but so will be the Python int type, and the hex literal then
indicates a positive integer, which is well in range.

As for ioctl not being Posix: It actually is, in the latest
revision of Posix (IEEE Std 1003.1-2001), which is identical
to Single Unix (see the top of the ioctl page).

In any case, I think this is not worth fixing, as I cannot
see a problem arising from it that cannot be easily
worked-around, hence closing the report.
History
Date User Action Args
2007-08-23 13:59:21adminlinkissue521723 messages
2007-08-23 13:59:21admincreate