Message6426

On Mar 1, 2011, at 9:07 AM, Philip Jenvey wrote:
Philip Jenvey <pjenvey@underboss.org> added the comment:
> My guess is you have a psyco.py file somewhere in your sys.path that is being picked up when you aren't expecting it to be

Hmmmm...  Good thought so I took an extensive look at PATH and sys.path.  No Joy.

Looking then at CLASSPATH I see I had it defined to be ".:..:"  ...a leftover artifact from some testing I did a year or two ago.  When I removed ".." (parent dir) everything worked as expected.

What's curious is the parent dir is a dir of [uninteresting] dirs.  So then how could Java/Jython pick up anything related to psyco with just ".."?  

...unless Jython sets/resets the working directory for some reason and the parent dir at that point has a file with psyco in it.  (I do have such files in various places in my file system but none should be "interesting".)

For now I can get along with CLASSPATH=. but if I or anybody else were to use a relative pathname in their CLASSPATH they could conceivably get unexpected results?  Dunno, just a theory.  

So thank you Philip for the hint.  I'm good-to-go, but this does raise the question: Does Jython/Java change working dirs (internally/on-the-fly) and then use CLASSPATH from that point making relative paths problematic?

Larry