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 h.venev
Recipients benjamin.peterson, h.venev, mark.dickinson, vstinner
Date 2014-04-06.15:16:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1396797417.26.0.4848461453.issue21111@psf.upfronthosting.co.za>
In-reply-to
Content
I did not intend to make it so that PyLong_AsUnsignedLong* to call __int__ but it looks like a good idea because PyLong_AsLong* does that and the patch is exactly about that - removing differences between converting to signed and unsigned.

Should I upload the patch with docs and with the warning fixed? Will it be applied in 3.4.1? It will be a lot easier to check the value of an int than to create a new PyLong = 2^64 and compare the number with that.

P.S.: is there a very fast way to check if a PyLong fits in unsigned long long with the limited API?
P.P.S.: Just a random idea: would it be a to rewrite PyLong to use GMP instead as a PyVarObject of mp_limb_t's?
History
Date User Action Args
2014-04-06 15:16:57h.venevsetrecipients: + h.venev, mark.dickinson, vstinner, benjamin.peterson
2014-04-06 15:16:57h.venevsetmessageid: <1396797417.26.0.4848461453.issue21111@psf.upfronthosting.co.za>
2014-04-06 15:16:57h.venevlinkissue21111 messages
2014-04-06 15:16:56h.venevcreate