homepage

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 amaury.forgeotdarc, loewis, mark.dickinson, nadeem.vawda, rhettinger, schmir
Date 2012年02月08日.21:08:12
SpamBayes Score 2.7352638e-05
Marked as misclassified No
Message-id <1328735292.94.0.745762538967.issue13965@psf.upfronthosting.co.za>
In-reply-to
Content
On Win64, the long type is 32-bit; the compiler does not support any other mode. So the question "whether another memory model could have been selected during compilation" must be answered as "no, the compiler does not support multiple memory models".
We could have chosen to not use long for ob_ival. However, that would have cause a massive API change, as functions such as PyLong_AsLong either would have to change their return type, or start raising exceptions even for exact int objects.
In Python 3, this issue is fixed as the int type has no range constraint anymore.
History
Date User Action Args
2012年02月08日 21:08:12loewissetrecipients: + loewis, rhettinger, amaury.forgeotdarc, mark.dickinson, schmir, nadeem.vawda
2012年02月08日 21:08:12loewissetmessageid: <1328735292.94.0.745762538967.issue13965@psf.upfronthosting.co.za>
2012年02月08日 21:08:12loewislinkissue13965 messages
2012年02月08日 21:08:12loewiscreate

AltStyle によって変換されたページ (->オリジナル) /