Tom Karzes added the comment:
If it's going to be closed, it should at least be acknowledged that it *is* a
fundamental design flaw, stemming from the misguided goal of trying (and
necessarily failing) to allow options to be freely intermixed with positional
arguments, which of course can't
Tom Karzes added the comment:
Is there *still* no fix for this? I keep running into this bug. People
sometimes say "oh, it's no problem, just use = to associate the option value
with the option name". That is so sad. It's basically saying "it can't be
made to work the wa
Tom Karzes added the comment:
Thanks Tim and Terry. Stackless Python sounds interesting. It's nice to know
that others had the same idea I did, although I tend to shy away from exotic
variants since they tend to be less well-supported. Any chance that CPython
will go stackless at some
Tom Karzes added the comment:
I tested this some more, and one thing became clear that I hadn't realized
before: This bug has nothing to do specifically with generators (as I had
thought), but is in fact due purely to the recursion limit.
I created a recursive test program that doesn't use
Tom Karzes added the comment:
That is a good point, except I don't believe the value needed to expose this
bug is a "too-high limit" (as the documentation calls it). I set it to 100100
for convenience, but in practice even a value of 17000 is more than enough to
expose the bug on
New submission from Tom Karzes :
If I create a sufficiently long chain of generators, I encounter a segmentation
fault. For example, the following works as expected:
% ./gen_bug3.py 1
1
%
But for sufficiently larger chain lengths, it seg faults:
% ./gen_bug3.py
Tom Karzes <kar...@sonic.net> added the comment:
Here's my situation: I originally used optparse, although some of the guys I
worked with at the time were starting to use argparse. At first I thought, I'm
sticking with optparse, it's more standard than argparse and probably better
sup
Tom Karzes <kar...@sonic.net> added the comment:
I'm dismayed to see that this bug was reported in 2010, yet as of January 2018
has not yet been fixed. This option parsing behavior is contrary to Unix
option passing conventions. I certainly don't mind enhancements, but the last
