On Tue, Aug 25, 2009 at 12:40 AM, Leo Soto M. <leo.soto@gmail.com> wrote:
Marc, Oti: Thanks for your feedback. I definitely was a bit lost on
the use cases for PySystemState#classLoader and you saved me a lot of
time.

So, from this two use cases contract seems to be that the provided
class loader should take full control of loading Java classes
referenced from Python code, disabling any builtin strategy (such as
searching classes on sys.path).

That is correct.
 

And the purpose, expressed in generic terms, would be (a) to allow
Jython users to customize the way in which Java classes are loaded
without loading Jython itself with the customized class loader (Marc's
case)

As is that.

(I wouldn't want to give the impression of understanding the Jython classloader architecture. Any knowledge that precipitated my setClassLoader call was shed to make room for the next bug some time ago. All this makes me glad that you are poking at it.) 

I'll try to holler as soon as anything of ours breaks --- let me know if there's anything I should be testing against.

Marc.