yes, thanks.
On Aug 10, 3:56 pm, "Justin C. Walker" wrote:
> On Aug 10, 2010, at 06:25 , kcrisman wrote:
>
> > On Aug 9, 9:58 pm, "Justin C. Walker" wrote:
> >> On Aug 7, 2010, at 17:26 , kcrisman wrote:
> [snip]
> >> Turns out I took part in that thread :-}
>
> >> Just tried the suggested "fix"
On Aug 10, 2010, at 06:25 , kcrisman wrote:
On Aug 9, 9:58 pm, "Justin C. Walker" wrote:
On Aug 7, 2010, at 17:26 , kcrisman wrote:
[snip]
Turns out I took part in that thread :-}
Just tried the suggested "fix", and it worked. Note that, for me,
the
problems occur on 10.5, not 10.6.
On Aug 9, 9:58 pm, "Justin C. Walker" wrote:
> On Aug 7, 2010, at 17:26 , kcrisman wrote:
>
>
>
>
>
>
>
> >> Upgraded from .rc1 which was in turn upgraded from .rc0, on Mac OS X,
> >> 10.5.8 (Dual Quad Xeon), w/o problems.
>
> >> One test failed (ptestlong):
> >> devel/sage/sage/plot/plot3d
On Aug 7, 2010, at 17:26 , kcrisman wrote:
Upgraded from .rc1 which was in turn upgraded from .rc0, on Mac OS X,
10.5.8 (Dual Quad Xeon), w/o problems.
One test failed (ptestlong):
devel/sage/sage/plot/plot3d/base.pyx
4 instances of "_imaging C module is not installed".
Try a searc
> Upgraded from .rc1 which was in turn upgraded from .rc0, on Mac OS X,
> 10.5.8 (Dual Quad Xeon), w/o problems.
>
> One test failed (ptestlong):
> devel/sage/sage/plot/plot3d/base.pyx
>
> 4 instances of "_imaging C module is not installed".
>
Try a search for "imaging C module not instal
