[sage-devel] vote required for (small) backward incompatible change

Hello everybody, In ordre to solve the problem raised in trac #12706, it is necessary to make a backward incompatible change, namely : http://trac.sagemath.org/sage_trac/ticket/12706 BEFORE: at some point, in the doc, one can find something equ

[sage-devel] same error building 5.1 and 5.2rc0

Hello, I have tried to build first 5.1 and then 5.2rc0 on an Dell E5500 laptop running a brand new ubuntu. Both fails in the same way ; here below is a small excerpt of the log. What should I do ? Thanks for your help Frederic configure: creating ./config.status config.status: creating Makef

[sage-devel] Re: same error building 5.1 and 5.2rc0

Frederic Le lundi 23 juillet 2012 20:33:06 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > I have tried to build first 5.1 and then 5.2rc0 on an Dell E5500 laptop > running a brand new ubuntu. Both fails in the same way ; here below is a > small excerpt of

[sage-devel] Re: same error building 5.1 and 5.2rc0

oops, I have just shut the window and lost the messages.. :( Where can I find this log file ? Le lundi 23 juillet 2012 20:33:06 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > I have tried to build first 5.1 and then 5.2rc0 on an Dell E5500 laptop > running a brand new ubu

[sage-devel] Re: same error building 5.1 and 5.2rc0

on/sage-5.2.rc0/spkg/build/givaro-3.2.13.p0' && '/home/chapoton/sage-5.2.rc0/sage' -sh) When you are done debugging, you can type "exit" to leave the subshell. Le lundi 23 juillet 2012 20:33:06

Re: [sage-devel] Re: same error building 5.1 and 5.2rc0

Thanks a lot. I reinstalled from scratch and it worked. Le mardi 24 juillet 2012 10:31:42 UTC+2, Jeroen Demeyer a écrit : > > This is because the error in building GCC sort of messed up the whole > build. Either reinstall from scratch, or reinstall MPIR using: > > $ ./sage -f mpir > -- -- T

[sage-devel] Re: patchbot down?

I am missing the patchbot, too.. Can we hope for its return soon ? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr

[sage-devel] Re: Race condition in star_imports cache?

There is the same problem with ticket #8386 ( http://trac.sagemath.org/sage_trac/ticket/8386) Le mercredi 12 décembre 2012 18:48:50 UTC+1, Nils Bruin a écrit : > > There's a patchbot problem on #8327 that needs more eyeballs (or at > least Robert's eyeballs): > > The patchbot there sporadically

[sage-devel] what about adding trac roles for oeis and arxiv

Hello everybody, What do you think of the idea of adding two new roles (such as the ones existing for trac and wikipedia) : :arxiv:`hep-ph/0206021` and :doi:`10.1007/BF02546665` The idea is to try to have more links in the references, towards the outer web, so that one can click to the cite

[sage-devel] Re: (abs(sin(x))^2).simplify_full()

This is not a bug, because x can be any complex number : sage: x=CDF(4+2*I) sage: abs(sin(x))**2 13.7268664349 sage: sin(x)**2 2.48667440045 + 13.4997523143*I Le jeudi 14 février 2013 16:21:29 UTC+1, Julius a écrit : > > I think (abs(sin(x))^2).simplify_full() should render sin(x)^2. Thi

[sage-devel] a problem with references in functions with 2 names

Working on ticket #14496 (http://trac.sagemath.org/sage_trac/ticket/14496) I have met the following problem: I have defined a function "q_binomial" and an alias for this function : "gaussian_binomial" but the definition of "q_binomial" contains a reference, say to [iota2013] Then the document

Re: [sage-devel] New doctest continuation ....:

Hello, I do not understand what the new plugin "plugins.doctest_continuation" is supposed to test. Is it the plugin alluded to in the previo

[sage-devel] Re: incorrect spelling in a function name

This could be done as part of #14609 maybe ? Le jeudi 6 juin 2013 11:18:40 UTC+2, John Cremona a écrit : > > While reviewing #13591 I noticed that two functions on point on > elliptic curves over number fields are spelled incorrectly: > > schemes/elliptic_curves/ell_point.py:2600:def > arch

[sage-devel] Re: absolute value in a p-adic quotient field

Well, the problem comes from a.matrix() which does not work. This is because it receives an incorrect number of terms, so it cannot build the matrix. In turn, this is because the length of (a**i).list() depends on i, which is maybe unexpected. I have not tried to look further. Frederic Le me

[sage-devel] Re: Trac ticket with a new file

Bonjour Matthieu, je vais essayer d'expliquer comment je fais. you can also work from a terminal, using "sage -hg" instead of "hg_sage" inside sage. You have to be in your SAGE_DIRECTORY/devel/sage-main/ first step: create a patch sage -hg qnew trac_14914_stuffle.patch second step: create or m

[sage-devel] is there a photographic image in the sage sources ?

Hello, for the sake of testing image filters, I would need to have a png and/or jpg image available in the sage sources, and it should rather be a * photograph* does something like that already exist ? where ? there is nothing in sage/media. Maybe in some tutorials ? otherwise, maybe somebody

[sage-devel] Re: is there a photographic image in the sage sources ?

well, a very classical one ! thanks a lot Frederic Le jeudi 22 août 2013 21:42:41 UTC+2, Volker Braun a écrit : > > > $SAGE_ROOT/local/lib/python2.7/site-packages/matplotlib/mpl-data/sample_data/lena.jpg > > > > On Thursday, August 22, 2013 8:38:28 PM UTC+1, Frédéric Chapot

[sage-devel] Re: centered banner

The banner does no longer look like that, it has been changed in 5.12.beta2. Le dimanche 25 août 2013 11:02:45 UTC+2, P Purkayastha a écrit : > > Hi devs, > > How would you like a centered banner when sage is started? Is that > something desirable, or do you always prefer a left-aligned banner?

[sage-devel] patchbot is not working correctly on dependencies

It seems that the patchbot currently does not work. More precisely, it does not know where to stop in the dependencies to be applied, and tries to apply very old (and since long included) dependencies Just one example among many : http://patchbot.sagemath.org/ticket/8388/ Patchbot is a great

[sage-devel] git and patchbot

Hello, so far, the patchbot is not able to test the tickets given by a git branch (and it seems that it does not recognize the branch field) Would it be hard to get that working ? There are already several tickets with a git branch waiting for review (just one example #15054) Frederic -- You

[sage-devel] not trusted anymore ?

Hello, it seems (the patchbot has told me) that I am not a default trusted user. That must be the reason why the patchbot dos not look at my patches. I feel a bit sad :( Not so long ago, the patchbot was working on my patches very often. If this is not a deliberate banishment (I hope not, I

[sage-devel] Re: not trusted anymore ?

told otherwise So, if somebody has the power to add me back, it would be great. Otherwise, what should I do ? Frederic Le jeudi 12 septembre 2013 14:17:45 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > it seems (the patchbot has told me) that I am not a default trusted user. &g

[sage-devel] Re: not trusted anymore ?

trusted user. :) Frederic Le jeudi 12 septembre 2013 14:17:45 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > it seems (the patchbot has told me) that I am not a default trusted user. > That must be the reason why the patchbot dos not look at my patches. > > I feel a bit sad

[sage-devel] Re: not trusted anymore ?

this ticket, even if you have not contributed to the code. So my being non-trusted currently prevents the bot to run on a lot of patches.. Frederic Le jeudi 12 septembre 2013 14:17:45 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > it seems (the patchbot has told me) that I am n

[sage-devel] Re: not trusted anymore ?

le, I have none: compare http://patchbot.sagemath.org/ticket/?status=closed%20:%20fixed&author=chapoton and http://patchbot.sagemath.org/ticket/?status=closed&author=chapoton So it would be good to try and find a better way to know who can be trusted ! Cheers, Frederic Le jeudi 12 septembre 20

[sage-devel] Re: not trusted anymore ?

Thanks Robert for your answer ! I am trying to do that myself, but i am not an expert of github... should i go on, or rather let you do that ? Le jeudi 12 septembre 2013 14:17:45 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > it seems (the patchbot has told me) that I am n

[sage-devel] Re: not trusted anymore ?

Hello, I have made a pull request at https://github.com/robertwb/sage-patchbot I am not sure whether I have done the right changes in the sources of the patchbot. I guess it is now up to Robert to give his opinion. Frederic Le jeudi 12 septembre 2013 14:17:45 UTC+2, Frédéric Chapoton a écrit

[sage-devel] Re: Coloured blobs on tickets

Hello, If you want to run a patchbot on your own tickets, I would suggest the following : 0) upload (i.e. clone) the latest patchbot from here : https://github.com/robertwb/sage-patchbot Then in a shell 1) cd sage-patchbot/src 2) ipython 3) from patchbot import Patchbot 4) P=Patchbot('your

[sage-devel] trac email config

Hello, since the new trac server introduced last week, the trac emails are classified as spam in my mailbox. This is very inconvenient. Am I the only one observing this ? If not, maybe this could be caused by a misconfiguration of the new trac machine ? Frédéric -- You received this message

[sage-devel] patchbots , how to have your own

Hello everybody, two things about the patchbots: 1) I would like to tell whoever is running the patchbot named Fedora/19/x86_64/3.11.2-201.fc19.x86_64/desktop that her/his patchbot is prob

[sage-devel] Re: patchbots , how to have your own

version is in the spkg, but maybe it needs to be updated. Maybe one should ask Robert Bradshaw what is the current status of things ? Frederic Le mardi 22 octobre 2013 14:03:19 UTC+2, Volker Braun a écrit : > > On Tuesday, October 22, 2013 12:53:02 PM UTC+1, Frédéric Chapoton wrote: >

Re: [sage-devel] trac email config

Hello Since a few days, I am no longer receiving any email from trac, even in my spam box.. Can somebody please confirm that this problem is still there ? Frédéric Le mercredi 23 octobre 2013 19:09:56 UTC+2, Keith Clawson a écrit : > > On Wednesday, October 23, 2013 8:21:21 AM UTC-7, Anne Schi

[sage-devel] Re: sage startup time...

Hello, I have made a ticket #15335 (about removing the linefrom sage.server.all import * ) Fred Le dimanche 27 octobre 2013 19:09:52 UTC+1, William a écrit : > > Hi, > > I think the startup time of Sage may be starting to get out of control > again. For example, I'm concerned about so

[sage-devel] Re: Sage 5.11 crashes on run when functions are imported

Hello Anna, primes_above is a *method* of number fields, you cannot import this (and you do not need to import it to use it) Frederic Le jeudi 14 novembre 2013 21:30:10 UTC+1, Anna Haensch a écrit : > > I'm running 5.11 (built from source-code). I went into the file > quadratic_form__local_fi

[sage-devel] Re: Error with trac

I have the same problem with #15550. Quite displeasant. Frédéric Le vendredi 20 décembre 2013 04:18:37 UTC+1, Travis Scrimshaw a écrit : > > I'm getting the following error anytime I try to attach a new branch to a > ticket which previously didn't have one (in particular #12453 and #9280): > > *

[sage-devel] Re: Patchbot gets "priority" and "status" of a ticket totally wrong

Hello, it seems that the patchbot has not really digested the git transition. I would be happy to see it back, as it was very useful in the development process in the mercurial era. To modify the patchbot, you have to clone from here https://github.com/robertwb/sage-patchbot and then propose

[sage-devel] Re: reduce compilation times during development

Hello, to avoid recompliation, I am rather doing the following (not sure if this is a good thing to do) : $ git fetch trac# needs to be in /sage $ git ch develop# I switch to the develop branch $ git pull trac develop # this updates to the latest developement version of sage $ ma

[sage-devel] Re: ticket 12455 inaccessible

Same for #8698 ! Le dimanche 20 juillet 2014 07:41:32 UTC+2, Ralf Stephan a écrit : > > Hello, > > http://trac.sagemath.org/ticket/12455 > gives me > *Trac detected an internal error:* > > OSError: [Errno 2] No such file or directory: '/tmp/tmpfcOFO7' > > > Could an admin please have a look? > >

[sage-devel] speaking spanish or catalan ?

Hello, is there any spanish (native) speaker there, to have a quick look at http://trac.sagemath.org/ticket/7192 that needs review ? and maybe a catalan (native) speaker to look at http://trac.sagemath.org/ticket/12847 ? Thanks, Frederic -- You received this message because you are subscrib

[sage-devel] last mercurial footprints

Hello everybody, there is a rather simple ticket needing review that removes the last mercurial footprints : http://trac.sagemath.org/ticket/16104 could you please have a look ? Frederic -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsu

[sage-devel] Re: Warn about long doctests (#16609 needs review)

I have made ticket #16738 for removing the long tests in src/sage/combinat/cluster_algebra_quiver/mutation_type.py Le mardi 29 juillet 2014 04:58:52 UTC+2, Volker Braun a écrit : > > A small handful of modules takes the majority of the doctest walltime, see > e.g. this lopsided distribution: > >

[sage-devel] Re: Difficulties with resultant

Hello, it works for me on sage 6.3.beta8, giving: 2201*xbar^2 + 487324445*xbar + 487325602 which version of sage do you use ? type version() to know that. By the way, you should rather have asked that question on sage-support or on ask.sagemath.org Le jeudi 7 août 2014 16:03:43 UTC+2, Bill Ha

[sage-devel] what is the plot3D viewer used in sagemath cloud

Hello, I am trying in #12212 to allow plotting colored 3D surfaces. http://trac.sagemath.org/ticket/12212 So far, progress has been done on jmol, tachyon and canvas3D viewers. Does anybody know what is the viewer used in sagemath cloud ? -- You received this message because you are subscribed

[sage-devel] Re: what is the plot3D viewer used in sagemath cloud

geCell (you have to call it > explicitly as (threejs(plot(sin))), but they function differently. There > are some threads on the notebook list about three.js problems. > > On Wednesday, 20 August 2014 14:19:52 UTC-6, Frédéric Chapoton wrote: >> >> Hello, >> >&g

[sage-devel] Re: what is the plot3D viewer used in sagemath cloud

cannot experiment with it right now. Frederic Le vendredi 22 août 2014 06:09:03 UTC+2, jason a écrit : > > On 8/21/14, 15:27, Frédéric Chapoton wrote: > > Thanks ! Do you know which file format is used by sagemath cloud to > > communicate with threejs ? Is it .obj or .x3d or

[sage-devel] Re: Patchbot troubles

Maybe it was caused by some temporary slowness of trac ? Anyway, I have created #16872 to upgrade the patchbot to the latest version. http://trac.sagemath.org/ticket/16872 Le vendredi 22 août 2014 12:17:21 UTC+2, Jeroen Demeyer a écrit : > > Hello, > > Given the message asking for patchbot volu

[sage-devel] Re: Interested in co-writing an article?

This could have some relation with http://trac.sagemath.org/ticket/15635, maybe. Le samedi 11 octobre 2014 03:26:24 UTC+2, Alasdair a écrit : > > I've written an article about using Sage to develop explicit Runge-Kutta > formulas for the numerical solution of ODEs. I've sent it off to a few >

[sage-devel] fail to make

Hello, I got that on two different machines with 6.4.beta5: Error building Sage. The following package(s) may have failed to build: package: python-2.7.8 Does anybody else meet the same problem ? I have not yet used the heavy option "make distclean", because I hate to recompile ATLAS Freder

[sage-devel] Re: fail to make

s 0m49.290s Error installing package python-2.7.8 Le dimanche 12 octobre 2014 20:47:02 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > I got that on two different machines with 6.4.bet

[sage-devel] where are the bots ?

Hello, it seems that the bots have disappeared. Both the buildbot (was top left) and the patchbot (top right). The patchbot links are broken (used to be colored little round things). And http://patchbot.sagemath.org points to William's homepage. Can we we hope that the bots will be back soon ?

[sage-devel] Re: Posets: interval/closed_interval

Probably one should keep *closed_interval* as an alias of *interval* I also noticed today that *interval_iterator* forgets about trivial intervals [v,v]. Le mercredi 5 novembre 2014 12:17:10 UTC+1, Jori Mantysalo a écrit : > > What is the logic having both interval() and closed_interval() define

Re: [sage-devel] where are the bots ?

; On Tue, Oct 21, 2014 at 1:22 PM, R. Andrew Ohana > wrote: > > The buildbot was having some issues and was reporting everything as a > > failure. I disabled it until I get a moment to fix it. > > > > On Tue, Oct 21, 2014 at 1:18 PM, Frédéric Chapoton > > &g

[sage-devel] py3: what to do with cmp ?

As an intermediate step in our long way to python3, I would like to be able to compile all the .pyx files in py3. Except for #21246 (please review), the big remaining problem preventing to reach this goal is the removal of the builtin "cmp" in py3. One solution would be to have our own "cmp" th

[sage-devel] Re: patchbot.sagemath.org down?

Happy to hear that you care about the patchbot. Maintenance is currently being done (slowly). It will hopefully be resurrected soon. Frédéric Le dimanche 14 août 2016 18:17:12 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > Since yesterday (at least), it seems that patchbot.sagemath.org is > unre

Re: [sage-devel] py3: what to do with cmp ?

thing)" in pyx files, and the "cythonizing" worked all the way. Then the compilation itself hanged up in one the pyx files. I have not yet investigated why. Frederic Le lundi 15 août 2016 09:19:53 UTC+2, Jeroen Demeyer a écrit : > > On 2016-08-14 14:41, Frédéric Chapoton wrot

[sage-devel] Re: patchbot.sagemath.org down?

The patchbot server should be up again (it has been moved). Please report problems here, and please restart (and update) your patchbot clients as explained in https://wiki.sagemath.org/buildbot/details Frederic Le dimanche 14 août 2016 18:17:12 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > Sin

[sage-devel] Re: Issue with coverage plugin?

Well, this is typical of Python3. You are trying to use the patchbot with python3. This has never been done (vene if I tried to anticipate). You should rather not be using python3 to run a patchbot (yet) Le samedi 20 août 2016 13:46:48 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > In https://pat

[sage-devel] Re: broken %attach and %debug ?

TC-5, Volker Braun wrote: >> >> Presumably attach (or, more generally, using the python inputhook) >> doesn't work since Ipython 5 now implements its own input handling. >> >> >> >> >> On Friday, August 12, 2016 at 2:22:51 PM UTC+2, Frédéric Chapoton wrote: &g

[sage-devel] Re: Should we close all tickets with milestone "sage-duplicate/invalid/wontfix"?

Hello, May *please* somebody close all the *69* positive-reviewed duplicate/invalid/wontfix tickets ? if Volker has no time for that, maybe somebody else should be given the power to do that ? Frédéric Le jeudi 19 mai 2016 10:51:20 UTC+2, Samuel Lelievre a écrit : > > I'm wondering if we shou

[sage-devel] Re: Bug in FreeQuadraticModule.discriminant

yes, indeed this is a bug. Thanks for reporting. Would you like to make the next step to solve that ? Then you should ask for an account on trac.sagemath.org and open a ticket. Instructions are available here: http://www.sagemath.org/git-developer-guide/ Frederic Le mercredi 31 août 2016 15:3

[sage-devel] Re: Weekend workshop BIRS: SageMath development related to K3 surfaces (March 2016)

Maybe the authors/users of the Chow package for sage would be interested ? Probably not Sorger, who is busy being currently head of mathematics in CNRS. http://www.math.sciences.univ-nantes.fr/~sorger/chow_en.html Frederic Le jeudi 8 septembre 2016 16:00:37 UTC+2, Simon Brandhorst a écrit : >

[sage-devel] Re: Compilation error with linbox-1.4.2 during compilation of sage 7.4.beta4

I also have problems with linbox since the update, I have attached the log to #17635. Le lundi 12 septembre 2016 19:50:11 UTC+2, leif a écrit : > > Volker Braun wrote: > > The error is in an optional part that isn't compiled by default; I guess > > its the maple interface? The config contains

[sage-devel] Re: Graceful shutdown of patchbot

There is an option --count to say how many ticket to tests before to stop. you may want to use that. You may even change it in your json config file during the patchbot run (not tested if this works to stop the bot) But Ctrl-C should not be very problematic. Could you tell what kind of problem

[sage-devel] Re: broken %attach and %debug ?

I have opened a ticket https://trac.sagemath.org/ticket/21545 to upgrade to ipython 5.1, in the hope that this will solve this *damn* %attach issue Frederic Le vendredi 12 août 2016 14:22:51 UTC+2, Frédéric Chapoton a écrit : > > is this only me, or the recent update to ipython 5.0 has

Re: [sage-devel] Re: Graceful shutdown of patchbot

ee a écrit : > > Dear all, > > > > > > A patchbot is supposed to run forever, but realistically I should stop > it > > from time to time. Pushing ctrl-c stops the patchbot abruptly, and the > > subsequent run seems sometimes to show somewhat erroneous behavior,

Re: [sage-devel] sage4 patchbot

sage4 is going on as usual with 7.4.beta6, always giving us generously wrong BuildFailed reports. Frederic Le vendredi 23 septembre 2016 11:12:51 UTC+2, Jeroen Demeyer a écrit : > > On 2016-09-23 08:51, Ralf Stephan wrote: > > What has that to do with stopping the bot (or monitoring it at all,

[sage-devel] Re: Build issues with patchbots hades, poseidon and fermat

if you look here, you see that almost all bots have failed to build 7.4.rc0: https://patchbot.sagemath.org/ticket/0/ Among them is my own bot, now stopped. I tried a make distclean & make, and the same error still appears. Frederic Le mardi 11 octobre 2016 09:38:19 UTC+2, Eric Gourgoulhon a éc

[sage-devel] Re: Build issues with patchbots hades, poseidon and fermat

I now have this problem on my own machine: sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' already defined and this has nothing to do with any patchbot.. Frederic Le mardi 11 octobre 2016 19:04:40 UTC+2, Frédéric Chapoton a écrit : > > if you look here, you see

Re: [sage-devel] Re: cython memory leak when one's forget to cdef the for loop variable

xrange will stilll be allowed in cython files, even after (if) we switch to python3 Frederic Le jeudi 20 octobre 2016 11:47:38 UTC+2, Johan S. R. Nielsen a écrit : > > >> sage: a = range(10**8) # takes a lot of memory > >> sage: del a# free the memory > > > > Ok, so now,

[sage-devel] Re: ordering of polynomials and failing optional doctest for database_jones_numfield

there is already a positive reviewed ticket for this issue Frederic Le jeudi 20 octobre 2016 18:48:03 UTC+2, vdelecroix a écrit : > > Hello, > > Some tests related to the optional package database_jones_numfield > fail for some ordering reason [1]. Sadly this is broken in the new > Sage releas

Re: [sage-devel] Re: ordering of polynomials and failing optional doctest for database_jones_numfield

apparently not so many people care for the patchbot's results.. and optional packages are probably not tested by Volker Le jeudi 20 octobre 2016 19:06:03 UTC+2, vdelecroix a écrit : > > Thanks for your answer. > > Why was it not a blocker!? I would have thought that passing all tests > (includi

[sage-devel] vote on behaviour of is_similar for matrices

Hello, on https://trac.sagemath.org/ticket/18505, we are trying to enhance the *is_similar* method of matrices. Because we cannot agree, we require your vote on the following matter: 1) When M.is_similar(N) is called and either M or N is not square: A) raise an helpful specific error message B

[sage-devel] Re: vote on behaviour of is_similar for matrices

I consider that the vote is now closed. The result is 6 for AA, 3 for BB and 1 for ?A. Other people did not express a clear choice. Please now review https://trac.sagemath.org/ticket/18505, which implements the AA choice. Frédéric Le jeudi 27 octobre 2016 10:48:17 UTC+2, Frédéric Chapoton a

Re: [sage-devel] Re: sage's increasingly long startup time?

If nobody else than me cares about *working* on the transition to py3, this is probably not going to happen anytime soon. Frederic Le lundi 7 novembre 2016 11:19:51 UTC+1, Erik Bray a écrit : > > On Thu, Oct 27, 2016 at 9:53 PM, Jeroen Demeyer > wrote: > > Well, Python isn't exactly efficient

[sage-devel] build system changes should care about py3 ?

Hello, Trying to compile 7.5.b2 with python3 (using export SAGE_PYTHON3=yes), I got now the following error: [sagelib-7.5.beta2] python -c "from sage_setup.autogen.pari import rebuild; rebuild()" [sagelib-7.5.beta2] sys:1: RuntimeWarning: not adding directory '' to sys.path since it's writable

[sage-devel] Re: build system changes should care about py3 ?

exact same problem after running ./configure. Should I try make distclean ? Le samedi 12 novembre 2016 22:16:41 UTC+1, Dima Pasechnik a écrit : > > > > On Saturday, November 12, 2016 at 8:43:57 PM UTC, Frédéric Chapoton wrote: >> >> Hello, >> >> Trying to compi

[sage-devel] Re: build system changes should care about py3 ?

lib-7.5.beta2] TypeError: memoryview: a bytes-like object is required, not 'str' [sagelib-7.5.beta2] generate_py_source.mk:10 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a échouée Le dimanche 13 novembre 2016 09:56:24 UTC+1, Dima Pasechnik a écrit : > > > > On Sunday, Nove

[sage-devel] Re: build system changes should care about py3 ?

The culprit line was just recently added in https://trac.sagemath.org/ticket/21821 could please the authors and reviewers of that ticket handle this problem ? Le dimanche 13 novembre 2016 13:34:32 UTC+1, Frédéric Chapoton a écrit : > > after a make distclean and make, same problem,

[sage-devel] Re: Cross-type comparisons

There is currently an effort being made (by me and a few referees) to get rid of cmp() in all pyx files. And the Element/Parent is one of the hardest cases remaining. Getting rid of all calls to cmp( ) is necessary for compatibility with python3. The intermediate objective is to be able to comp

[sage-devel] Re: Lollipop vs. Barbell

DO NOT TOUCH the import of range from six.moves ! This is part of our general move toward python3 ! And do never use xrange, this is now forbidden. Frederic Le mardi 6 décembre 2016 16:26:12 UTC+1, Peleg Michaeli a écrit : > > I actually think that this is an unwanted behaviour of `six`. > > An

[sage-devel] Re: Lollipop vs. Barbell

The new (python3 or six) range is an iterator. You just have to wrap it with list( ) to get back to the python2 behaviour if needed. Le mardi 6 décembre 2016 17:31:20 UTC+1, Frédéric Chapoton a écrit : > > DO NOT TOUCH the import of range from six.moves ! This is part of our > gen

[sage-devel] Re: Python3-compatible syntax

Hello, Regression in the move to python3 is happening all the time, and it is indeed very annoying. Making a test target and a buildbot may be easier once at least all our cython files are correctly cythonized in py3. This is blocked by the removal of cmp() in all .pyx files. Not an easy task,

Re: [sage-devel] Re: Python3-compatible syntax

The patchbot plugin is not enough. I did my best to shape it to prevent regression, but it is far from perfect in detecting possible problems. Of course, people should care about the results of this plugin. But we need also buildbots to check that no regression happens in the build process. Fre

[sage-devel] Re: patchbot: ticket list latency?

Hello, Tickets with untrusted authors are never looked at, unless you ask specifically so : { "Clemens Heuberger": "trusted", "Roswitha Rissner": "not trusted" } Frederic Le jeudi 5 janvier 2017 16:00:53 UTC+1, Clemens Heuberger a écrit : > > I am playing around with a patchbot and I a

[sage-devel] more than a hundred

Hello, We are now reaching the number of 108 positively reviewed tickets. Could we at least get rid of those that are duplicate/invalid/wonftix ? And shouldn't we postpone the last blocker ticker to a later release ? Just asking. Frederic -- You received this message because you are subscrib

[sage-devel] Re: Question on 3D plots

I am just working on similar questions, see https://trac.sagemath.org/ticket/22144 on pourrait en causer directement ? Frederic Le mardi 10 janvier 2017 17:59:16 UTC+1, Viviane Pons a écrit : > > Hi all, > > I'm introspecting 3D plots right now to fix some issues we have with sdl > export. I n

[sage-devel] Re: Why is patchbot testing closed tickets?

Yes, there is something fishy in the way the patchbot gets the list of tickets to test. Any help is welcome. There is already a check that should avoid that, but it seems that somehow it fails. I have just added another check (belt and suspenders..), that will be in patchbot 2.6.7 Not sure th

[sage-devel] Re: A triangulate method that produces quadrilaterals. Why ?

Hello, I think this is more subtle than that. The procedure "triangulate" is used in several places, and sometimes it may generate triangles. When I wrote the old stl_ascii_string, I was lazy and did not care about faces other than triangles, even if I knew perfectly that they could happen. I h

[sage-devel] Re: Python3?

Hello, let me try to summarize : we are still *quite far* from being python3 compatible. There are two main milestones we must reach: 1) being able to build sage with python3 ; (with substeps: 1A) being able to cythonize all pyx files / 1B) being able to compile all pyx files) 1C) being able

Re: [sage-devel] Re: Python3?

Le jeudi 19 janvier 2017 08:58:24 UTC+1, Snark a écrit : > > Hi, > > On 19/01/2017 08:47, Frédéric Chapoton wrote: > > > The problem with cmp is quite hard, and it seems that every instance of > > cmp() must be handled separately. I have gained some experience on

[sage-devel] Re: Closing wontfix-tickets

+1, please Le jeudi 19 janvier 2017 09:48:58 UTC+1, Jori Mäntysalo a écrit : > > Could someone close all 49 wontfix-positive_review -tickets? > > IMO it would be nice to have this done after every stable release. > > -- > Jori Mäntysalo > -- You received this message because you are subscrib

[sage-devel] py3 and widgetsnbextension

Last tentative of "export SAGE_PYTHON3=yes" then "make" fails as follows: This is a new behaviour in 7.6.beta0. [widgetsnbextension-1.2.6.p0] Successfully installed widgetsnbextension-1.2.6 [widgetsnbextension-1.2.6.p0] Cleaning up... [widgetsnbextension-1.2.6.p0] Traceback (most recent call las

[sage-devel] Re: py3 and widgetsnbextension

In fact, it seems that SAGE_PYTHON3=yes is no longer correctly recognized... Did somebody change something in the build procedure? Frederic. Le mardi 24 janvier 2017 09:36:11 UTC+1, Frédéric Chapoton a écrit : > > Last tentative of "export SAGE_PYTHON3=yes" then "m

Re: [sage-devel] py3 and widgetsnbextension

Jeroen, could you please try to build using SAGE_PYTHON3=yes and tell me what happens ? Frederic Le mardi 24 janvier 2017 13:12:34 UTC+1, Jeroen Demeyer a écrit : > > On 2017-01-24 09:36, Frédéric Chapoton wrote: > > Last tentative of "export SAGE_PYTHON3=yes" then &quo

Re: [sage-devel] Re: py3 and widgetsnbextension

21:06:32 UTC+1, Jeroen Demeyer a écrit : > > On 2017-01-24 10:40, Frédéric Chapoton wrote: > > In fact, it seems that SAGE_PYTHON3=yes is no longer correctly > > recognized... Did somebody change something in the build procedure? > > Here is a guess: could it be that you

[sage-devel] Re: Bug report: Incorrect json representation for graphics.

I have created a ticket on trac (https://trac.sagemath.org/ticket/22253#ticket) we do not use github and pulls, but trac tickets. I am going to post a branch there soon. Frederic Le mercredi 25 janvier 2017 11:12:11 UTC+1, mjs...@gmail.com a écrit : > > Markdown below: > > Bug report: Incorre

[sage-devel] Re: Bug report: Incorrect json representation for graphics.

More importantly, you absolutely should verify that you can send the > corrected json to jmol and have it work. > > > > El miércoles, 25 de enero de 2017, 11:14:56 (UTC+1), Frédéric Chapoton > escribió: >> >> I have created a ticket on trac ( >> https://trac.sag

[sage-devel] how to check zip, map, range, print for Python3

Hello, your help is required for some Python3-related question, please. I would like to have a branch which activates the future behaviour of zip (for example, but range or map are also candidates) both in code and doctests. Here is my tentative for zip, that only change zip behaviour in the d

Re: [sage-devel] how to check zip, map, range, print for Python3

avid > > On Thu, Jan 26, 2017 at 3:02 PM, Frédéric Chapoton > wrote: > >> Hello, >> >> your help is required for some Python3-related question, please. >> >> I would like to have a branch which activates the future behaviour of zip >> (for example,

[sage-devel] py3 build and a c++ error

Dear all, * Next step towards py3 would be to get rid of the last few calls to cmp() in pyx files, so that cythonization works. This is going to be hard. There remains only 4 files with such calls, but they are tough ones, see them using git grep "^[^#:]*[^a-z_\.]cmp(" *.pyx * 3 out of 4 inv

  1   2   3   4   5   >