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 pitrou
Recipients lemburg, ned.deily, pitrou, ronaldoussoren
Date 2010-12-21.18:36:04
SpamBayes Score 8.314437e-10
Marked as misclassified No
Message-id <1292956561.3720.4.camel@localhost.localdomain>
In-reply-to <1292806293.27.0.64653489151.issue10735@psf.upfronthosting.co.za>
Content
> Adding a warning sounds like a good idea.  Is it reasonable to include
> a recommended cross-platform approach in the platform doc, like either
> the sys.maxsize test or the struct.calsize("P") test (which is used as
> a default fallback in platform.architecture)?

Yes.

>   Are there any currently supported platforms where either of those
> wouldn't work?

No. I think even on fringe platforms it is unlikely for size_t to not
reflect the native pointer width (although it is theoretically
possible).
History
Date User Action Args
2010-12-21 18:36:07pitrousetrecipients: + pitrou, lemburg, ronaldoussoren, ned.deily
2010-12-21 18:36:05pitroulinkissue10735 messages
2010-12-21 18:36:05pitroucreate