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 David.Edelsohn, neologix, pitrou
Date 2013-04-24.21:20:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3r-HzuXPhvLtRGmHBkDLS7MpB=sO_1zy8Q1gDS-2x7zA@mail.gmail.com>
In-reply-to <1366837660.78.0.528342031414.issue17835@psf.upfronthosting.co.za>
Content
> Ok, here is a new patch updating PIPE_MAX_SIZE with a proper value if
> possible.

The patch is correct, however I think it's a bit overkill, especially
since it's Linux only.
Choosing a fixed large value (3 or 4 MB) just consumes a bit more
memory and should be more than enough.

Anyway, this problem also affects all versions from 2.7, so
PIPE_MAX_SIZE should be backported there.
History
Date User Action Args
2013-04-24 21:20:41neologixsetrecipients: + neologix, pitrou, David.Edelsohn
2013-04-24 21:20:41neologixlinkissue17835 messages
2013-04-24 21:20:41neologixcreate