Any chances of getting review for easy updates of some spkg?
I plan on working on FLINT update, and so on MPIR one, but before doing so,
it would be really nice to get my tiny changes for Cygwin integrated (or at
least positively reviewed and get them in the updated versions of MPIR
spkg).
The
>
> > haven't seen this before, so it might be forking combined with the
> > doctest framework in some way I don't understand.
>
> > Also, the "RuntimeError: ECL says: Module error: Don't know how to
> > REQUIRE MAXIMA" occurs not just in the doctests, but in "real
> > life".
>
> You mean in real l
On Thursday, October 11, 2012 2:59:48 PM UTC+2, kcrisman wrote:
>
>
>
> On Oct 10, 1:51 pm, kcrisman wrote:
> > On Wednesday, October 10, 2012 11:04:43 AM UTC-4, John H Palmieri wrote:
> >
> > > On Wednesday, October 10, 2012 5:31:56 AM UTC-7, kcrisman wrote:
> >
> > >> Incidentally, I can'
On Oct 10, 1:51 pm, kcrisman wrote:
> On Wednesday, October 10, 2012 11:04:43 AM UTC-4, John H Palmieri wrote:
>
> > On Wednesday, October 10, 2012 5:31:56 AM UTC-7, kcrisman wrote:
>
> >> Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
> >> exist, and where is it? Again,
On Wednesday, October 10, 2012 11:04:43 AM UTC-4, John H Palmieri wrote:
>
> On Wednesday, October 10, 2012 5:31:56 AM UTC-7, kcrisman wrote:
>>
>> Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
>> exist, and where is it? Again, a cursory reading of the developer
>> gui
On Wednesday, October 10, 2012 5:31:56 AM UTC-7, kcrisman wrote:
>
> Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
> exist, and where is it? Again, a cursory reading of the developer
> guide doesn't seem to have this info, but it's probably there.
>
When running doctes
Incidentally, I can't find the full test log in SAGE_TESTDIR - does it
exist, and where is it? Again, a cursory reading of the developer
guide doesn't seem to have this info, but it's probably there.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
Just to put this somewhere, here are the tests which failed on my XP
box. I have strong reason to believe these are not at all
independent, but putting them here anyway. Here are two very common
types, both of which I find unsurprising, given "fork" problems on
Cygwin. I also seem to have had is
>From the installation guide:
>
>> SAGE_TESTDIR - a temporary directory used during Sage’s doctesting.
>> The default is to use the directory $DOT_SAGE/tmp, but you can override
>> that by setting this variable.
>>
>> So try setting this environment variable. You could also set DOT_SAGE to
On Friday, October 5, 2012 1:32:34 PM UTC-4, John H Palmieri wrote:
>
>
>
> On Friday, October 5, 2012 10:09:38 AM UTC-7, kcrisman wrote:
>>
>>
>>
>>> User 1@GCO2635 /home/newsagetest/sage-5.4.rc0/devel/sage
>>> $../../sage -t sage/functions/piecewise.py
>>> sage -t "devel/sage-main/sage/function
On Friday, October 5, 2012 10:09:38 AM UTC-7, kcrisman wrote:
>
>
>
>> User 1@GCO2635 /home/newsagetest/sage-5.4.rc0/devel/sage
>> $../../sage -t sage/functions/piecewise.py
>> sage -t "devel/sage-main/sage/functions/piecewise.py"
>> python: can't open file 'home/User': [Errno 2] No such file or
>
> User 1@GCO2635 /home/newsagetest/sage-5.4.rc0/devel/sage
> $../../sage -t sage/functions/piecewise.py
> sage -t "devel/sage-main/sage/functions/piecewise.py"
> python: can't open file 'home/User': [Errno 2] No such file or directory
>
> Apparently sage -t tries to make a temp directory somewh
On Friday, October 5, 2012 12:46:02 PM UTC-4, kcrisman wrote:
>
>
>>> Still couldn't import maxima_lib when it tried to build doc (I only have
>>> the p0 from #13324, so I guess I missed that I should use #9167), and then
>>> it failed anyway with what appears to be a "need to rebase" error. S
>
>
>> Still couldn't import maxima_lib when it tried to build doc (I only have
>> the p0 from #13324, so I guess I missed that I should use #9167), and then
>> it failed anyway with what appears to be a "need to rebase" error. Still,
>> this is good news.
>>
> Yup, for the maxima_lib thingy y
On Friday, October 5, 2012 5:05:10 PM UTC+2, kcrisman wrote:
>
>
>
> On Thursday, October 4, 2012 12:07:27 PM UTC-4, kcrisman wrote:
>>
>>
>> >
>> > Should we continue this conversation in a new thread, or on
>> sage-windows?
>>
>> For now I'll leave it on sage-devel... though this is mainly f
On Thursday, October 4, 2012 12:07:27 PM UTC-4, kcrisman wrote:
>
>
> >
> > Should we continue this conversation in a new thread, or on
> sage-windows?
>
> For now I'll leave it on sage-devel... though this is mainly for JP
> and/or Dima.
>
>
Other than the cvxopt issue, which I'm sure you'r
>
>
Yup, but I got a bunch of such errors, so still strange I did not get
>>> that particular one.
>>> Or maybe the cvxopt spkg was updated in between?
>>>
>> Indeed it was updated in 5.3 and I built 5.2., so this looks fishy.
>>
>
> Yes, in http://trac.sagemath.org/sage_trac/ticket/13160,
On Thursday, October 4, 2012 1:36:27 PM UTC-4, Jean-Pierre Flori wrote:
>
>
>
> On Thursday, October 4, 2012 7:33:02 PM UTC+2, Jean-Pierre Flori wrote:
>>
>>
>> Well, you're not on XP, right? That seems like the right analysis,
>>> though.
>>>
>>> Yup, but I got a bunch of such errors, so still
On Thursday, October 4, 2012 7:33:02 PM UTC+2, Jean-Pierre Flori wrote:
>
>
> Well, you're not on XP, right? That seems like the right analysis, though.
>>
>> Yup, but I got a bunch of such errors, so still strange I did not get
> that particular one.
> Or maybe the cvxopt spkg was updated in b
On Thursday, October 4, 2012 7:15:21 PM UTC+2, kcrisman wrote:
>
>
>
> On Thursday, October 4, 2012 12:52:56 PM UTC-4, Jean-Pierre Flori wrote:
>>
>>
>>
>> On Thursday, October 4, 2012 6:07:27 PM UTC+2, kcrisman wrote:
>>>
>>>
>>> >
>>> > Should we continue this conversation in a new thread, or
On Thursday, October 4, 2012 12:52:56 PM UTC-4, Jean-Pierre Flori wrote:
>
>
>
> On Thursday, October 4, 2012 6:07:27 PM UTC+2, kcrisman wrote:
>>
>>
>> >
>> > Should we continue this conversation in a new thread, or on
>> sage-windows?
>>
>> For now I'll leave it on sage-devel... though this
On Thursday, October 4, 2012 6:07:27 PM UTC+2, kcrisman wrote:
>
>
> >
> > Should we continue this conversation in a new thread, or on
> sage-windows?
>
> For now I'll leave it on sage-devel... though this is mainly for JP
> and/or Dima.
>
> I couldn't get cvxopt to build - Volker's new pack
22 matches
Mail list logo
