Issue1318

When a file executed with PythonInterpreter.execfile (InputStream,
String) contains the following line at the top:

    from __future__ import with_statement

I get this error:

    ImportError: No module named __future__

If this is executed using the standalone JAR, it works fine.

Maybe there is some other way to enable "future" features when running
scripts this way (i.e. with PythonInterpreter), but then I couldn't find
those.

.py file containing the import statement

As the attached sample shell script demonstrates, simply copying 
jython.jar to another location and pointing the classpath to it will 
work in the following cases:

1.
jython.jar is a standalone jar (which contains the /Lib folder)

2.
jython knows the path to the /Lib folder (using -Dpython.path in the 
example)

Thank you, I was trying to create a small example (I have a failure in a
huge webap), but couldn't reproduce it.

To summarize:

When using jython.jar not containing the /Lib folder, the path to /Lib 
has to be specified.

(Special case: if the classpath points to an installed jython.jar, 
jython guesses the correct path)

However, in my webapp, I can import normal library modules, e.g. 'import
time' succeeds and works fine after that.  I'm confused about what
'python.path' is actually for...

I was only guessing what your problem with __future__ was, and tried to 
build a small example.
Web applications might be different, though.

Are you sure you really can import a module living in a .py file ?
(there is no physical time.py file, jython -v and 'import time' gives:
import: 'time' as org.python.modules.time.Time in builtin modules)

Oh, indeed.  I mostly use Java classes and just a few Python library
modules.  When I try to import a non-builtin module I indeed get the
same ImportError, so yes, Jython is not configured properly...

I guess it's not a bug then?

doublep - thanks for your feedback!
Now closing as 'works for me'.

One small improvement would be to give a more understandable error
message in such cases.  But anyway, works here now.  Thanks!