Re: [sage-devel] Re: ImportError: The _imaging C module is not installed

2010-08-18 Thread Tim Joseph Dumol
It seems to be a problem with dynamic linking in Mac OS X 10.6. I personally don' t know, since I don't own a Mac. On Wed, Aug 18, 2010 at 10:29 PM, kcrisman wrote: > > > On Aug 18, 9:46 am, Tim Joseph Dumol wrote: >> They are under review as optional packages. In order to become > > Okay, as su

Re: [sage-devel] Re: ImportError: The _imaging C module is not installed

2010-08-18 Thread Tim Joseph Dumol
They are under review as optional packages. In order to become standard packages, they must be voted in here at sage-devel, and must have 2 maintainers (iirc[1]). [1] http://groups.google.com/group/sage-devel/msg/6ea0a0e0a0a2a71a On Wed, Aug 18, 2010 at 8:09 AM, kcrisman wrote: > > > On Aug 17,

Re: [sage-devel] Re: ImportError: The _imaging C module is not installed

2010-08-17 Thread Tim Joseph Dumol
New packages are up at #7344 and #7345 (http://trac.sagemath.org/sage_trac/ticket/7344 and http://trac.sagemath.org/sage_trac/ticket/7345) for review that should hopefully work for all platforms. On Tue, Aug 3, 2010 at 2:31 AM, Tim Joseph Dumol wrote: > Hi, > > SAGE_BINARY_BUILD was introduced as

Re: [sage-devel] Re: ImportError: The _imaging C module is not installed

2010-08-02 Thread Tim Joseph Dumol
Hi, SAGE_BINARY_BUILD was introduced as a compromise when it was decided that libjpeg and libtiff were to be introduced first as optional packages, since PIL is a standard package. Without SAGE_BINARY_BUILD set, binary distributions have PIL link with libjpeg and libtiff as shared libraries, which