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 mwh
Recipients
Date 2002-05-16.09:21:44
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=6656

I'm not *trying* to be a party-pooper, but there's another
problem: the point of passing a mutable array is so that
fcntl.ioctl can return ioctl(2)'s return code rather than
the string it returns now.  So if someone does use arrays
(or I guess Numeric.arrays?) for ioctls this would very
likely cause breakage.  I don't know how likely that is. 
Probably not very.  But I know that if this change broke my
code, I'd be a bit miffed.

All this is a bit annoying, as mutating arrays is clearly
the right solution -- where's that time machine?
History
Date User Action Args
2007-08-23 14:01:21adminlinkissue555817 messages
2007-08-23 14:01:21admincreate