Issue991100

This patch (made against 2.1 final) fixes two problems:

1. When importing from a jar/zip on the PYTHONPATH,
"import foo" will now load foo$py.class from the jar.
Previously foo.py would also have to be present in the
jar, or else foo$py.class would be ignored. Of course
if foo.py is present and newer, that will still be
preferred.

2. As a last resort, "import foo" will use
Py.findClassEx to load a class called "foo$py".
Previously there was no obvious way to load a python
module from the current classpath, unless it had been
compiled to have the name "foo$Py_Inner" (perhaps
Jythonc does it this way, I don't know).

Logged In: YES 
user_id=61408

this need to be addressed in the improving java imports
discussion.

Hi Bryn - this patch is very old and the import mechanism has completely changed since it was submitted. Are you still having an issue and if so are you still interested in seeing a change like this? I'm attempting to address all outstanding patches. I am embarrassed that so many have stagnated for so long...

No need, I haven't used jython in years. You can close this. Thanks for checking.