En Sun, 12 Apr 2009 19:28:43 -0300, > escribió:
Ryniek90 writes:
When i wanted to send an .iso file of 4GB length, i had traceback:
"OverflowError: requested number of bytes is more than a Python string
can hold"
You're not supposed to put the 4GB all in one string. Open the
socket and sen
Steven D'Aprano REMOVE-THIS-cybersource.com.au> writes:
>
> which suggests to me that it will be implementation dependent
The length of sequences is constrained by sys.maxsize
(and no, you can't change it).
--
http://mail.python.org/mailman/listinfo/python-list
On 13 Apr 2009 01:45:56 GMT, Steven D'Aprano
wrote:
On Mon, 13 Apr 2009 00:21:34 +0200, Ryniek90 wrote:
When i wanted to send an .iso file of 4GB length, i had traceback:
"OverflowError: requested number of bytes is more than a Python string
can hold"
Sockets are being used in every network
On Mon, 13 Apr 2009 00:21:34 +0200, Ryniek90 wrote:
> When i wanted to send an .iso file of 4GB length, i had traceback:
> "OverflowError: requested number of bytes is more than a Python string
> can hold"
>
> Sockets are being used in every network app, i.e: p2p progs (like
> BitTorrent), and ex
Ryniek90 writes:
> When i wanted to send an .iso file of 4GB length, i had traceback:
> "OverflowError: requested number of bytes is more than a Python string
> can hold"
You're not supposed to put the 4GB all in one string. Open the
socket and send smaller packets through it.
--
http://mail.pyt
When i wanted to send an .iso file of 4GB length, i had traceback:
"OverflowError: requested number of bytes is more than a Python string
can hold"
Sockets are being used in every network app, i.e: p2p progs (like
BitTorrent), and exchanged data is often bigger than 4GB. So why i've
had that
