Message10037

I don't understand much of the above, and some of it turned out to be a red herring. Does the following scenario represent the issue? I have a jarred-up the files I used in #2158 (and hidden the original):

> jar tf ulib.jar
META-INF/
META-INF/MANIFEST.MF
u/
u/v/
u/v/w/
u/v/w/x.py
u/v/w/y.py
u/v/w/__init__.py
u/v/y.py
u/v/__init__.py
u/y.py
u/__init__.py

When you invoke x.py, each of these will tell you its path. Now, from 2.7.0+ I get:

> java -cp ulib.jar;%JT%\dist\jython-dev.jar;%JT%\dist\javalib\* org.python.util.jython -c"import u.v.w.x"
Init: u\__init__.py
Init: u\v\__init__.py
Init: u\v\w\__init__.py
File: u\v\w\x.py
File: u\y.py

> java -cp ulib.jar;%JT%\dist\jython-dev.jar;%JT%\dist\javalib\* org.python.util.jython -m u.v.w.x
Init: u\__init__.py
Init: u\v\__init__.py
Init: u\v\w\__init__.py
... stack dump ...
AttributeError: 'ClasspathPyImporter' object has no attribute 'is_package'

The failure of the second one constitutes the issue, and is because our loaders do not implement the "optional" methods that are indispensible to runpy. Right?