On Aug 2, 2:05 pm, John H Palmieri <jhpalmier...@gmail.com> wrote: > On Aug 2, 11:01 am, kcrisman <kcris...@gmail.com> wrote: > > > Great, this is exactly what I had figured was going on now. It is > > very unfortunate that PIL does this. But at any rate I am making sure > > these tickets have that thread referenced, which they currently > > don't. > > > Also, what other effects will SAGE_BINARY_BUILD have on a source > > build? After all, I'm not distributing the binary I make! It would > > be nice to not have to deal with this, but since I don't use PIL it > > doesn't matter that much to me. > > Starting very recently, Sage environment variables are now documented > in the Sage installation guide. See > > <http://sagemath.org/doc/installation/source.html#environment- > variables> > > When I was looking into this, I only found SAGE_BINARY_BUILD in the > pil package, so I think it has no other effect.
Having two environment variables used by only one package seems odd as well ;) Maybe we should just include the libjpeg or whatever - otherwise it's yet another dependency for Sage to test right, though as noted it only impacts my testing, not any use I can think of for me. - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
