By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,461 Members | 1,120 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,461 IT Pros & Developers. It's quick & easy.

Float to int conversions (was: int(float(sys.maxint)) buglet)

P: n/a
<Sorry for the disconnected reply -I've been having news server issues, and just
switched to the mailing list instead>

A quick check of the source code reveals that this behaviour is deliberate.
There is apparently an issue with the corner case breaking badly (potentially
raising an exception) on some platforms. So, Python plays it safe and converts
the two boundary cases to Python longs instead of Python ints.

See the code for the gory details (the relevant function is 'float_int'):


Nick Coghlan | nc****** | Brisbane, Australia
Jul 18 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.