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 neologix
Recipients neologix, pitrou, sbt, vstinner
Date 2013-08-28.21:29:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3XLDNQ6B=UnaReQrjPUxuONktY=U-Hajr6sqfTyANO1g@mail.gmail.com>
In-reply-to <1377723416.46.0.990785965458.issue18643@psf.upfronthosting.co.za>
Content
> Why not using a different value (constant) for sockets?

We can add a new constant (e.g. SOCK_MAX_SIZE), that would be fine, as
long as it aliases to PIPE_MAX_SIZE.
There's no need to have two values (the current 4MB value is fine).

> By alternating between PIPE and SOCK, you get POPK, which is as descriptive as it gets.

Thank you Antoine :-)

I'll think I'll go for:
SOCK_MAX_SIZE = PIPE_MAX_SIZE = 4MB
History
Date User Action Args
2013-08-28 21:29:35neologixsetrecipients: + neologix, pitrou, vstinner, sbt
2013-08-28 21:29:35neologixlinkissue18643 messages
2013-08-28 21:29:35neologixcreate