> Accepted strategy? It doesn't seem very portable. It assumes that
> everyone puts their library
> modules in the exact same place. Or do they just figure that changing
> the sys.path.append
> line is easy enough?
Portability has nothing to do with it. If you arrange your project in a way
that th
Diez B. Roggisch wrote:
> >> Maybe Jython expert has the perfect answer but til then.
> >>
> >> Did you try:
> >>
> >> sys.path.append('path to search')
> >>
> >> Usually this works if nothing else does.
> >>
> >> -Larry
> >
> > Thanks. That's a good workaround, but I would like to know the
> > "
Russ wrote:
> On Feb 21, 4:15 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
>> Russ wrote:
>> > I have a Python program that I want to run in Jython so I can get Java
>> > bytecode output. The program runs fine in Python, but when I change
>> > the first line of the main program to make it run in Jyt
On Feb 21, 4:15 pm, Larry Bates <[EMAIL PROTECTED]> wrote:
> Russ wrote:
> > I have a Python program that I want to run in Jython so I can get Java
> > bytecode output. The program runs fine in Python, but when I change
> > the first line of the main program to make it run in Jython, it fails
> > t
Russ wrote:
> I have a Python program that I want to run in Jython so I can get Java
> bytecode output. The program runs fine in Python, but when I change
> the first line of the main program to make it run in Jython, it fails
> to find some of the imported modules. These are just plain Python
> im
I have a Python program that I want to run in Jython so I can get Java
bytecode output. The program runs fine in Python, but when I change
the first line of the main program to make it run in Jython, it fails
to find some of the imported modules. These are just plain Python
imports of code I wrote
