[Python-bugs-list] [ python-Bugs-778964 ] parameter confusion in 2.3c2

[SourceForge.net]

Bugs item #778964, was opened at 2003-07-28 10:47
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=778964&group_id=5470

Category: Python Interpreter Core
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Bill la Forge (blaforge)
Assigned to: Nobody/Anonymous (nobody)
Summary: parameter confusion in 2.3c2

Initial Comment:
class crjentPje(PJE):
    def __init__
(self,uuri,headline,actorName,jentProxy,lelProxy=None,p
op='',op='',jelType='L1PJENT.PJENT',ts='NoName'):
        Cache.PJE.__init__(self,uuri,actorName,'*',pop+' 
|'+headline+'|',ts=ts)

class StartOfJel(PJE):
    def __init__
(self,uuri,jelName,actorName,partOfProxy=None,jelType
='L1JelTypes.JEL',ts='NoName'):
        Cache.PJE.__init__
(self,uuri,actorName,'`','StartOfJel',ts=ts)
        self['*JelName']=jelName
        self['*JelType']=jelType
        if partOfProxy:
            self['*PartOf']=partOfProxy.uuri

About 1 time in 10 when running 2.3c2, when creating 
a StartOfJel, the partOfProxy ended up being passed as 
the uuri parameter to crjentPje!!! (I was passing None 
as the value for the uuri parameter.)

The problem vanishes when I fall back to 2.2.


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-07-29 00:39

Message:
Logged In: YES 
user_id=12800

The most important thing right now is to get an isolated,
runnable script that we can use to try to reproduce the
problem.  Without this, we're at a loss, and time is rapidly
running out for us to be able to do anything for Python 2.3
final (if it hasn't already run out).


----------------------------------------------------------------------

Comment By: Bill la Forge (blaforge)
Date: 2003-07-29 00:31

Message:
Logged In: YES 
user_id=22406

Bad news.

I'm running 2000 with service pack 3. I moved the code to 
another 2000 system (with no service pack). Code still runs 
under 2.2 but not under 2.3. ;-(

blaforge

----------------------------------------------------------------------

Comment By: Bill la Forge (blaforge)
Date: 2003-07-28 23:06

Message:
Logged In: YES 
user_id=22406

I'm running MS Windows 2000 and did the standard python 
windows install. So you can't blame my build! Its real.

And yes, this is a pretty basic flaw, and intermittent at that!
(about 1 out of ten runs failing.)

I'll see what I can do about isolation. (Being in India has its 
advantages.)

My guess is that a small change to the signiture will fix this, 
which doesn't help anyone else, as this bug will likely haunt 
2.3 if not caught.

blaforge

----------------------------------------------------------------------

Comment By: Jack Jansen (jackjansen)
Date: 2003-07-28 11:15

Message:
Logged In: YES 
user_id=45365

My gut feeling says that if something this basic isn't working there 
is probably something in your setup wrong, or something in the 
way you built Python, or some such. The reasoning behind this is 
that something so essential as parameters being mixed up would 
have shown up earlier.

But: there is also the possibility that you have found a genuine 
bug, and then it is very serious. Unfortunately the bug report as it 
is now doesn't allow for easy duplication. We can try if you can 
provide the following:
- an isolated runnable script that shows the problem
- exact details on your Python version, OS version, any other 
details that may be pertinent
- a recipy for running the script to see the problems.

As Python 2.3 is scheduled for tomorrow there is a bit of a hurry 
here...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=778964&group_id=5470