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 Devin Jeanpierre
Recipients Devin Jeanpierre, benjamin.peterson, josh.r, mark.dickinson, pitrou, serhiy.storchaka, vstinner, yselivanov
Date 2017-06-15.01:22:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1497489729.87.0.437095421283.issue17870@psf.upfronthosting.co.za>
In-reply-to
Content
> Write your own C extension to do that. Sorry, I don't know what is the best way to write such C extension.

If everyone who wants to convert intptr_t to a python int has to write their own function, then why not just include it in the C-API?

Having support for intmax_t means we never have to have this conversation ever again, because it should work for all int types.

Reopening since this use-case doesn't sound solved yet.
History
Date User Action Args
2017-06-15 01:22:09Devin Jeanpierresetrecipients: + Devin Jeanpierre, mark.dickinson, pitrou, vstinner, benjamin.peterson, serhiy.storchaka, yselivanov, josh.r
2017-06-15 01:22:09Devin Jeanpierresetmessageid: <1497489729.87.0.437095421283.issue17870@psf.upfronthosting.co.za>
2017-06-15 01:22:09Devin Jeanpierrelinkissue17870 messages
2017-06-15 01:22:09Devin Jeanpierrecreate