From: Charlie G. <cha...@gm...> - 2007-02-18 06:11:19
|
Hmm, then I'm at a loss as to why this is happening. I can't reproduce it. Could you send me the SAS package so I can try to catch it in the act? Charlie On 2/16/07, Alan Field <Ala...@sa...> wrote: > Charlie, > > I don't think the '' entry is causing this problem, because then the import would fail if my package was in the Lib directory. If I insert my package directory in sys.path, the import does not fail until the entry is inserted after the "__classpath__" entry. This problem is also not just a name clash. If I rename the directory from "SAS" to "SASFull", then the import still fails if it is after the "__classpath__" entry. > > Thanks, > Alan > > > -----Original Message----- > From: Charlie Groves [mailto:cha...@gm...] > Sent: Fri 2/16/2007 1:05 AM > To: Alan Field > Cc: jython users > Subject: Re: Problems with import and Jython 2.2 Beta1... > > On 2/15/07, Alan Field <Ala...@sa...> wrote: > > This is the output from sys.path: > > >>> sys.path > > ['C:\\SASJythonPackage', '', 'C:\\jython2.2b1', 'C:\\jython2.2b1\\Lib', '__classpath__'] > > > > How do I read the value of __classpath__? > > __classpath__ is just an entry for Jython's classloader import hook to > try at that point. It's what jython uses to figure out when to try > and load something from the classpath. > > Do you have anything in the directory you're running from with SAS in > it? That's what '' specifies, and it seems like the only thing left > to check. > > Charlie > > |