[issue8069] struct documentation problem and suggestion to add fixed size formats

2010-03-05 Thread Mark Dickinson
Mark Dickinson added the comment: Well, it's a bug inasmuch as the docs aren't as clear as they could be.I've got issue 7355 open to remind me to do something about that, though, so this one can probably be closed. -- resolution: -> invalid status: open -> closed ___

[issue8069] struct documentation problem and suggestion to add fixed size formats

2010-03-05 Thread Jeremy Sanders
Jeremy Sanders added the comment: Sorry - I didn't read the docs clearly enough. This probably isn't a bug then. Can you mark it invalid? -- ___ Python tracker ___ _

[issue8069] struct documentation problem and suggestion to add fixed size formats

2010-03-05 Thread Mark Dickinson
Mark Dickinson added the comment: Oops. In "... struct format string doesn't start with.. " in my comment above, replace "doesn't start with" with "starts with". -- ___ Python tracker

[issue8069] struct documentation problem and suggestion to add fixed size formats

2010-03-05 Thread Mark Dickinson
Mark Dickinson added the comment: Please note that the docs distinguish 'standard size and alignment' from 'native size and alignment'. The standard size (which is what you get if your struct format string doesn't start with '<', '>', '=' or '!') does exactly what you suggest: it gives stru

[issue8069] struct documentation problem and suggestion to add fixed size formats

2010-03-05 Thread Jeremy Sanders
New submission from Jeremy Sanders : The struct documentation at http://docs.python.org/library/struct.html says: 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