> Ok. Why are you using such an old version of Python?
We have dependencies elsewhere in the system that lock us into 2.4
> Not that I think that's the problem - just curious.
Any idea what the problem is? Or what additional diagnostics I can try?
--
A. Heifets
http://www.cs.toronto.edu/~aheife
On Thu, 3 Nov 2011, A. Heifets wrote:
Ok. Why are you using such an old version of Python?
We have dependencies elsewhere in the system that lock us into 2.4
Not that I think that's the problem - just curious.
Any idea what the problem is? Or what additional diagnostics I can try?
You sa
Andi Vajda wrote:
> > Won't specifying "--package javax.imageio" cause all public classes in
> > that package to be wrapped? Seems to work that way for java.awt.image.
>
> No, and it never has. All --package blah does is enable dependencies
> in that package to be wrapped as well. If you list n
I got the build working by changing the import line in
/usr/lib64/python2.4/site-packages/jcc/__init__.py from
import os, sys
to
import os, sys, _jcc
> That's unexpected. JCC should get installed as an egg. For example, on my
> system, its installation dir looks like:
> .../lib/python2.
On Thu, 3 Nov 2011, Bill Janssen wrote:
Andi Vajda wrote:
Won't specifying "--package javax.imageio" cause all public classes in
that package to be wrapped? Seems to work that way for java.awt.image.
No, and it never has. All --package blah does is enable dependencies
in that package to b
On Thu, 3 Nov 2011, A. Heifets wrote:
I got the build working by changing the import line in
/usr/lib64/python2.4/site-packages/jcc/__init__.py from
import os, sys
to
import os, sys, _jcc
That's unexpected. JCC should get installed as an egg. For example, on my
system, its installati
On Thu, 3 Nov 2011, Bill Janssen wrote:
Andi Vajda wrote:
On Thu, 3 Nov 2011, Bill Janssen wrote:
* All classes from either --include jars or the JRE, which already selected
classes depend on, that come from packages included with --package
No. If you --include blah.jar and its pack
