Re: [sage-devel] Sage Installation on Mac: no app.dmg on mirrors

vdelecroix schrieb am Donnerstag, 27. Mai 2021 um 09:31:01 UTC+2: > As written in the documentation at > https://doc.sagemath.org/html/en/installation/binary.html#macos dmg are > available at > https://github.com/3-manifolds/Sage_macOS/releases/ Thanks. FWIW, this differs from

[sage-devel] Sage Installation on Mac: no app.dmg on mirrors

I was just asked by a colleague why there is no .dmg or app.dmg file on the mirrors, like on http://www-ftp.lip6.fr/pub/math/sagemath/osx/intel/index.html ? Is this simply (still) missing (as not built yet) or is there a reason? (FWIW Installation guide still speaks about these files.) Best,

[sage-devel] Re: Trac account request

Am Dienstag, 5. Mai 2020 11:15:43 UTC+2 schrieb Jean-Florent Raymond: > > Could someone create a proper trac account for me? Desired username: > jfraymond. > Done. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] subs bug in fraction field (critical)

I believe I have found a very serious issue in fraction field substitution, see https://trac.sagemath.org/ticket/27933 I find this very critical, so we should try to fix it soon... Best, Daniel PS: I just spent two days of debugging my computations just to narrow it down to such an unexpected

[sage-devel] testing for equality in new ring

I have implemented a new ring (parent/element structure) and now want to do equality testing. I use the code below, which seems to me somehow canonical for rings and equality testing (using coercions properly). For short, the difference between self and other is built and then compared for zero.

Re: [sage-devel] Factoring bug in Pari stack

On 06.05.19 10:37, David Roe wrote: > I've run across a strange bug that seems to be hardware dependent: I can reproduce the error on both systems that I've just checked: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (Laptop) Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz (Desktop) Both run Linux Mint

Re: [sage-devel] patchbot questions

On 24.04.19 22:16, John H Palmieri wrote: > > > On Tuesday, April 23, 2019 at 12:18:13 AM UTC-7, Daniel Krenn wrote: > > On 23.04.19 01:37, John H Palmieri wrote: > > I was running a patchbot successfully until some time last week. For > > reasons I don't

Re: [sage-devel] patchbot questions

On 23.04.19 01:37, John H Palmieri wrote: > I was running a patchbot successfully until some time last week. For > reasons I don't understand, I did "git pull" on the patchbot, and now it > won't run with Python 2, complaining AFAIK, the patchbot runs on Python 3 only (so, yes, you need this

Re: [sage-devel] python3 patchbot

On 17.04.19 16:00, E. Madison Bray wrote: > On Wed, Apr 17, 2019 at 3:06 PM Daniel Krenn wrote: >> >> Is it possible to set up a patchbot for running tests of SageMath on >> Python3? > > Yes, I believe so. Frédéric would know the specifics since I think he > made i

[sage-devel] python3 patchbot

Is it possible to set up a patchbot for running tests of SageMath on Python3? -- 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

Re: [sage-devel] Re: frozensets in doctests / for display in Python3

On 16.04.19 17:26, Nils Bruin wrote: > Do you want to test that you get *that* string representation back? > Or do you want to check that you are getting string representations of > that shape, but with possibly differently order frozensets? > Or do you want to check that you get a list back with

Re: [sage-devel] gitlab status?

On 16.04.19 14:04, E. Madison Bray wrote: > So if anyone wants to contribute hardware to work as runners, I can > walk them through the setup process now that I've done it myself. > It's quite easy for the most part. I can set-up one. FYI, I have once created a runner for a different (local)

Re: [sage-devel] Re: frozensets in doctests / for display in Python3

On 16.04.19 16:56, John H Palmieri wrote: > Is the printed order important? If not, you can change the doctest to > something else that is actually testing something relevant [...] Changing the doctest really an option here, as we want to see the transistions of the automaton which are display

Re: [sage-devel] frozensets in doctests / for display in Python3

On 16.04.19 16:59, E. Madison Bray wrote: > On Tue, Apr 16, 2019 at 4:43 PM Daniel Krenn wrote: >> sage: from IPython.lib.pretty import pretty >> sage: pretty(frozenset([frozenset(['A', 'B']), frozenset(['B', 'C'])])) >> >> displays the set of sets with random order. H

[sage-devel] frozensets in doctests / for display in Python3

In Python2-SageMath we have sage: frozenset([frozenset(['A', 'B']), frozenset(['B', 'C'])]) frozenset({frozenset({'B', 'C'}), frozenset({'A', 'B'})}) in all my trials, whereas in Python3 we get all possible permutations of the elements at random. Even using sage: from IPython.lib.pretty import

[sage-devel] gitlab status?

Some time ago there was an attempt to use additionally Gitlab for our development process. What is the current status of this? (Back then, I (@dakrenn) asked to be included as user, so that I can contribute/test as well, as I frequently use Gitlab for many other projects.) Best, Daniel -- You

Re: [sage-devel] No reponse to account request

On 02.04.19 00:55, Dima Pasechnik wrote: > it can take some time, as it's done manually by volunteers... So apparently more volunteers are needed; I could be one of them... If so, who would need what from me to make this happend? Daniel -- You received this message because you are subscribed

Re: [sage-devel] SystemError: calling remove_from_pari_stack() inside sig_on()

On 30.03.19 09:23, Jeroen Demeyer wrote: > See https://trac.sagemath.org/ticket/27477 Thanks. -- 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] SystemError: calling remove_from_pari_stack() inside sig_on()

I've recently seen a couple of random doctest failures, see below. Anyone some ideas? File "src/sage/rings/number_field/number_field.py", line 1288, in sage.rings.number_field.number_field.NumberField_generic Failed example: for chi in G: D = ModularSymbols(chi, 2,

[sage-devel] Patchbot steenrod troubles

However is in charge of it, take a look... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send

Re: [sage-devel] how to log sage output for long running program

On 16.03.19 05:46, Ai Bo wrote: > I am running a long running program. I would like to log the output. > I have tried:  >  ../sage-8.6/sage test.sage > test.log & I used something along PYTHONUNBUFFERED=whatever ../sage-8.6/sage test.sage > test.log & a couple of times. Daniel -- You

Re: efficiency in creating multivariate polynomial rings [Re: [sage-devel] problem with scalar multiplication: polynomial and vector]

On 01.03.19 03:59, Travis Scrimshaw wrote:> IMO we do not want there to be too much of a distinction between > multivariate polynomial rings in 1 variable and univariate > polynomial rings. I would say the proper thing to do is to pass along > the underlying implementation as part of the MPoly

[sage-devel] fix or not? [Re: efficiency in creating multivariate polynomial rings]

The question remains: Do we want the change proposed in https://trac.sagemath.org/ticket/27364 fixing the mentioned issue (but introducing a slowdown) or not? (I somehow tend to say "we want that", because the change obviously fixes a bug. (It seems natural that the MPoly functor returns a

Re: efficiency in creating multivariate polynomial rings [Re: [sage-devel] problem with scalar multiplication: polynomial and vector]

On 01.03.19 03:59, Travis Scrimshaw wrote:> IMO we do not want there to be too much of a distinction between > multivariate polynomial rings in 1 variable and univariate > polynomial rings. I would say the proper thing to do is to pass along > the underlying implementation as part of the MPoly

efficiency in creating multivariate polynomial rings [Re: [sage-devel] problem with scalar multiplication: polynomial and vector]

On 28.02.19 09:15, Daniel Krenn wrote: > Does someone have a glue why > > sage: T = PolynomialRing(QQ, 't', 1); t = T.gen() > sage: t * vector([1,2]) The underlying problem is that the functor MPoly[t] applied to QQ (for example) returns a true univariate polynomial

Re: [sage-devel] problem with scalar multiplication: polynomial and vector

On 28.02.19 09:15, Daniel Krenn wrote: > I tried to debug, but I am a bit lost on this particalar problem, so any > kind of input is welcome. Found something; I'll report back soon. -- You received this message because you are subscribed to the Google Groups "sage-devel" group

[sage-devel] problem with scalar multiplication: polynomial and vector

Does someone have a glue why sage: T = PolynomialRing(QQ, 't', 1); t = T.gen() sage: t * vector([1,2]) results in an error TypeError: unsupported operand parent(s) for *: 'Multivariate Polynomial Ring in t over Rational Field' and 'Ambient free module of rank 2 over the principal

[sage-devel] .an_element() != 0?

Can I savely assume that S.an_element() of something S (within SageMath) returns an element different from S.zero() if possible (meaning if there are nonzero elements in S)? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] groebner basis algorithm: intended way of calling (out of other method)

Let I be an ideal. Then I might want to compute something involving Groebner basis, e.g. computing I.variety(). Now suppose one wants to select a particular algorithm for the computation of the Groebner basis. Then (due to caching) I use something along the lines of GB =

Re: [sage-devel] Re: python3 status report

On 2019-01-27 14:50, Simon King wrote: > How to do so most easily, so that "git pull" etc. still referes to trac? > That was part of my question. Doing "git pull > /path/to/my/old/installation" would mean that I need to go to my old > installation, "git pull" (pulls develop from trac), go to the

[sage-devel] Re: Graph theory: neighbors of a nonexistent vertex

On 2019-01-07 12:34, Jean-Florent Raymond wrote: > I think I know how to fix it. Should I open a trac ticket? Yes, please. (And do a quick search on trac before so that noone else has created a ticket for this, but I doubt it.) Daniel -- You received this message because you are subscribed to

Re: [sage-devel] Re: how to use a singular lib

On 2018-11-23 20:49, Simon King wrote: > Hi Daniel, > > On 2018-11-23, Daniel Krenn wrote: >> Singular is shipped with symodstd.lib (it contains an algorithm for >> computing a Groebner basis in a special case). >> How can I access it from within Sage? >> >&g

Re: [sage-devel] Re: how to use a singular lib

On 2018-11-23 21:18, 'Martin R. Albrecht' via sage-devel wrote: > Indeed, this should work: > > _ = sage.libs.singular.function.lib("symodstd.lib") > syModStd = sage.libs.singular.function.singular_function("syModStd") Oh, this is easy. Thanks :) -- You received this message because you are

[sage-devel] how to use a singular lib

Singular is shipped with symodstd.lib (it contains an algorithm for computing a Groebner basis in a special case). How can I access it from within Sage? I looked up the code and coming from an ideal's groebner_basis method, it is somehow clear how to extend this, but how do I make the actual call

Re: [sage-devel] deterministic "ordering" of subsets (py3)

On 2018-11-08 08:08, Vincent Delecroix wrote: > Python 3 introduced randomness in their base hashing functions. That > impact strings. > > $ python -c 'print(hash("hello Daniel!"))' > -4203807413548925149 > $ python -c 'print(hash("hello Daniel!"))' > 7756578277334792321 I wasn't aware of this,

[sage-devel] deterministic "ordering" of subsets (py3)

I just was hunting a Heisenbug related to Python3. It boils down to the following: dakrenn@nops:~$ /opt/sage/8.5.beta2-python3/sage -c "P. = QQ[]; S = Set([x,y,z]).subsets(2); print(S); print(list(S))" Subsets of {y, x, z} of size 2 [{x, y}, {z, y}, {z, x}] dakrenn@nops:~$

Re: [sage-devel] Upcoming Debian freeze

On 2018-11-06 10:04, Frédéric Chapoton wrote: > ("round,ceil,floor in python semantics" I am curious: What is this about? Daniel -- 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,

[sage-devel] _l_action_ and _r_action_ not working?

Do _l_action_ and _r_action_ actually work? We have the following occurrences: dakrenn@nops:~$ sage -grep "_l_action_" sage/rings/multi_power_series_ring_element.py:#return self._l_action_(c) sage/rings/multi_power_series_ring_element.py:def _l_action_(self, c):

Re: [sage-devel] Re: sage Python3 build: sagenb problem

n3 to see the failing doctests in sage.rings.asymptotic and to play around with these. Is there a way to exclude this from the build? Daniel > On Tue, Oct 30, 2018 at 2:35 PM Daniel Krenn wrote: >> >> On 2018-10-30 13:47, Eric Gourgoulhon wrote: >>> I had the same probl

Re: [sage-devel] Re: sage Python3 build: sagenb problem

On 2018-10-30 13:47, Eric Gourgoulhon wrote: > I had the same problem this morning, while performing the python3 build > of Sage 8.5.beta1: > [sagenb-1.1.0] Error installing package sagenb-1.1.0  > The command was > MAKE="make -j8" make build > Running it a second time lead to a successful build

[sage-devel] sage Python3 build: sagenb problem

I tried to build Sage with Python3 via make configure ./configure --with-python=3 make build (fresh clone of 8.5.beta1) as announced on https://wiki.sagemath.org/Python3-compatible%20code but it failed building its docs. From what I read, building the docs does still not work (part of the log

Re: [sage-devel] Re: number field: exactness of result of abs

Thank you for your detailed explaination. On 2018-10-25 11:09, John Cremona wrote: > Personally I cannot think of a reason why one would want this abs() to > be returned as an algebraic number, since the whole point of absolute > values in algebraic number theory is that they like in some

[sage-devel] number field: exactness of result of abs

Dear all, we have sage: C. = CyclotomicField(60) sage: abs(z) 1.00 sage: abs(z).parent() Real Field with 53 bits of precision What is the reason, why this returns an inexact result and not something in an exact ring like QQbar? Best wishes Daniel -- You received this message

[sage-devel] no conversion between number fields (extensions) over base rings which have conversion

sage: CyclotomicField(3).extension(x^2+1, 'i')(QQ.extension(x^2+1, 'i').gen()) returns TypeError: Cannot coerce element into this number field Does anyone have some idea why this is not working? (This is https://trac.sagemath.org/ticket/26443) Best, Daniel -- You received this message

Re: [sage-devel] Re: Enabling Merge Requests from GitLab

On 09/04/2018 02:33 PM, Jeroen Demeyer wrote: > Let me make one important comment (something that I've said before > though): a large part of what makes the current workflow work is not so > much Trac itself but our git server and the "git trac" scripts. > > For example, I very much like the fact

Re: [sage-devel] failing doctest in function_field

On 08/29/2018 01:14 PM, Jeroen Demeyer wrote: > On 2018-08-29 13:11, Daniel Krenn wrote: >> Shouldn't we simply use >>    https://trac.sagemath.org/ticket/26150 >> ? > > How is conversion from the symbolic related to evaluating "r" as the R > interp

Re: [sage-devel] failing doctest in function_field

On 08/29/2018 12:59 PM, Jeroen Demeyer wrote: > Can you create a ticket for this such that we can discuss it there? Shouldn't we simply use https://trac.sagemath.org/ticket/26150 ? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] failing doctest in function_field

On 08/29/2018 12:39 PM, Daniel Krenn wrote: > In the element_constructor, there is the following (extracted): > sage: sage_eval('r', QQ['x'].fraction_field().gens_dict_recursive()) > R Interpreter > My intuition says that this should fail. For clearification, not the paricular c

Re: [sage-devel] failing doctest in function_field

On 08/29/2018 10:13 AM, Daniel Krenn wrote: > A simple fix in > https://trac.sagemath.org/ticket/26150 > (fraction field: fix conversion from symbolic ring) > turns out to have an side effect in function_field: > > File "src/sage/rings/function_field/functi

[sage-devel] failing doctest in function_field

A simple fix in https://trac.sagemath.org/ticket/26150 (fraction field: fix conversion from symbolic ring) turns out to have an side effect in function_field: File "src/sage/rings/function_field/function_field.py", line 1602, in sage.rings.function_field.function_field.FunctionField_polymod.hom

Re: [sage-devel] Re: Enabling Merge Requests from GitLab

On 08/23/2018 11:15 AM, Dima Pasechnik wrote: > github has a command line tool, called hub, allowing one to e.g. create pull > requests and issues, without using a browser. > https://hub.github.com/hub-pull-request.1.html > https://hub.github.com/hub-issue.1.html > > I don't know whether gitlab

Re: [sage-devel] Enabling Merge Requests from GitLab

On 08/21/2018 10:43 AM, Erik Bray wrote: > https://gitlab.com/sagemath/sage How do I become a member of the SageMath group (or the project) in Gitlab? (username: dakrenn) Best Daniel -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] installation fortran

On 08/19/2018 08:06 PM, Mathieu Roux wrote: > but i have just installed my new linux, after formating hard disk... I > took last version of linux mint cinnamon. > > What can i do? Is there a new solution but building sage from sources? FWIW, I just did the same: format, install current linux

Re: [sage-devel] Release schedule survey

On 2018-07-19 08:50, Jeroen Demeyer wrote: > On 2018-07-19 00:24, Volker Braun wrote: >> Since Erik is clamoring for a more calendar-driven release schedule, >> here is a quick A/B test: >> >> A) Keep the current process of releasing approximately every 3 months, >> longer if people insist on

Re: [sage-devel] error compiling 8.2: openblas, lgfortran

On 2018-05-17 16:44, Jeroen Demeyer wrote: > On 2018-05-17 15:58, Daniel Krenn wrote: >> Sorry, now found it exactly there (modulo version which is 4.8) > > So, the question is: why is it not found? I'm afraid I cannot help you > further here... Ok, thank you for your help. &

Re: [sage-devel] error compiling 8.2: openblas, lgfortran

On 2018-05-17 15:48, Jeroen Demeyer wrote: > On 2018-05-17 15:29, Daniel Krenn wrote: >> On 2018-05-17 15:13, Jeroen Demeyer wrote: >>> Is libgfortran.so installed >>> somewhere on your system? >> >> I did not find this file anywhere. > > There's your

Re: [sage-devel] error compiling 8.2: openblas, lgfortran

On 2018-05-17 15:13, Jeroen Demeyer wrote: > On 2018-05-17 14:45, Daniel Krenn wrote: >> Compiling 8.2 from scatch (on a system that worked for 8.1) breaks with >> the errors below. >> Any ideas why? > > Your gfortran installation is messed up somehow. Are you

[sage-devel] error compiling 8.2: openblas, lgfortran

Compiling 8.2 from scatch (on a system that worked for 8.1) breaks with the errors below. Any ideas why? Best, Daniel [openblas-0.2.20.p1] make[4]: Entering directory `/local/dakrenn/sage/8.2/local/var/tmp/sage/build/openblas-0.2.20.p1/src/exports' [openblas-0.2.20.p1] gcc -O2

Re: [sage-devel] Whitespace patchbombs

On 2018-02-20 21:47, Jeroen Demeyer wrote: > Interesting fact: the number of lines with trailing whitespace is > generally *increasing* with every Sage release. So it seems to me that > the biggest problem (if you find whitespace a problem) is preventing new > whitespace. So, there should be a

Re: [sage-devel] Re: Whitespace patchbombs

On 2018-02-20 12:07, Simon King wrote: > Why not doing such cleanup right before releasing a beta version? Or even better, right before a release, e.g. doing it for a rc0 or rc1. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] Re: Merge fails of positive ticket HOWTO

On 2018-01-05 13:00, Erik Bray wrote: > On Thu, Jan 4, 2018 at 10:26 PM, Jeroen Demeyer > wrote: >> On 2018-01-02 22:59, Volker Braun wrote: >>> >>> IMHO it shouldn't be easy to find. Certainly nobody should base their >>> work on it. >> >> >> I agree here. > > I don't,

[sage-devel] solve and conjugate bug

Is the following a known bug? sage: var('z') z sage: z0all = solve(z - 4*z.conjugate() == 1 + 3*I, z); z0all [z == (-I - 1/3)] sage: z0 = z0all[0].rhs(); z0 -I - 1/3 sage: (z0 - 4*z0.conjugate()) - (1 + 3*I) -8*I Clearly, the result of solve is not a solution of the given equation. -- You

Re: [sage-devel] What does MPolynomial_libsingular.reduce() do?

On 2017-10-17 11:49, Luca De Feo wrote: >> It takes I as the generators of the ideal and uses that as the reduction >> set. > > That's not a definition. I'm in front of a class asking what this > function does, and I'm unable to give a mathematical definition of > what Sage means by "reduction"

Re: [sage-devel] How do I overwrite comparison for modules?

On 2017-10-17 12:13, Simon Brandhorst wrote: > Because the documentation did not tell me it was possible: Maybe sage.structure.richcmp.richcmp_by_eq_and_lt is something for you (see also L1100 in sage/rings/asymptotic/growth_group.py). Daniel -- You received this message because you are

Re: [sage-devel] What does MPolynomial_libsingular.reduce() do?

On 2017-10-16 18:41, Luca De Feo wrote: > Here's a Sage session: > > sage: A. = QQ[] > sage: (x+y).reduce([(x-y), (x+y)]) > 0 > sage: (x-y).reduce([(x-y), (x+y)]) > -2*y > > The docstring says reduce computes "the normal form of self w.r.t. I, > i.e. [...] the remainder

Re: [sage-devel] git trac is down ?

On 2017-09-12 12:49, Daniel Krenn wrote: > On 2017-09-12 12:04, Frédéric Chapoton wrote: >> I have access failures to the git repo from trac : >> >> chapoton@pc-chapoton:~/sage$ git pull trac >> u/mantepse/fricas_output_and_sage_conversion_bug >> fatal: read error

Re: [sage-devel] git trac is down ?

On 2017-09-12 12:04, Frédéric Chapoton wrote: > I have access failures to the git repo from trac : > > chapoton@pc-chapoton:~/sage$ git pull trac > u/mantepse/fricas_output_and_sage_conversion_bug > fatal: read error: Connexion ré-initialisée par le correspondant > > Does anybody else suffers

[sage-devel] Re: [sage-release] Sage 8.0 released

On 2017-07-22 00:43, Volker Braun wrote: > The "master" git branch has been updated to Sage-8.0. make ptestlong produced the failing doctest below. Trying again with "sage -t --long src/sage/interfaces/rubik.py" let the test pass. Is this something known? sage -t --long

Re: [sage-devel] English translation of "Calcul Mathématique avec Sage" and Python 3

On 2017-08-28 12:45, Nicolas M. Thiery wrote: > - Do you foresee other sources of problems? Recommend other tests to run? I've just randomly looked at some of the pages and found filter (is_prime, [1..55]) When I am correct, this will be an iterator in Python 3 (and is a list now). There are

Re: [sage-devel] Calculation Error

On 2017-08-26 02:40, David Roe wrote: > This is not a bug. If you look at the documentation for > Integer.__pow__, you'll see "For consistency with Python and MPFR, 0^0 > is defined to be 1 in Sage." To avoid such a discussion in future: https://trac.sagemath.org/ticket/23735 (with the link

Re: [sage-devel] Re: sage -docbuild useless

On 2017-08-21 15:08, Ralf Stephan wrote: > Ah the citations need a make and will not compile with a simple sage > -docbuild. So it really is useless and should be disabled to not confuse > people like me. I am strongly against disabling "sage -docbuild": When developing and only changing e.g.

[sage-devel] doctests: non-sorted output

A patchbot reported two failing doctests because the result is a set and the elements were in a different order, see https://trac.sagemath.org/ticket/23637 I somehow remember that such an issue was discussed here and I thought it was about the output of dict and set being sorted by a display

Re: [sage-devel] 0 should not be a primitive root

On 2017-08-14 18:37, Will Song wrote: > Not sure if this is a known bug or not. > > SageMath version 8.0, Release Date: 2017-07-21 > > sage: mod(0, 17).is_primitive_root() > True > > The easy fix would just be to add > > if self == 0: > return True > > after >

Re: [sage-devel] Sorting strings and integers

On 2017-08-07 22:53, David Roe wrote: > >>> sorted([1,2,'a']) > Traceback (most recent call last): > File "", line 1, in > TypeError: '<' not supported between instances of 'str' and 'int' > [...] > Which still leaves the second part of Stefan's question: how do we get >

Re: [sage-devel] testing docstrings

On 2017-08-04 16:32, John Cremona wrote: > Is there a quicker way to check docstrings for syntax and appearance > than "make doc" which takes a very long times as it builds all of the > docs? I have only changed 3 files and want to keeping making the docs > on those. I suppose that after doing

Re: [sage-devel] Re: Bug in groebner_basis()?

On 2017-07-14 16:41, Simon King wrote: > On 2017-07-14, Johannes Schwab wrote: >> Here is the code: >> R. = PolynomialRing(QQ, 'lex') > That's not what you want. > [...] > Instead you have to do > sage: R. = PolynomialRing(QQ, order='lex') > (i.e., specify what

Re: [sage-devel] Question on git merge

On 2017-07-11 14:39, Simon King wrote: > Being on a different git branch, I tried >git cherry-pick xyz Why cherry-pick and not simply git merge xyz ? This could git help finding a proper merge base. -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Old-style packages

On 2017-07-05 14:50, Jeroen Demeyer wrote: > TL;DR: should we drop support for old-style .spkg packages completely in > Sage? Will this mean that they stop working immediately or they will only be broken if certain parts in SageMath are altered by some (future) ticket/fix etc.? -- You received

Re: [sage-devel] Simple new patchbot feature I'd like to add

On 2017-06-26 13:26, Erik Bray wrote: > I submitted a PR [1] to the sage patchbot to add a feature I would > like to have, that re-runs failed tests one or more times. If > previously failing tests pass on a repeat attempt then the test is > considered "passing". However, I added a new return

Re: [sage-devel] the overhead of sorting in .roots()

On 2017-06-12 07:21, Nils Bruin wrote: > How attached are people to creating deterministic output where none is > warranted? > > Currently, there is a "sort" routine in f.roots which creates a 60% > overhead: > > sage: C=ComplexField(100) > sage: %timeit f.roots(multiplicities=False) > 1000

Re: [sage-devel] Sage Python 3 proposal

On 2017-06-01 16:35, William Stein wrote: > The second oldest is "notebook -- should be able export (=print) to > latex/pdf/dvi", which could be finally closed when Jupyter notebook is > the default notebook Does typeset output meanwhile work? (I ask as, having e.g. show(x^2) in a Jupyter

Re: [sage-devel] Re: Poll for issue G1 a specific guideline for writing docstrings

On 2017-05-23 04:16, Nicolas M. Thiery wrote: > For how to typeset True/False/None/... when we need to spell them out > explicitly, as already suggested, I would be in favor of :obj:`True`. I wasn't aware that this works. But in this case, I am in favor (+1) of :obj:`True` as well. Best Daniel

Re: [sage-devel] Second round poll for H5 a specific guideline for writing docstrings

On 2017-05-22 12:08, Jeroen Demeyer wrote: > On 2017-05-22 12:05, Kwankyu Lee wrote: >> My opinion is that the phrase "a tuple `(a,b,c)` where ..." is just >> redundant. > > I think that "a tuple" is important non-redundant information. +1 for "a tuple" in this case (and not skipping this

Re: [sage-devel] Re: Second round poll for H2 a specific guideline for writing docstrings

On 2017-05-20 00:03, Kwankyu Lee wrote: > This is my last attempt to save the guideline. > > A Sage user has an integer X. He hit the tab key and get "X.is_prime", > and then ask what this method does by entering "X.is_prime?". Imagine > that he reads > > (1) Return whether the integer is prime.

Re: [sage-devel] Second round poll for H5 a specific guideline for writing docstrings

On 2017-05-19 08:57, Jeroen Demeyer wrote: > As I mentioned on the other thread, since OUTPUT is not a list of things > (as opposed to INPUT), I would prefer > > OUTPUT: tuple of lattices +1 for this option -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Second round poll for H4 a specific guideline for writing docstrings

On 2017-05-19 00:24, Kwankyu Lee wrote: > I prepared H4 revised from G4 based on your ideas and wishes. It was > hard to make a compromise from your differing opinions and reach a > proposal for the better. So this time_ if I fail to get approval from > most of you, the guideline will be simply

Re: [sage-devel] Second round poll for H3 a specific guideline for writing docstrings

On 2017-05-19 00:22, Kwankyu Lee wrote: > I prepared H3 revised from G3 based on your ideas and wishes. It was > hard to make a compromise from your differing opinions and reach a > proposal for the better. So this time_ if I fail to get approval from > most of you, the guideline will be simply

Re: [sage-devel] Second round poll for H2 a specific guideline for writing docstrings

On 2017-05-19 00:20, Kwankyu Lee wrote: > Hi, > > I prepared H2 revised from G2 based on your ideas and wishes. It was > hard to make a compromise from your differing opinions and reach a > proposal for the better. So this time_ if I fail to get approval from > most of you, the guideline will be

Re: [sage-devel] Re: Second round poll for H1 a specific guideline for writing docstrings

On 2017-05-19 08:35, Simon King wrote: > PS, to the +1 given earlier: I suggest that one should also write `f(x)` > instead of f(x). +1 -- 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

Re: [sage-devel] Second round poll for H1 a specific guideline for writing docstrings

On 2017-05-19 00:17, Kwankyu Lee wrote: > I prepared H1 revised from G1 based on your ideas and wishes. It was > hard to make a compromise from your differing opinions and reach a > proposal for the better. So this time_if I fail to get approval from > most of you, the guideline will be simply

Re: [sage-devel] Poll for issue G2 a specific guideline for writing docstrings

On 2017-05-17 17:17, Jeroen Demeyer wrote: > On 2017-05-17 17:10, Daniel Krenn wrote: >> I find this perfectly fine. I personally would write "Return whether >> this lattice is contained in the other lattice", but I do not find any >> need to include ``self`` in the

Re: [sage-devel] Re: Unifying "test::" and "tests::"

On 2017-05-17 14:13, Kwankyu Lee wrote: > I agree; in the formatteed text, there should not be quotes, > > > In terminal and jupyter, ``True`` is rendered "True". I think this is > ugly. It should be rendered True > > > but it should also not be formatted as plain text. > > > Why

Re: [sage-devel] Poll for issue G2 a specific guideline for writing docstrings

On 2017-05-17 17:00, Jeroen Demeyer wrote: > def is_sublattice(self, other): > """ > Return ``True`` if this lattice is contained > in the other lattice. > """ > > In this case, it would be better to refer to ``self`` and ``other``. I find this perfectly fine. I personally would

Re: [sage-devel] Re: Unifying "test::" and "tests::"

On 2017-05-17 13:40, Kwankyu Lee wrote: > I am simply asking why we aren't writing a docstring as > > "Return True if " > > instead of > > "Return ``True`` if ..." > > just like > > "Return an integer ..." > > instead of > > "Return an ``Integer``" Because ``True`` is an object of

Re: [sage-devel] Poll for issue G1 a specific guideline for writing docstrings

On 2017-05-17 16:07, Kwankyu Lee wrote: > We do a poll for adopting an official guideline for docstrings > (see https://trac.sagemath.org/ticket/23017) > > G1. Write > > | > Return True if something is true. > | > > but do not write > > | > Return ``True`` if something is true. > |

Re: [sage-devel] Poll for issue G2 a specific guideline for writing docstrings

On 2017-05-17 16:11, Kwankyu Lee wrote: > We do a poll for adopting an official guideline for docstrings > (see https://trac.sagemath.org/ticket/23017 > ) > > G2. Write > > | > if the lattice is reflexive ... > | > > but don't write > > | > if

Re: [sage-devel] Poll for issue G3 a specific guideline for writing docstrings

On 2017-05-17 16:16, Kwankyu Lee wrote: > | > Return whether the lattice is reflexive. > | +1 for the above option. (i.e. -1 in the sense of this poll) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

Re: [sage-devel] Poll for issue G4 a specific guideline for writing docstrings

On 2017-05-17 16:24, Kwankyu Lee wrote: > We do a poll for adopting an official guideline for docstrings > (see https://trac.sagemath.org/ticket/23017 > ) > > G4. OUTPUT block is optional > > The developer manual says OUTPUT block is not

Re: [sage-devel] Poll for issue G5 a specific guideline for writing docstrings

On 2017-05-17 16:30, Kwankyu Lee wrote: > We do a poll for adopting an official guideline for docstrings > (see https://trac.sagemath.org/ticket/23017 > ) > > G5. Write > > | > OUTPUT: > > - lattice > | > > > but do not write > > | > OUTPUT: >

Re: [sage-devel] Re: Unifying "test::" and "tests::"

On 2017-05-17 10:51, Kwankyu Lee wrote: > I am for writing double-quotes ``True``, ``False``, ``None``, as > this is > the "offical" representation of these objects and therefore is printed > as output. Thus a typewriter-font is appropriate. > > > In what sense, is it official?

  1   2   3   4   >