➜

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 meador.inge
Recipients amaury.forgeotdarc, belopolsky, meador.inge, vstinner
Date 2011-12-15.05:05:01
SpamBayes Score 0.01132532
Marked as misclassified No
Message-id <CAK1QooqmjroiZ3ahWKs+YeEd+63BNj9gAkRc=LPDJ8TjqX3HbA@mail.gmail.com>
In-reply-to <1322727070.74.0.529182027643.issue13097@psf.upfronthosting.co.za>
Content 
On Thu, Dec 1, 2011 at 2:11 AM, STINNER Victor <report@bugs.python.org> wrote:

> Is there really an use case where you need 2 ** 20 (1,048,576) arguments? If yes, I'm not against the torture in this case :-)

Not very likely :-)  However, the segfault can occur with less
arguments in low stack space situations (e.g. deep callstack).

> If no, why not raising an error if there are too many arguments? E.g. limit to 1,024 arguments or maybe just 10?

That is certainly an option.
History
Date User Action Args
2011-12-15 05:05:02meador.ingesetrecipients: + meador.inge, amaury.forgeotdarc, belopolsky, vstinner
2011-12-15 05:05:02meador.ingelinkissue13097 messages
2011-12-15 05:05:01meador.ingecreate