Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Dima Pasechnik
one way or the other, underlinking does not work on Cygwin. On Friday, June 2, 2017 at 9:54:22 AM UTC+1, Ralf Stephan wrote: > > No. See > https://stackoverflow.com/questions/44322187/binary-using-both-python-c-api-version-2-and-3 > > On Friday, June 2, 2017 at 8:35:57 AM UTC+2, François wrote:

Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Francois Bissey
> On 2/06/2017, at 20:54, Ralf Stephan wrote: > > No. See > https://stackoverflow.com/questions/44322187/binary-using-both-python-c-api-version-2-and-3 So much for that then. This email may be confidential and subject to legal privilege, it may not reflect the views of the

Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Ralf Stephan
No. See https://stackoverflow.com/questions/44322187/binary-using-both-python-c-api-version-2-and-3 On Friday, June 2, 2017 at 8:35:57 AM UTC+2, François wrote: > > > > On 2/06/2017, at 17:57, Ralf Stephan > wrote: > > > > On Thursday, June 1, 2017 at 12:29:23 PM UTC+2,

Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Francois Bissey
> On 2/06/2017, at 17:57, Ralf Stephan wrote: > > On Thursday, June 1, 2017 at 12:29:23 PM UTC+2, François wrote: > .. Installing pynac for both python at the same time > means rethinking its packaging. > > As a possible alternative, would avoiding those calls that differ

Re: [sage-combinat-devel] Re: Crystals not displaying

2017-06-02 Thread Dima Pasechnik
On Friday, June 2, 2017 at 1:16:19 AM UTC+1, Julie Beier wrote: > > Current version of SAGE: 7.5.1 though this happened with several versions, > all binary install > Operating System: OSX 10.11.6 > Version of Tex: Version 3.14159265-2.6-1.40.17 (TeX Live 2016); All > packages up to date > > As

Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Francois Bissey
> On 1/06/2017, at 23:27, Kwankyu Lee wrote: > > I also thought about building both py2+3 at the same time, it would be a > great debugging help during the transition if you can easily run both. Then > in 3 years we'll just cut out the py2 part and be done with it... > >

[sage-devel] why is assume() so slow?

2017-06-02 Thread Stan
I asked this question before on ask.sagemath (https://ask.sagemath.org/question/37744/why-is-assume-so-slow/) but haven't found an answer yet, so perhaps someone here has an idea. Basically, declaring assumptions using `assume()` or within `var('x', domain='real') takes an awful lot of time,

[sage-devel] Re: why is assume() so slow?

2017-06-02 Thread Nils Bruin
On Friday, June 2, 2017 at 6:33:12 AM UTC-6, Stan wrote: > > I asked this question before on ask.sagemath ( > https://ask.sagemath.org/question/37744/why-is-assume-so-slow/) but > haven't found an answer yet, so perhaps someone here has an idea. > > Basically, declaring assumptions using

Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Nils Bruin
On Friday, June 2, 2017 at 2:54:22 AM UTC-6, Ralf Stephan wrote: > > No. See > https://stackoverflow.com/questions/44322187/binary-using-both-python-c-api-version-2-and-3 > > But then we need to either build libraries libpynac2 and libpynac3 or put libpynac somewhere in local/lib/python*. Do we

[sage-devel] Re: transferring sagetex github repo to sagemath?

2017-06-02 Thread Dima Pasechnik
On Friday, June 2, 2017 at 8:29:05 PM UTC+1, Frédéric Chapoton wrote: > > Please, if you are a member of sagemath group on github, do merge the pull > requests #5 and #11 (easy ones) for sagetex > > https://github.com/sagemath/sagetex/pull/11 > https://github.com/sagemath/sagetex/pull/5 >

[sage-devel] Re: transferring sagetex github repo to sagemath?

2017-06-02 Thread Frédéric Chapoton
Please, if you are a member of sagemath group on github, do merge the pull requests #5 and #11 (easy ones) for sagetex https://github.com/sagemath/sagetex/pull/11 https://github.com/sagemath/sagetex/pull/5 Frederic Le mercredi 31 mai 2017 21:52:16 UTC+2, Dima Pasechnik a écrit : > > Hi Dan, >

[sage-devel] escape bug in sparse6 output

2017-06-02 Thread J Kinable
There seems to be a bug in the sparse6 string generator. sage: G=graphs.EllinghamHorton78Graph() sage: G.sparse6_string() ':~?@M_GEA_w?C`WGEaOOGaWWI_OmGBGKL`w}OcXINCxQGCPUWCp]WdPeOEh[Zc`q^Fh}_gXwagyAfGaYfhAa^IYEgIyqlji}ojREqfa{rlbCtljKvjbatMYWv_Jq|hBy{hSAdn{M *\\*OCRAeRtEa_wVlSHBhagjkBgzpCY}OSr'

Re: [sage-devel] Sage Python 3 proposal

2017-06-02 Thread Francois Bissey
> On 3/06/2017, at 05:28, Nils Bruin wrote: > > On Friday, June 2, 2017 at 2:54:22 AM UTC-6, Ralf Stephan wrote: > No. See > https://stackoverflow.com/questions/44322187/binary-using-both-python-c-api-version-2-and-3 > > But then we need to either build libraries libpynac2 and

[sage-devel] Re: why is assume() so slow?

2017-06-02 Thread Ralf Stephan
On Friday, June 2, 2017 at 2:33:12 PM UTC+2, Stan wrote: > > Does anyone know why this is and how this could be accelerated? > It could be accelerated by caching the assumptions and only send them to Maxima before integration/solve/simplification requests. Other usage of assumptions/domains is by