Dear all,
I have just put online a survey addressing the topic of leadership
in the open-source environment. Basically, my objective is to
identify the personal conceptions of good leadership that reside in
the minds of the contributors, in terms of leaders' _behaviors_ and
Tim Peters wrote:
The globals set up for running the script appear not to contain a '__file__'
key, and have a '__name__' key explicitly set to None. If it set either of
these to something useful, or didn't have a '__name__' key explicitly set to
None, warning.warn() would have been able to make
Yo,
I just stumbled on a bug in the python scripting parameter passing.
It seems that under certain conditions, the actual parameters are
ignored, and the default parameters are always used.
It is best shown by the following example:
0) create a python script with the following source:
##
Tim Peters wrote:
it *looks* like you could leave name None, but set '__file__' to something
(non-None) explicitly.
Thanks! This seems to do the trick, and I have a unit test that fails
before and passes after the change.
While creating the test, though, I ran across some disturbing behavior.
Evan Simpson wrote:
Argh. Scripts need a __name__ defined, or various activities choke. It
can't be the Id of the Script, since that can contain '.', which screws
up imports in the Script. It can't be None, since that will cause this
problem.
Are there hidden gotchas lurking around
On Tue, Feb 03, 2004 at 01:16:48PM -0600, Evan Simpson wrote:
Romain Slootmaekers wrote:
I just stumbled on a bug in the python scripting parameter passing.
Actually, it's a bug in the test tab support code. The parameter
fields in the form are set to a , b , and c instead of a, b,
and
Am Dienstag, 3. Februar 2004 23:16 schrieb Paul Winkler:
On Tue, Feb 03, 2004 at 01:16:48PM -0600, Evan Simpson wrote:
Romain Slootmaekers wrote:
I just stumbled on a bug in the python scripting parameter
passing.
Actually, it's a bug in the test tab support code. The parameter
Paul Winkler wrote:
On Tue, Feb 03, 2004 at 01:16:48PM -0600, Evan Simpson wrote:
Romain Slootmaekers wrote:
I just stumbled on a bug in the python scripting parameter passing.
Actually, it's a bug in the test tab support code. The parameter
fields in the form are set to a , b , and c instead
Am Dienstag, 3. Februar 2004 23:16 schrieb Paul Winkler:
On Tue, Feb 03, 2004 at 01:16:48PM -0600, Evan Simpson wrote:
Romain Slootmaekers wrote:
I just stumbled on a bug in the python scripting parameter
passing.
Actually, it's a bug in the test tab support code. The parameter
