Re: [Zope-dev] Re: bug in 2.6.2, 2.6.1 , and probably others.
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 > > fields in the form are set to "a ", "b ", and "c " instead of "a", > > "b", and "c". I'm fixing it in CVS for 2.7. > > Will this get into 2.6.4-final too? Sorry, I build my example script with wrong pararmeter (the space between 'a' and '=' is important) The bug is in Zope 2.6.4-rc2 too ! Dirk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: bug in 2.6.2, 2.6.1 , and probably others.
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 of "a", "b", and "c". I'm fixing it in CVS for 2.7. Will this get into 2.6.4-final too? -1. In fact, it shouldn't even make 2.7.0 final. I don't think it is a "showstopper" bug, and would prefer to stick by our process ("*no* non-packaging changes between the last RC and the release.") Tres. -- === Tres Seaver[EMAIL PROTECTED] Zope Corporation "Zope Dealers" http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: bug in 2.6.2, 2.6.1 , and probably others.
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 > > fields in the form are set to "a ", "b ", and "c " instead of "a", > > "b", and "c". I'm fixing it in CVS for 2.7. > > Will this get into 2.6.4-final too? I tried the example with zope 2.6.4-rc2. I got the right output and can't see a bug. Regards, Dirk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Re: Zope 2.7.0 rc2 + python 2.3.3 problem
[Evan Simpson] > ... > While creating the test, though, I ran across some disturbing > behavior. In interactive mode (and when running unit tests) > something is getting confused: ... [examples snipped] ... I copied the rest into a Python bug report, since it didn't appear to have anything to do with Zope anymore: http://www.python.org/sf/890010 ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: bug in 2.6.2, 2.6.1 , and probably others.
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 "c". I'm fixing it in CVS for 2.7. Will this get into 2.6.4-final too? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's HARVESTER GUTS SCREEN! (random hero from isometric.spaceninja.com) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.7.0 rc2 + python 2.3.3 problem
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 giving all Scripts the __name__ > "Script (Python)"? Other suggestions? Ages ago I suggested "__main__" because the newly instantiated code is sort-of a new top-level namespace for a sort-of python interpreter. But given all the issues that arrised with the other choices maybe there's lurking gotchas with "__main__" too. Anyway, thats my thought. -- Jamie Heilman http://audible.transient.net/~jamie/ "Paranoia is a disease unto itself, and may I add, the person standing next to you may not be who they appear to be, so take precaution." -Sathington Willoughby ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: bug in 2.6.2, 2.6.1 , and probably others.
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 "c". I'm fixing it in CVS for 2.7. Normal parameter passing is unaffected. Cheers, Evan @ 4-am ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.7.0 rc2 + python 2.3.3 problem
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. In interactive mode (and when running unit tests) something is getting confused: Python 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> range(1.0) __main__:1: DeprecationWarning: integer argument expected, got float [0] >>> So far, so good. However: Python 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> __name__=None >>> range(1.0) [] >>> 1+1 Traceback (most recent call last): File "/usr/lib/python2.3/warnings.py", line 57, in warn warn_explicit(message, category, filename, lineno, module, registry) File "/usr/lib/python2.3/warnings.py", line 63, in warn_explicit if module[-3:].lower() == ".py": TypeError: unsubscriptable object >>> ...and... Python 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import warnings >>> warnings.simplefilter("error", category=DeprecationWarning) >>> range(1.0) [] >>> 1+1 Traceback (most recent call last): File "/usr/lib/python2.3/warnings.py", line 57, in warn warn_explicit(message, category, filename, lineno, module, registry) File "/usr/lib/python2.3/warnings.py", line 92, in warn_explicit raise message DeprecationWarning: integer argument expected, got float >>> ...and... Python 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import pdb >>> __name__ = None >>> pdb.run('range(1.0)') > (1)?() (Pdb) s --Call-- > /usr/lib/python2.3/warnings.py(24)warn() -> def warn(message, category=None, stacklevel=1): (Pdb) r --Return-- /usr/lib/python2.3/bdb.py:302: RuntimeWarning: tp_compare didn't return -1 or -2 for exception i = max(0, len(stack) - 1) [traceback snipped] Looks like something isn't properly propagating exceptions. Cheers, Evan @ 4-am ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] bug in 2.6.2, 2.6.1 , and probably others.
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: ## Script (Python) "buggy" ##bind container=container ##bind context=context ##bind namespace= ##bind script=script ##bind subpath=traverse_subpath ##parameters=a = 'default_a', b = 'default_b', c = 'default_c' ##title=exposes a bug in 2.6.1 and 2.6.2 ## print a print b print c return printed 1) in the ZMI click on the "test" tab and fill in the values: parameter value a a b b c c 2) click on "run script" 3) the result page is: default_a default_b default_c that's not what it should be. I quickly browsed the bug collector and did not found a related issue, but before I file a bug report, I'd like to know what versions are affected. I don't have the time nor the desire to install all versions and test this. So if you guys could take a minute to test it on your version. tia, Romain Slootmaekers. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Re: Zope 2.7.0 rc2 + python 2.3.3 problem
[Tim Peters] >> 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 up *something* for warn_explicit's filename and/or >> module arguments. [Evan Simpson] > 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. Since that's mondo obscure, let's point to your explanation: http://mail.python.org/pipermail/python-dev/2004-January/041749.html That's especially worth reading because of Guido's profusely apologetic response . > It can't be None, since that will cause this problem. > > Are there hidden gotchas lurking around giving all Scripts the > __name__ "Script (Python)"? Other suggestions? I don't really know about Python Script, I've been talking about what Python's warnings module does. Perhaps you could use the Id of the script as __name__ after Id.replace('.', '-') (i.e., get rid of the dots)? Or it *looks* like you could leave name None, but set '__file__' to something (non-None) explicitly. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 2.7.0 rc2 + python 2.3.3 problem
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 up *something* for warn_explicit's filename and/or module arguments. 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 giving all Scripts the __name__ "Script (Python)"? Other suggestions? Cheers, Evan @ 4-am ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [leadership/opensource] invitation to online survey
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 _characteristics_. What is a good open-source project leader, from the contributor's point of view? To what extent, those personal believes are shared among developers? Can the contributor's national cultural belonging and level of experience in contributing to open-source projects explain such differences in their idea of what a good leader is? I would really appreciate your participation to the survey! Contribution (*completely* anonymous) consists in rating a list of statements that may be used to describe the behaviors of an open-source leader. It will take around ten minutes - there aren't any "time-consuming" open ended questions;) Following, the link to the survey: http://freeonlinesurveys.com/rendersurvey.asp?id=52191 If you are interested, I will not miss to email you a link to the final report, when ready ;) (approx, a couple of months from now) Thank you in advance, and don't hesitate to contact me if you have any questions or comments :) Gianluca Bosco [EMAIL PROTECTED] Denmark Technical University Department of manufacturing engineering and management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )