On Fri, 6 Apr 2012 00:17:49 -0400
Andrew Clay Shafer a...@parvuscaptus.com wrote:
What were you expecting/trying to do with the code change?
Here's a patch that hopefuly answers the question, although be warned
that it does not actually work even if the scope of parser is fixed
(it measures
Hi, All:
In the process of tinkering for lp:959221, I made a benign modification
to make it possible to invoke swift as a module, when everything broke
loose with errors like NameError: global name 'parser' is not defined.
Looking at the code it seems like a thinko, with the following fix:
diff
Pete,
There is clearly something interesting going on with scope. 'options',
which appears to really be 'parser' get passed in as a variable, but are
then gets over written before being used by the call using the global
'parser'.
(options, args) = parse_args(parser, args)
The history of the
3 matches
Mail list logo
