Feature Requests item #1436243, was opened at 2006-02-21 17:43 Message generated for change (Comment added) made by tjreedy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1436243&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: Tim Delaney (tcdelaney) Assigned to: Georg Brandl (birkenfeld) Summary: Extend pre-allocated integers to cover [0, 255] Initial Comment: When the `bytes` object is introduced (successor to PEP 332) the full range of byte integer objects [0, 255] are likely to be used more commonly. Suggest extending the pre-allocated integer obejcts to include the full range [0, 255]. ---------------------------------------------------------------------- >Comment By: Terry J. Reedy (tjreedy) Date: 2006-02-22 01:38 Message: Logged In: YES user_id=593130 I decided to test out the new svn view facility ;-) Looks like 100 in #define NSMALLPOSINTS 100 in python/trunk/Objects/intobject.c just needs to be upped to 257 Unlike for other builtin types, I could not find a Lib/test/test_int.py file or equivalent where ints are tested, to see if pre-allocation is tested. What did I miss? ---------------------------------------------------------------------- Comment By: Raymond Hettinger (rhettinger) Date: 2006-02-21 17:47 Message: Logged In: YES user_id=80475 Georg, would you take care of this one for Py2.5. Also include the value 256. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1436243&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
