Re: [sage-devel] Re: Definition of multifactorial #5415

[Travis Scrimshaw]

On Wednesday, December 9, 2015 at 4:45:35 PM UTC-6, Nils Bruin wrote:
>
> On Wednesday, December 9, 2015 at 10:21:17 AM UTC-8, prateek sharma wrote:
>>
>> No . The system just says "Newly created local branch..." and processing 
>> keeps on going.
>> I have to forcefully stop the programme. 
>>
>
> It works for me (it does take some time to finish, however. I don't know 
> what it's doing. I'd imagine that any of: speed of local disk access, 
> processor speed, internet speed might affect how long this should take. I'd 
> imagine that if you are not up-to-date on the local develop, it might have 
> quite a bit of downloading to do from trac (I assume that pulling a ticket 
> with a non-existant branch will just pull "develop" on trac.)
>

Doing it directly via git should work really quickly since git is designed 
to be lightweight. See 
http://doc.sagemath.org/html/en/developer/manual_git.html for more.

Best,
Travis

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build failure OS X sage-6.10.beta7 numpy-1.10

[François Bissey]

Works here, and your log definitely indicate ATLAS has been found.
The error message seem to indicate the wrong options are passed
to gfortran to link the shared object. This is probably due to some
confusion in the numpy build system which doesn't expect ATLAS
on OS X.

Francois

On 12/10/15 15:12, François Bissey wrote:

Have you set SAGE_ATLAS_ARCH? Doing so is definitely not supported.
We prefer using the accelerate framework on OS X.
I have just upgraded xcode so I will give it a try.

Francois

On 12/10/15 13:20, Ian Hoffman wrote:

This is my first post (and first time building Sage). I'm using El
Capitan with the latest versions of Xcode (7.2) and command line tools.

I just tried to build Sage and encountered a problem with numpy where
the compiler seems to be looking for some header files and not finding
them. I've attached my log file for reference.

Ian Hoffman

--
You received this message because you are subscribed to the Google
Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.




--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build failure OS X sage-6.10.beta7 numpy-1.10

[François Bissey]

Have you set SAGE_ATLAS_ARCH? Doing so is definitely not supported.
We prefer using the accelerate framework on OS X.
I have just upgraded xcode so I will give it a try.

Francois

On 12/10/15 13:20, Ian Hoffman wrote:

This is my first post (and first time building Sage). I'm using El
Capitan with the latest versions of Xcode (7.2) and command line tools.

I just tried to build Sage and encountered a problem with numpy where
the compiler seems to be looking for some header files and not finding
them. I've attached my log file for reference.

Ian Hoffman

--
You received this message because you are subscribed to the Google
Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Definition of multifactorial #5415

[Nils Bruin]

On Wednesday, December 9, 2015 at 10:21:17 AM UTC-8, prateek sharma wrote:
>
> No . The system just says "Newly created local branch..." and processing 
> keeps on going.
> I have to forcefully stop the programme. 
>

It works for me (it does take some time to finish, however. I don't know 
what it's doing. I'd imagine that any of: speed of local disk access, 
processor speed, internet speed might affect how long this should take. I'd 
imagine that if you are not up-to-date on the local develop, it might have 
quite a bit of downloading to do from trac (I assume that pulling a ticket 
with a non-existant branch will just pull "develop" on trac.)

I've pushed the branch there now. Perhaps that helps you along? Otherwise, 
you could try setting up a sage branch from scratch, following the docs. 
Perhaps that gets things working for you. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] BUG: segfault in 6.10.beta7

[John Cremona]

On 9 December 2015 at 19:47, Jeroen Demeyer  wrote:
> I added this to
> http://trac.sagemath.org/ticket/18639

Thanks.  I had forgotten all about that one.

>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] BUG: segfault in 6.10.beta7

[Jeroen Demeyer]

I added this to
http://trac.sagemath.org/ticket/18639

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] BUG: segfault in 6.10.beta7

[John Cremona]

Can we bring this thread back to topic?  An innocent sage statement
causes as segfault, and that is a Bad Thing.

John

On 9 December 2015 at 19:41, Dima Pasechnik  wrote:
>
>
> On Wednesday, 9 December 2015 16:36:05 UTC, John Cremona wrote:
>>
>> On 9 December 2015 at 16:28, Nathann Cohen  wrote:
>> >> Try this (6.10.beta7):
>> >
>> > This concept of a zero in mathematics is fishy. There is not any of
>> > our troubles that cannot be traced back to it.
>> >
>> > +1 for the removal of 0 in Sage.
>>
>> Nice try, Nathann!  I will obey, and indeed will remove nothing from Sage.
>
>
> perhaps even better would be to remove all the negative stuff from Sage, so
> that only positive vibes
> remain...
>
>>
>>
>> Meanwhile I dusted off my algebraic number theory 101 and replaced
>>
>> if three.divides(a1):
>>
>> with
>>
>> if not a1 in three:
>>
>> but I.divides(a) should work whenever I is a fractional ideal of a
>> number field and a is an element of the field.
>>
>> Note that this is not just some error but a *segfault* so indicates
>> something more serious.
>>
>> John
>>
>>
>>
>> >
>> > Nathann
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "sage-devel" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to sage-devel+...@googlegroups.com.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > Visit this group at http://groups.google.com/group/sage-devel.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] BUG: segfault in 6.10.beta7

[Dima Pasechnik]

On Wednesday, 9 December 2015 16:36:05 UTC, John Cremona wrote:
>
> On 9 December 2015 at 16:28, Nathann Cohen  > wrote: 
> >> Try this (6.10.beta7): 
> > 
> > This concept of a zero in mathematics is fishy. There is not any of 
> > our troubles that cannot be traced back to it. 
> > 
> > +1 for the removal of 0 in Sage. 
>
> Nice try, Nathann!  I will obey, and indeed will remove nothing from Sage. 
>

perhaps even better would be to remove all the negative stuff from Sage, so 
that only positive vibes
remain...
 

>
> Meanwhile I dusted off my algebraic number theory 101 and replaced 
>
> if three.divides(a1): 
>
> with 
>
> if not a1 in three: 
>
> but I.divides(a) should work whenever I is a fractional ideal of a 
> number field and a is an element of the field. 
>
> Note that this is not just some error but a *segfault* so indicates 
> something more serious. 
>
> John 
>
>
>
> > 
> > Nathann 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-devel+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: floating point (xeon/gentoo only?) weirdness with cvxopt ('sage' vs 'sage --python' difference)

[Dima Pasechnik]

On Wednesday, 9 December 2015 16:51:45 UTC, Volker Braun wrote:
>
> Can you compare the floating point rounding modes at entry and exit of 
> solvers.sdp?
>

I cannot reproduce it anymore. I don't know, I ran 

sage: from decimal import getcontext
sage: getcontext()
Context(prec=28, rounding=ROUND_HALF_EVEN, Emin=-9, Emax=9, 
capitals=1, flags=[], traps=[DivisionByZero, Overflow, InvalidOperation])

and the same in Sage's Python --- the only difference was the order of 
entries in traps[]. (The order of these things appears to be sort of 
random, on another
machine I tried, too)

And then this chunk of code started to work in Sage, just like this.
(I tried to get another copy of Sage, and it still worked)
Cosmic rays? Dying hardware? No idea...

Dima



 

>
>
> On Wednesday, December 9, 2015 at 5:04:45 PM UTC+1, Dima Pasechnik wrote:
>>
>> Are floating point settings (some low level flags???)
>> subtly different for Sage's Python and Sage itself? Namely, the same code 
>> succeeds or fails, depending on whether
>> it is invoked in Sage's Python, or in Sage proper (with preparser(False)).
>>
>> It is an iterative procedure (call to solvers.sdp() below)  that for 
>> first few steps behaves identically, but then there is divergence - it 
>> completes correctly in Python, but fails, after many
>> iterations,  in Sage.  I can only reproduce it on a Xeon machine running 
>> Gentoo Linux (the sage4 patchbot at U.Ghent). This was 1st uncovered while
>> testing #16929. 
>>
>> Here is the complete code (in Sage you also need preparser(False) first).
>>
>> 
>> from cvxopt import matrix, solvers
>> c = matrix([1.,-1.])
>> G =  [ matrix([[1., 2., 2., 3.],   [3., 4., 4., 5.]]) ]
>> G += [ matrix([[1., 1., 1., 1.], [2., 2., 2., 2.]]) ]
>> G += [ matrix([[-1.],  [0.]]) ]
>> G += [ matrix([[0.],  [-1.]]) ]
>> h =  [ matrix([[5., 6.], [6., 7.]]) ]
>> h += [ matrix([[3., 3.], [3., 3.]]) ]
>> h += [ matrix([[0.]]) ]
>> h += [ matrix([[0.]]) ]
>> sol = solvers.sdp(c, Gs=G, hs=h)
>> print(sol['x'])
>> ##
>> # in sage I get 'Terminated (maximum number of iterations reached).' 
>> (after 100 iterations)
>> # in sage --python I get 'Optimal solution found.' (after 26 iterations)
>> # divergence happens around iteration 17 or 18
>> # 
>>
>> Thanks,
>> Dima
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Definition of multifactorial #5415

[prateek sharma]

On Wednesday, December 9, 2015 at 10:55:18 PM UTC+5:30, Nils Bruin wrote:
>
> On Wednesday, December 9, 2015 at 5:13:58 AM UTC-8, prateek sharma wrote:
>>
>> Can you tell me how can I create a branch .When I do git-trac-checkout 
>> 5415
>> It says "Newly created local branch: t/5415/problems_with_multifactorial_"
>>
>  
>
Doesn't the system just tell you that you have now succeeded in creating a 
> (local) branch?
>
No . The system just says "Newly created local branch..." and processing 
keeps on going.
I have to forcefully stop the programme. 

>
>  
>>
> I have made my changes on git.
>>
>
> Does that mean that you have followed the instructions 
> http://doc.sagemath.org/html/en/developer/git_trac.html#making-changes ? 
> or do you mean "my changes are sitting on github"? The documentation will 
> tell you how to commit changes to your local branch
>  
>
>> How can I commit those changes on trac.
>>
>
> Do you mean "How do I push those changes to a remote branch on trac 
> attached to the ticket?", That's described in the next section, 
> http://doc.sagemath.org/html/en/developer/git_trac.html#uploading-changes-to-trac
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Definition of multifactorial #5415

[Nils Bruin]

On Wednesday, December 9, 2015 at 5:13:58 AM UTC-8, prateek sharma wrote:
>
> Can you tell me how can I create a branch .When I do git-trac-checkout 5415
> It says "Newly created local branch: t/5415/problems_with_multifactorial_"
>

Doesn't the system just tell you that you have now succeeded in creating a 
(local) branch? 

>  
>
I have made my changes on git.
>

Does that mean that you have followed the instructions 
http://doc.sagemath.org/html/en/developer/git_trac.html#making-changes ? or 
do you mean "my changes are sitting on github"? The documentation will tell 
you how to commit changes to your local branch
 

> How can I commit those changes on trac.
>

Do you mean "How do I push those changes to a remote branch on trac 
attached to the ticket?", That's described in the next section, 
http://doc.sagemath.org/html/en/developer/git_trac.html#uploading-changes-to-trac
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: floating point (xeon/gentoo only?) weirdness with cvxopt ('sage' vs 'sage --python' difference)

[Volker Braun]

Can you compare the floating point rounding modes at entry and exit of 
solvers.sdp?


On Wednesday, December 9, 2015 at 5:04:45 PM UTC+1, Dima Pasechnik wrote:
>
> Are floating point settings (some low level flags???)
> subtly different for Sage's Python and Sage itself? Namely, the same code 
> succeeds or fails, depending on whether
> it is invoked in Sage's Python, or in Sage proper (with preparser(False)).
>
> It is an iterative procedure (call to solvers.sdp() below)  that for first 
> few steps behaves identically, but then there is divergence - it completes 
> correctly in Python, but fails, after many
> iterations,  in Sage.  I can only reproduce it on a Xeon machine running 
> Gentoo Linux (the sage4 patchbot at U.Ghent). This was 1st uncovered while
> testing #16929. 
>
> Here is the complete code (in Sage you also need preparser(False) first).
>
> 
> from cvxopt import matrix, solvers
> c = matrix([1.,-1.])
> G =  [ matrix([[1., 2., 2., 3.],   [3., 4., 4., 5.]]) ]
> G += [ matrix([[1., 1., 1., 1.], [2., 2., 2., 2.]]) ]
> G += [ matrix([[-1.],  [0.]]) ]
> G += [ matrix([[0.],  [-1.]]) ]
> h =  [ matrix([[5., 6.], [6., 7.]]) ]
> h += [ matrix([[3., 3.], [3., 3.]]) ]
> h += [ matrix([[0.]]) ]
> h += [ matrix([[0.]]) ]
> sol = solvers.sdp(c, Gs=G, hs=h)
> print(sol['x'])
> ##
> # in sage I get 'Terminated (maximum number of iterations reached).' 
> (after 100 iterations)
> # in sage --python I get 'Optimal solution found.' (after 26 iterations)
> # divergence happens around iteration 17 or 18
> # 
>
> Thanks,
> Dima
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] BUG: segfault in 6.10.beta7

[John Cremona]

On 9 December 2015 at 16:28, Nathann Cohen  wrote:
>> Try this (6.10.beta7):
>
> This concept of a zero in mathematics is fishy. There is not any of
> our troubles that cannot be traced back to it.
>
> +1 for the removal of 0 in Sage.

Nice try, Nathann!  I will obey, and indeed will remove nothing from Sage.

Meanwhile I dusted off my algebraic number theory 101 and replaced

if three.divides(a1):

with

if not a1 in three:

but I.divides(a) should work whenever I is a fractional ideal of a
number field and a is an element of the field.

Note that this is not just some error but a *segfault* so indicates
something more serious.

John



>
> Nathann
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] BUG: segfault in 6.10.beta7

[Nathann Cohen]

> Try this (6.10.beta7):

This concept of a zero in mathematics is fishy. There is not any of
our troubles that cannot be traced back to it.

+1 for the removal of 0 in Sage.

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] BUG: segfault in 6.10.beta7

[John Cremona]

Try this (6.10.beta7):

sage: K. = NumberField(x^2-15)
sage: three = K.ideal(3)
sage: zero = K(0)
sage: three.divides(zero)

...

Saved trace to /home/jec/.sage/crash_logs/sage_crash_hnuaJL.log

Unhandled SIGSEGV: A segmentation fault occurred in Sage.
This probably occurred because a *compiled* component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Sage will now terminate.

Segmentation fault (core dumped)

The log file is empty.   In fact

sage: zero/three

causes the fault.

John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] floating point (xeon/gentoo only?) weirdness with cvxopt ('sage' vs 'sage --python' difference)

[Dima Pasechnik]

Are floating point settings (some low level flags???)
subtly different for Sage's Python and Sage itself? Namely, the same code 
succeeds or fails, depending on whether
it is invoked in Sage's Python, or in Sage proper (with preparser(False)).

It is an iterative procedure (call to solvers.sdp() below)  that for first 
few steps behaves identically, but then there is divergence - it completes 
correctly in Python, but fails, after many
iterations,  in Sage.  I can only reproduce it on a Xeon machine running 
Gentoo Linux (the sage4 patchbot at U.Ghent). This was 1st uncovered while
testing #16929. 

Here is the complete code (in Sage you also need preparser(False) first).


from cvxopt import matrix, solvers
c = matrix([1.,-1.])
G =  [ matrix([[1., 2., 2., 3.],   [3., 4., 4., 5.]]) ]
G += [ matrix([[1., 1., 1., 1.], [2., 2., 2., 2.]]) ]
G += [ matrix([[-1.],  [0.]]) ]
G += [ matrix([[0.],  [-1.]]) ]
h =  [ matrix([[5., 6.], [6., 7.]]) ]
h += [ matrix([[3., 3.], [3., 3.]]) ]
h += [ matrix([[0.]]) ]
h += [ matrix([[0.]]) ]
sol = solvers.sdp(c, Gs=G, hs=h)
print(sol['x'])
##
# in sage I get 'Terminated (maximum number of iterations reached).' (after 
100 iterations)
# in sage --python I get 'Optimal solution found.' (after 26 iterations)
# divergence happens around iteration 17 or 18
# 

Thanks,
Dima


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage4 patchbot failure on #16929

[Dima Pasechnik]

On Wednesday, 9 December 2015 13:33:48 UTC, Frédéric Chapoton wrote:
>
> Hello,
>
> what error do you see exactly ? The latest branch is reported as "pending" 
> by two bots. If this persists, this could be because
> it is deemed unsafe by the bots. This happens when files are modified 
> outside of src/sage (or a few other allowed dirs). Did you introduce the 
> change in module_list in the last commit ?
>
> it was OK. My last commit changes src/sage/numeric/all.py, making most 
imports there lazy.

One way or another, it is totally different issue from the one I need to 
resolve, some floating point weirdness (see my other post here, soon).

Dima

 

> Frederic
>
> Le mardi 8 décembre 2015 16:42:10 UTC-5, Dima Pasechnik a écrit :
>>
>> I get a strange patchbot sage4 failure here: 
>> patchbot.sagemath.org/ticket/16929/
>> Looks like this is gentoo-specific. 
>> Jeroen, could you perhaps have a look at it offline and send me the 
>> detailed log, or
>> arrange for a login for me?
>>
>> Dima
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Definition of multifactorial #5415

[John Cremona]

On 9 December 2015 at 13:13, prateek sharma
 wrote:
> Can you tell me how can I create a branch .When I do git-trac-checkout 5415
> It says "Newly created local branch: t/5415/problems_with_multifactorial_"
> I have made my changes on git.How can I commit those changes on trac.
> Please help.

This is all explained in great detail in the developers guide -- have
you read that?  You can ask again here if that is not clear in any
way.

>
>
> On Tuesday, December 8, 2015 at 10:14:09 PM UTC+5:30, Nils Bruin wrote:
>>
>> On Tuesday, December 8, 2015 at 5:56:36 AM UTC-8, prateek sharma wrote:
>>>
>>> Can you please summarize me what I basically need to do?
>>>
>>
>> Read this:
>>
>> http://doc.sagemath.org/html/en/developer/
>>
>> and follow the workflow there to push a branch incorporating your changes
>> to trac.sagemath.org.
>> The sage development workflow doesn't currently involve "pull requests" on
>> github. Instead, you should make sure there's a branch on trac.sagemath.org
>> and that that branch is registered on the relevant ticket. Then a potential
>> reviewer knows where to find the code to be reviewed.
>>
>> The "git-trac" command (documented there) helps performing a lot of the
>> required steps. If you're more comfortable with using git directly then "git
>> the hard way" might be useful doc.
>>
>> Make sure you read "Sage Development Process" and "Sage Trac and tickets".
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage4 patchbot failure on #16929

[Frédéric Chapoton]

Hello,

what error do you see exactly ? The latest branch is reported as "pending" 
by two bots. If this persists, this could be because
it is deemed unsafe by the bots. This happens when files are modified 
outside of src/sage (or a few other allowed dirs). Did you introduce the 
change in module_list in the last commit ?

Frederic

Le mardi 8 décembre 2015 16:42:10 UTC-5, Dima Pasechnik a écrit :
>
> I get a strange patchbot sage4 failure here: 
> patchbot.sagemath.org/ticket/16929/
> Looks like this is gentoo-specific. 
> Jeroen, could you perhaps have a look at it offline and send me the 
> detailed log, or
> arrange for a login for me?
>
> Dima
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Definition of multifactorial #5415

[prateek sharma]

Can you tell me how can I create a branch .When I do git-trac-checkout 5415
It says "Newly created local branch: t/5415/problems_with_multifactorial_"
I have made my changes on git.How can I commit those changes on trac.
Please help.

On Tuesday, December 8, 2015 at 10:14:09 PM UTC+5:30, Nils Bruin wrote:
>
> On Tuesday, December 8, 2015 at 5:56:36 AM UTC-8, prateek sharma wrote:
>>
>> Can you please summarize me what I basically need to do?
>>
>>
> Read this:
>  
> http://doc.sagemath.org/html/en/developer/ 
>
> and follow the workflow there to push a branch incorporating your changes 
> to trac.sagemath.org.
> The sage development workflow doesn't currently involve "pull requests" on 
> github. Instead, you should make sure there's a branch on 
> trac.sagemath.org and that that branch is registered on the relevant 
> ticket. Then a potential reviewer knows where to find the code to be 
> reviewed.
>
> The "git-trac" command (documented there) helps performing a lot of the 
> required steps. If you're more comfortable with using git directly then 
> "git the hard way" might be useful doc.
>
> Make sure you read "Sage Development Process" and "Sage Trac and tickets".
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] subs semantic

[Johan S . R . Nielsen]

Hi,

+1, that seems to make sense, and it's a good idea to have both
semantics available.

Note that there are also complicated mixes:

sage: R. = RR[]
sage: Zxy = PolynomialRing(ZZ,'x,y,z')
sage: xx,yy,zz = Zxy.gens()
sage: (xx+yy).subs(x=x).parent()
Multivariate Polynomial Ring in x, y, z over Real Field with 53 bits of 
precision
sage: (xx+yy)(x=x).parent()
Multivariate Polynomial Ring in x, y, z over Real Field with 53 bits of 
precision

Your proposal is that the latter should only be RR[x,y], I guess?

Best,
Johan


Jonas Jermann writes:

> Hi
>
> +1 by me.
> How is the order of variables for "call" determined?
> How would this work for SR?
>
>
> Regards
> Jonas
>
> On 06.12.2015 15:24, Vincent Delecroix wrote:
>> Hello,
>>
>> We have substitution available for various objects (e.g. matrices when
>> the base ring is a polynomial ring). I would like to fix the conventions
>> of the parent of
>>
>>   my_object.subs(var1=val1, var2=val2)
>>
>> versus
>>
>>   my_object(var1=val1, var2=val2)
>>
>> With .subs, univariate polynomial ring somehow chooses the "minimal ring"
>>
>>  sage: R. = ZZ[]
>>  sage: (x+3).subs(x=2).parent()
>>  Integer Ring
>>  sage: (x+3).subs(x=x+4).parent()
>>  Univariate Polynomial Ring in x over Integer Ring
>>  sage: (x+3).subs(x=4.).parent()
>>  Real Field with 53 bits of precision
>>
>> Whereas multivariate are somehow "undecided"
>>
>>  sage: (x+3).subs(x=2).parent()
>>  Multivariate Polynomial Ring in x, y over Integer Ring
>>  sage: (x+3).subs(x=x+4).parent()
>>  Multivariate Polynomial Ring in x, y over Integer Ring
>>  sage: (x+3).subs(x=4.).parent()
>>  Real Field with 53 bits of precision
>>
>> Whereas the symbolic ring is as always a black hole
>>
>>  sage: x = SR('x')
>>  sage: x.subs(x=3.).parent()
>>  Symbolic Ring
>>  sage: x(x=3.).parent()
>>  Symbolic Ring
>>
>> My proposition is:
>>
>>   - .subs should be considered as an *internal* operation. Hence, the
>> result will always be in the same parent (or the result of a pushout).
>> In particular we would have
>>
>>  sage: R. = ZZ[]
>>  sage: x.subs(x=4).parent()
>>  Univariate Polynomial Ring in x over Integer Ring
>>  sage: x.subs(x=4.).parent()
>>  Univariate Polynomial Ring in x over Real Double Field
>>
>> - __call__ is considered as an external operation. The result should
>> (more or less) be the smallest parent in which the result belong.
>>
>>  sage: R. = ZZ[]
>>  sage: x(3,5).parent()
>>  Integer Ring
>>  sage: (x+y)(3., polygen(ZZ))
>>  Univariate Polynomial Ring in x over Real Field with 53 bits of
>> precision
>>
>> Does it look reasonable?
>>
>> Best,
>> Vincent
>>

-- 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: OSX binaries (including El Capitan)

[Volker Braun]

If its not too much effort I'd prefer a note that says that you need
sage-6.10 for El Capitan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: OSX binaries (including El Capitan)

[Harald Schilly]

On Wed, Dec 9, 2015 at 9:51 AM, Volker Braun  wrote:
> Harald, do you want to do that?

Yes, also, the website itself needs to be changed. Should I remove
that warning entirely?

-- harald

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: OSX binaries (including El Capitan)

[Volker Braun]

We could change the "Currently, SageMath does not work on the new OS X 
10.11!" message on http://files.sagemath.org/osx/intel/index.html

Harald, do you want to do that?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] OSX binaries (including El Capitan)

[Volker Braun]

This is a new beta release for the new OSX binaries, available at

http://files.sagemath.org/osx/intel/index.html

This should now work just like the old binaries; When you start it the 
first time the paths are automatically patched for the new location, but 
you do not have to run any special script. The only difference is that the 
Sage binary can now only be installed/relocated once, and that it works on 
OSX 10.11

The normal (commandline) sage binaries are available as (does anybody 
prefer tar.bz2 over dmg format?)

sage-6.10.beta7-OSX_10.11.1-x86_64.tar.bz2
sage-6.10.beta7-OSX_10.11.1-x86_64.dmg

and the Mac App is

sage-6.10.beta7-OSX_10.11.1-x86_64.app.dmg

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.