➜

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 martin.panter
Recipients benjamin.peterson, martin.panter
Date 2016-09-06.00:39:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473122358.59.0.347741692131.issue27961@psf.upfronthosting.co.za>
In-reply-to
Content 
Makes sense if it already doesn’t work without HAVE_LONG_LONG. This also came up in discussion of adding a BLAKE2 hash algorithm: <https://www.mail-archive.com/search?l=mid&q=CAMpsgwZJ47osOt597YedkAqXisu3b_4giTBXSMq6GH%2B_yLf2aw@mail.gmail.com>. FWIW the normal Windows compiler may not actually have “long long”; we use __int64 instead: https://hg.python.org/cpython/annotate/default/PC/pyconfig.h#l267 so maybe in some places (such as this bug title) you should refer to PY_LONG_LONG rathe than “long long” to avoid confusion :)
History
Date User Action Args
2016-09-06 00:39:18martin.pantersetrecipients: + martin.panter, benjamin.peterson
2016-09-06 00:39:18martin.pantersetmessageid: <1473122358.59.0.347741692131.issue27961@psf.upfronthosting.co.za>
2016-09-06 00:39:18martin.panterlinkissue27961 messages
2016-09-06 00:39:18martin.pantercreate