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 eric.snow
Recipients eric.snow, izbyshev, vstinner
Date 2019-02-12.15:40:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549986019.79.0.769638236965.issue35972@roundup.psfhosted.org>
In-reply-to
Content
Having slept on it and given the extra info you've provided I'm more comfortable with the proposed solution now. :)

So the result will be that on 32-bit architectures only 32-bit (signed) ints will be allowed through channels.  On 64-bit platforms (and higher) it will still be 64-bit ints.  That's a livable outcome, particularly since 32-bit platforms already have to deal with such variation already. :)  Plus, the consistency with sys.maxsize makes sense.

The alternative (on 32-bit arch) would be to send through a struct containing the long long, similar to what we do for str and bytes.  I don't think that's worth it.  If it matters we can do something like that later (since it's an implementation detail).

Consequently, I've approved the PR.  I'll merge it in a little while.

Thanks for working on this.
History
Date User Action Args
2019-02-12 15:40:19eric.snowsetrecipients: + eric.snow, vstinner, izbyshev
2019-02-12 15:40:19eric.snowsetmessageid: <1549986019.79.0.769638236965.issue35972@roundup.psfhosted.org>
2019-02-12 15:40:19eric.snowlinkissue35972 messages
2019-02-12 15:40:19eric.snowcreate