Issue991100
Created on 2004-07-14.19:04:49 by xoltar, last changed 2008-12-15.18:54:29 by fwierzbicki.
| msg2383 (view) |
Author: Bryn Keller (xoltar) |
Date: 2004-07-14.19:04:49 |
|
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).
|
| msg2384 (view) |
Author: Samuele Pedroni (pedronis) |
Date: 2005-01-09.20:18:53 |
|
Logged In: YES
user_id=61408
this need to be addressed in the improving java imports
discussion.
|
|
| Date |
User |
Action |
Args |
| 2008-12-15 18:54:29 | fwierzbicki | set | components:
+ Core, - None |
| 2008-11-01 19:06:17 | fwierzbicki | set | nosy:
+ fwierzbicki |
| 2004-07-14 19:04:49 | xoltar | create | |
|