Message3992

I implemented this as a PEP 302 hook in r5815 on trunk. It uses
getResourceAsStream on the classloader on sys or on the context class
loader if that one doesn't find anything. Instead of using a jar: prefix
to find things, it picks up on __pyclasspath__ entries in sys.path to
decide what level to import from in the classpath, like the
__classpath__ entry used by the Java importer. I think this should do
what you want and get your applets going, but I'd appreciate it if you'd
check.

By default __pyclasspath__ is added to sys.path, so .py and $py.class
files directly on the classpath will be loaded.  If you have them in a
Lib directory in your jar, you'll want to replace __pyclasspath__ with
__pyclasspath__/Lib.