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 loewis
Recipients loewis, vstinner
Date 2013-06-26.09:17:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372238242.51.0.291402614903.issue18295@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think they are actually the *same* issue.

For the limitations wrt. code objects (maximum size of byte code, maximum number of local variables, maximum number of parameters, etc.), I recommend the following thorough procedure:

1. document in a single text file all the limitations
2. check for each one whether an int is sufficient to represent them at runtime.
3. if yes: leave all structure definitions as-is. Local variables might be  changed to size_t where this simplifies the code. Otherwise, Py_SAFE_DOWNCAST should be used where the actual value ought to be valid already. Runtime errors where a value may come from the outside that might be out of range.
4. if not: widen the structures to Py_ssize_t.
History
Date User Action Args
2013-06-26 09:17:22loewissetrecipients: + loewis, vstinner
2013-06-26 09:17:22loewissetmessageid: <1372238242.51.0.291402614903.issue18295@psf.upfronthosting.co.za>
2013-06-26 09:17:22loewislinkissue18295 messages
2013-06-26 09:17:22loewiscreate