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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, kiilerix, mark.dickinson
Date 2010-04-20.14:44:29
SpamBayes Score 4.3190957e-07
Marked as misclassified No
Message-id <q2yd38f5331004200744n1f551218r13305ac2e4bbdcdc@mail.gmail.com>
In-reply-to <1271773847.98.0.0348498965653.issue8469@psf.upfronthosting.co.za>
Content
On Tue, Apr 20, 2010 at 10:30 AM, Mark Dickinson <report@bugs.python.org> wrote:
..
> It would be possible to add the 'standard' sizes to that table (i.e. the sizes that you get when using '<', '>', etc.);  would that be helpful?

The documentation already includes standard sizes in text:

"Standard size and alignment are as follows: no alignment is required
for any type (so you have to use pad bytes); short is 2 bytes; int and
long are 4 bytes; long long (__int64 on Windows) is 8 bytes; float and
double are 32-bit and 64-bit IEEE floating point numbers,
respectively. _Bool is 1 byte."

It may be helpful to add "Standard size" column to the code table with
a footnote that it only applies when <, > or ! code is used and that
for native sizes one should consult struct.calcsize().
History
Date User Action Args
2010-04-20 14:44:32Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, mark.dickinson, kiilerix
2010-04-20 14:44:29Alexander.Belopolskylinkissue8469 messages
2010-04-20 14:44:29Alexander.Belopolskycreate