Re: carry **arguments through different scopes/functions

2016-01-31 Thread Steven D'Aprano
On Sun, 31 Jan 2016 11:19 pm, c.bu...@posteo.jp wrote: > I am not sure what the problem is here, so I don't really know how I > should call the subject for that question. Please offer a better > subject. > > The code below is a extrem simplified example of the original one. But > it reproduce the

Re: carry **arguments through different scopes/functions

2016-01-31 Thread Thomas 'PointedEars' Lahn
Terry Reedy wrote: > On 1/31/2016 7:19 AM, c.bu...@posteo.jp wrote: >> I am not sure what the problem is here, so I don't really know how I >> should call the subject for that question. Please offer a better >> subject. >> >> The code below is a extrem simplified example of the original one. But >

Re: carry **arguments through different scopes/functions

2016-01-31 Thread Peter Otten
c.bu...@posteo.jp wrote: > I am not sure what the problem is here, so I don't really know how I > should call the subject for that question. Please offer a better > subject. > > The code below is a extrem simplified example of the original one. But > it reproduce the problem very nice. Please foc

carry **arguments through different scopes/functions

2016-01-31 Thread c.buhtz
I am not sure what the problem is here, so I don't really know how I should call the subject for that question. Please offer a better subject. The code below is a extrem simplified example of the original one. But it reproduce the problem very nice. Please focus on the variable `return_code`. The

Re: carry **arguments through different scopes/functions

2016-01-31 Thread Joel Goldstick
On Sun, Jan 31, 2016 at 7:19 AM, wrote: > I am not sure what the problem is here, so I don't really know how I > should call the subject for that question. Please offer a better > subject. > > The code below is a extrem simplified example of the original one. But > it reproduce the problem very n

Re: carry **arguments through different scopes/functions

2016-01-31 Thread Terry Reedy
On 1/31/2016 7:19 AM, c.bu...@posteo.jp wrote: I am not sure what the problem is here, so I don't really know how I should call the subject for that question. Please offer a better subject. The code below is a extrem simplified example of the original one. But it reproduce the problem very nice.