Oh good. Reading the Modules/_struct.c code I see that is indeed what
happens. There are still several instances of misused struct pack and
unpack strings in Lib but the problem is less serious, I'll make a new patch
that just addresses those.
___
Pytho
Gregory P. Smith wrote:
>
> The documentation for the struct module says:
>
> http://docs.python.org/dev/library/struct.html#module-struct
>
> " short is 2 bytes; int and long are 4 bytes; long long ( __int64 on
> Windows) is 8 bytes"
>
> and lists 'l' and 'L' as the pack code for a C long.
On 1/23/08, Thomas Heller <[EMAIL PROTECTED]> wrote:
>
> Gregory P. Smith schrieb:
> > The documentation for the struct module says:
> >
> > http://docs.python.org/dev/library/struct.html#module-struct
> >
> > "short is 2 bytes; int and long are 4 bytes; long long (__int64 on
> Windows)
> > is 8
Gregory P. Smith schrieb:
> The documentation for the struct module says:
>
> http://docs.python.org/dev/library/struct.html#module-struct
>
> "short is 2 bytes; int and long are 4 bytes; long long (__int64 on Windows)
> is 8 bytes"
>
> and lists 'l' and 'L' as the pack code for a C long.
>
>
The documentation for the struct module says:
http://docs.python.org/dev/library/struct.html#module-struct
"short is 2 bytes; int and long are 4 bytes; long long (__int64 on Windows)
is 8 bytes"
and lists 'l' and 'L' as the pack code for a C long.
As its implemented today, the documentation i