วันพฤหัสบดีที่ 3 สิงหาคม พ.ศ. 2560

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:39:00 หลังเที่ยง

[computer] [computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

[computer] [computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

[computer] Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/03/2560 02:38:00 หลังเที่ยง

Re: [sage-devel] Re: error accessing np.random?

thanks for your replies. i've opened: https://trac.sagemath.org/ticket/23579

El jueves, 3 de agosto de 2017, 16:14:30 (UTC+2), Dima Pasechnik escribió:


On Thursday, August 3, 2017 at 2:56:15 PM UTC+1, vdelecroix wrote:
Does *not* work in console for me (on sage 8.1.beta0). But does in Ipython

$ sage -ipython
In [1]: import numpy as np

In [2]: np.random?

moreover, if works if one does

from sage.all import *

first, so the problem is not really in the sage library, but somewhere where things like sage: prompt is handled, I guess.

 


On 03/08/2017 14:52, Dima Pasechnik wrote:
> by the way, this works (on console):
>
> sage: sage: import numpy as np
> sage: np.random.random?
> Docstring:
> ...
>
>
> So this looks like some ipython/Sage-related thing...
>
> On Thursday, August 3, 2017 at 1:33:27 PM UTC+1, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit :
>>
>>>
>>> could someone confirm the error?
>>>
>>
>>
>> I confirm.
>>  
>>
>>> is it an error on NumPy's or Sage's side? Thanks.
>>>
>>  
>>
>> Maybe on Sage's side: if you run the same thing in a python 2 kernel from
>> sage -n jupyter, you don't get the error.
>>
>> Best wishes,
>>
>> Eric.
>>
>
*

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

วันพุธที่ 2 สิงหาคม พ.ศ. 2560

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] [computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

[computer] Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 8/02/2560 06:27:00 ก่อนเที่ยง

Re: [sage-devel] Re: [sage-packaging] Re: Brainstorming about Sage dependencies from system packages

Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).

When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself?
 
Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

วันจันทร์ที่ 10 กรกฎาคม พ.ศ. 2560

Re: [sage-devel] Re: [ODK participants] Blog post on fast multivariate arithmetic



On Monday, 10 July 2017 17:05:10 UTC+2, vdelecroix wrote:
On 10/07/2017 16:36, 'Bill Hart' via sage-devel wrote:
>> BTW, it would be good to have them in the post!
>>
>
> It already says in the post that for systems that didn't provide the
> required function, I used quotient with remainder.

I meant code snippets.

I suppose that could be useful, but it's a lot of work for little clear benefit (5 systems, 6 benchmarks). The code is pretty much exactly what Ralph wrote, except that I used a for loop for the operation being timed, and timed that. This was the same in all the systems.

I used quo_rem for division with remainder (for the divisibility test with quotient benchmark) and * for multiplication. For quotient only, I don't recall if I used quo_rem or //. It's clear from the timings I didn't use /, and I do recall checking the documentation very carefully for 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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[computer] [computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [ODK participants] Blog post on fast multivariate arithmetic



On Monday, 10 July 2017 13:31:26 UTC+2, vdelecroix wrote:
On 10/07/2017 12:48, mmarco wrote:
> It is surprising the difference between singular and Sage, considering that
> Sage mostly relies on Singular for multivariate polynomial arithmetic. In
> the case of divisions, I suspect that it has to do with the fact that Sage
> treats division of polynomials as an operation in the fraction field, so it
> would construct the fraction, look for common factors in the numerator and
> denominator, and cancel them. That is probably not what other systems do.

Indeed, for (internal) division one should use // and not /

> Which commands/instructions did you use in your benchmarks?

It looks like I used quo_rem, since you need both the quotient and whether or not it is divisible, for which you need the remainder.
 

BTW, it would be good to have them in the post!

It already says in the post that for systems that didn't provide the required function, I used quotient with remainder. 
 

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

[computer] [computer] [computer] [computer] [computer] [computer] [computer] Re: [sage-devel] Re: [ODK participants] Blog post on fast multivariate arithmetic



On Monday, 10 July 2017 13:31:26 UTC+2, vdelecroix wrote:
On 10/07/2017 12:48, mmarco wrote:
> It is surprising the difference between singular and Sage, considering that
> Sage mostly relies on Singular for multivariate polynomial arithmetic. In
> the case of divisions, I suspect that it has to do with the fact that Sage
> treats division of polynomials as an operation in the fraction field, so it
> would construct the fraction, look for common factors in the numerator and
> denominator, and cancel them. That is probably not what other systems do.

Indeed, for (internal) division one should use // and not /

> Which commands/instructions did you use in your benchmarks?

It looks like I used quo_rem, since you need both the quotient and whether or not it is divisible, for which you need the remainder.
 

BTW, it would be good to have them in the post!

It already says in the post that for systems that didn't provide the required function, I used quotient with remainder. 
 

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง

--
เขียนโดย computer ถึง computer เวลา 7/10/2560 07:36:00 ก่อนเที่ยง