Message5472

Author doublep
Recipients cgroves, doublep, leosoto
Date 2010-02-01.10:33:06
SpamBayes Score 7.8825835e-15
Marked as misclassified No
Message-id <1265020387.85.0.641355633022.issue1216@psf.upfronthosting.co.za>
In-reply-to
Content
> Any reason why using PySystemState#setClassLoader wasn't enough for this use case?

I wasn't even aware of it.

> I'm about to make a case for ignoring the context classloader on the basis that PySystemState's classLoader does a better job

Please don't.  Current Jython just works for me.  You basically want to stop using common idiom in preference of custom solution.  What you will achieve is:
- Jython will _not_ just work for many people out of the box; they will have to actively look for a solution after spending time investigating what's wrong to begin with;
- many people will overlook PySystemState#setClassLoader just as I did.

On the upside you will probably have simpler code inside of Jython.

In the end you will make using Jython harder (mainly due to debugging, not because of one extra statement).  It will also become "less standard" by not using a mechanism already present in Java.

What is the problem with using PySystemState class loader else falling back to thread context class loader?
History
Date User Action Args
2010-02-01 10:33:07doublepsetmessageid: <1265020387.85.0.641355633022.issue1216@psf.upfronthosting.co.za>
2010-02-01 10:33:07doublepsetrecipients: + doublep, cgroves, leosoto
2010-02-01 10:33:07doubleplinkissue1216 messages
2010-02-01 10:33:06doublepcreate