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 terry.reedy
Recipients christian.heimes, marco.buttu, mark.dickinson, terry.reedy
Date 2013-07-27.20:30:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, 'long int' should just be 'int' in 3.x.

However, int/int (integer division) is *not* the same thing as int/float. In the latter case, the int is converted to float first and if that conversion fails, there is no result.

Now that int/int is always converted to float, it seems sensible that out of float range results be +-inf. But there may be an issue with back compatibility. I know there has been discussion on overflow vs. inf in various contexts.
Date User Action Args
2013-07-27 20:30:29terry.reedysetrecipients: + terry.reedy, mark.dickinson, christian.heimes, marco.buttu
2013-07-27 20:30:29terry.reedysetmessageid: <>
2013-07-27 20:30:29terry.reedylinkissue18570 messages
2013-07-27 20:30:29terry.reedycreate