Re: [sage-devel] Re: Trac slow

On Thursday, April 20, 2017 at 4:04:19 PM UTC+1, Erik Bray wrote: > > On Thu, Apr 20, 2017 at 4:54 PM, Dima Pasechnik > wrote: > > > > > > On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote: > >> > >> Just posting to say I've noticed and am investigating.

[sage-devel] How about moving the AUTHORS section to the last?

Hi all, In the ticket https://trac.sagemath.org/ticket/22847 I introduced a change that could be controversial. I propose to move the AUTHORS section to the last of the heading: r""" EXAMPLES:: AUTHORS: - YOUR NAME (2005-01-03): initial version - person (date in ISO year-month-day

Re: [sage-devel] Re: Trac slow

Hi, On Thu, Apr 20, 2017 at 12:10:42PM -0700, Dima Pasechnik wrote: > > > > Strange, well, I created a firewall rule blocking that IP for now and > > everything seems to be fine. > > > > Does this mean that we need some robots.txt somewhere, perhaps after some > restructuring, > which would

[sage-devel] RR, coercion of numpy.float32() and clang - coercion experts needed

see https://trac.sagemath.org/ticket/22799 : polynomials with numpy coefficients strike again, this time if you build Sage with clang: sage: import numpy as np sage: x=polygen(RR)# this is problematic sage: y=polygen(RDF) # this works fine sage: np.float('1.5')*x 1.50*x

Re: [sage-devel] Re: Trac slow

On Thu, Apr 20, 2017 at 4:54 PM, Dima Pasechnik wrote: > > > On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote: >> >> Just posting to say I've noticed and am investigating. >> >> It seems that somebody is performing a scrape of the front page which >> includes a

[sage-devel] Re: ulimit issues and IPython 5.0

Not sure if this is related, but one thing that goes wrong with the upgrade to IPython 5.0 is that multiline output gets an extraneous blank line, for example instead of sage: identity_matrix(2) [1 0] [0 1] we get sage: identity_matrix(2) [1 0] [0 1] This is solved in

[sage-devel] Trac slow

Just posting to say I've noticed and am investigating. It seems that somebody is performing a scrape of the front page which includes a list of users on the site [1] each of which is a link to a search query for all tickets and wiki pages associated with that user. That's what's causing the

[sage-devel] Re: Trac slow

On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote: > > Just posting to say I've noticed and am investigating. > > It seems that somebody is performing a scrape of the front page which > includes a list of users on the site [1] each of which is a link to a > search query for all

Re: [sage-devel] Re: Trac slow

Since some time last night, I have been unable to use "git trac checkout TICKET": $ git trac checkout 22764 Loading ticket #22764... Checking out Trac #22764 remote branch fb90d5e3667237f2d9fc7ba982b466bc52802b1d -> local branch t/22764/fb90d5e3667237f2d9fc7ba982b466bc52802b1d... Traceback

Re: [sage-devel] first python3 build of sage

It looks to me that the various .so files get compiled but then removed just before the build finishes. Here is a snippet of the log: byte-compiling /mnt/backup/sage-py3/local/lib/python3.5/site-packages/sage/stats/r.py to r.cpython-35.pyc byte-compiling

Re: [sage-devel] first python3 build of sage

Indeed if one comments line 847 in src/setup.py the files looks to be there. Sage crashes anyway but now: VulK@bunion /mnt/backup/sage-py3 (git)-[my_py3] % ./sage -sh Starting subshell with Sage environment variables set. Don't forget to exit when you are done. Beware: * Do not do anything

Re: [sage-devel] Re: Trac slow

On 2017-04-20 17:09, John H Palmieri wrote: > Since some time last night, I have been unable to use "git trac checkout > TICKET": This (other ticket) worked for me about an hour ago. Daniel -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Trac slow

On Thursday, April 20, 2017 at 9:25:12 AM UTC-7, Daniel Krenn wrote: > > On 2017-04-20 17:09, John H Palmieri wrote: > > Since some time last night, I have been unable to use "git trac checkout > > TICKET": > > This (other ticket) worked for me about an hour ago. > Yes, you're right. It's

Re: [sage-devel] first python3 build of sage

Do you have the corresponding (cython) library SAGE_ROOT/local/lib/python3.5/site-packages/sage/misc/lazy_import.so If so could you try (inside a python3 shell) import sage.misc.lazy_import that should give you a more precise error. Vincent On 19/04/2017 14:57, Frédéric Chapoton

Re: [sage-devel] first python3 build of sage

Salut, There is no lazy_import.so in local/lib/python3.5/site-packages/sage/misc folder (and in fact no .so file at all there) And I get Python 3.5.1 (default, Apr 16 2017, 11:35:45) Type "copyright", "credits" or "license" for more information. IPython 5.1.0 -- An enhanced Interactive

Re: [sage-devel] first python3 build of sage

Salut Frédéric, Then this is the problem. Cython should generate .so files for each .pyx present in the Sage source code (which should be in the site-packages of Python3). If you provide an explicit branch with your "hacks" to get Sage compiled I might be able to provide more help. Vincent

Re: [sage-devel] first python3 build of sage

Salut, you have to apply first : public/experimental_python3_v0 then the ticket 22775 (new conway_polynomial package) https://trac.sagemath.org/ticket/22775 Frederic Le jeudi 20 avril 2017 08:40:33 UTC+2, vdelecroix a écrit : > > Salut Frédéric, > > Then this is the problem. Cython should

Re: [sage-devel] first python3 build of sage

Why do you have 355 commits on public/experimental_python3_v0?! It is hard to find its way... On 20/04/2017 08:52, Frédéric Chapoton wrote: Salut, you have to apply first : public/experimental_python3_v0 then the ticket 22775 (new conway_polynomial package)

Re: [sage-devel] first python3 build of sage

Really 355 ? More like 20, but I agree that it is a mess. This is my own experimental branch, not for evereybody's eyes.. It is made from 22764, 22756, 22305 and 22775 plus one own commit that takes care (not in a good way) of the last two calls to cmp() in pyx files. Frederic Le jeudi 20

Re: [sage-devel] first python3 build of sage

Waiting for make... I have nothing to do in order that Python3 is used instead of Python2? On 20/04/2017 08:52, Frédéric Chapoton wrote: Salut, you have to apply first : public/experimental_python3_v0 then the ticket 22775 (new conway_polynomial package)

Re: [sage-devel] first python3 build of sage

STOP ! you should export SAGE_PYTHON3=yes Le jeudi 20 avril 2017 09:02:54 UTC+2, Frédéric Chapoton a écrit : > > Really 355 ? More like 20, but I agree that it is a mess. > > This is my own experimental branch, not for evereybody's eyes.. It is made > from 22764, 22756, 22305 and 22775 > > plus

Re: [sage-devel] first python3 build of sage

Can you look at SAGE_ROOT/src/build and try to find is there is a .so there. For example $ find $(sage -root)/src/build -name "*.so" (normally there should be, the cythonization process put stuff there) On 20/04/2017 09:07, Frédéric Chapoton wrote: STOP ! you should export SAGE_PYTHON3=yes

Re: [sage-devel] first python3 build of sage

~/sage3/src/build$ find -name "*.so" returns nothing :( Le jeudi 20 avril 2017 09:35:50 UTC+2, vdelecroix a écrit : > > Can you look at SAGE_ROOT/src/build and try to find is there is a .so > there. For example > > $ find $(sage -root)/src/build -name "*.so" > > (normally there should be, the