Re: [sage-devel] Re: New labels v: mimimal, v: small ... on pull requests

I fully agree with Travis. I do not see the added value of these additional tags. On Thu, 9 May 2024 at 23:46, Travis Scrimshaw wrote: > > I am *very* strongly opposed to these tags. Their cutoffs are arbitrary nor > they serve no useful purpose as far as I can tell. To this point, they do not

Re: [sage-devel] Re: Matrices over QQbar

0) > and optimizing them away might maybe improve performance? Just an idea, I > haven't done any benchmarking to support that hypothesis. > > Best regards, > > Håkan > > On Mon, May 6, 2024 at 12:15 AM Vincent Delecroix <20100.delecr...@gmail.com> > wrote: &

Re: [sage-devel] Re: Matrices over QQbar

Turns out to be a serious bug in complex interval fields. The problem is hopefully fixed by https://github.com/sagemath/sage/pull/37941 which should make its way to the next sage release. Thanks again for your report. Vincent On Fri, 3 May 2024 at 18:13, vdelecroix <20100.delecr...@gmail.com>

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

I do not remember anything specific about solve_mod. Though, there are many places in Cython source code where sig_on/sig_off is not handled carefully enough (and many that were fixed). The fact that it is not reproducible is not necessarily a huge problem. However, - Could you share the code (as

Re: [sage-devel] Re: stopping cypari2, pari-jupyter and pplpy maintenance

ojects, then I'll use the same deployment > key that the other sagemath projects use for pushing releases to PyPI. > https://github.com/sagemath/cypari2/pull/141 is already prepared for this, > and I can add the same for the other projects. > > Matthias > > On Tuesday, Ma

Re: [sage-devel] stopping cypari2, pari-jupyter and pplpy maintenance

y annoying > about the direction of these projects? Thanks for any insight to help guide > whoever takes over. > > -- William > > On Tue, Mar 12, 2024 at 10:44 AM Vincent Delecroix > <20100.delecr...@gmail.com> wrote: >> >> Dear all, >> >> I used to be

[sage-devel] stopping cypari2, pari-jupyter and pplpy maintenance

Dear all, I used to be the maintainer of cypari2, pari-jupyter and pplpy. I will not work anymore on any of them from now on. The three projects are under the sagemath organization on github so that any administrator can take over. Concerning the access to PyPI to push releases I can promote

Re: [sage-devel] VOTE: Use "CI Fix" label for merging into continuous integration runs

+1 On Mon, 4 Mar 2024 at 20:21, G. M.-S. wrote: > > > +1 > > Guillermo > > On Mon, 4 Mar 2024 at 09:43, David Roe wrote: >> >> The following proposal has been made several times the last few weeks: in PR >> #37428, in this thread and then in this thread. It is orthogonal to the >> ongoing

Re: [sage-devel] VOTE: disputed PRs

+1 On Mon, 4 Mar 2024 at 20:20, G. M.-S. wrote: > > > +1 > > Guillermo > > On Mon, 4 Mar 2024 at 09:23, David Roe wrote: >> >> With no further discussion on this thread, I'm calling a vote on a new >> process for resolving disagreements on a PR. >> >> Proposal >> It is now allowed to vote on

Re: [sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

On Thu, 29 Feb 2024 at 01:49, Kwankyu Lee wrote: > > > > On Thursday, February 29, 2024 at 8:35:24 AM UTC+9 Marc Culler wrote: > > I have a proposal: It should be forbidden to call for a vote on a proposal > before there has been a discussion. > > > Sorry if it was not clear to you, but the

Re: [sage-devel] Re: Unload "blocker" label

tthias Koeppe wrote: > > On Monday, February 26, 2024 at 5:31:47 AM UTC-8 Kwankyu Lee wrote: > > Anyway, as there are only objections here, I give up. > > Thanks for opinions. > > > On Monday, February 26, 2024 at 6:02:41 AM UTC-8 Vincent Delecroix wrote: > > Dear

Re: [sage-devel] Re: Unload "blocker" label

Dear Kwankyu, Note that everybody who kindly took the time to consider your proposal responded the same : it seems more consistent to have only two categories {1, 3} and {2} rather than three (following your numbering). Either you give up because people disagree with you (which is a problem

Re: [sage-devel] Re: Unload "blocker" label

Hi Kwankyu, I do not agree with usage 3: Issues that should be fixed as fast as possible To me it is rather "issues that should be fixed before the next release" (or at least it was the way it was supposed to work when we had trac). This looks better to me as that there is no reason to release

Re: [sage-devel] One year of Sage development on GitHub

I fully second the observation of Michael though it might have few to do with the github switch. Sage development nowadays does not seem to be anymore about math research and efficient computations but mostly about "dependencies", "infrastructure" and "maintenance". I am always depressed by

Re: [sage-devel] Re: Exception in floor(tanh(91))

The following is the proper way to extract digits sage: tanh(91).numerical_approx(digits=10) 1.0 sage: tanh(91).numerical_approx(digits=100) 0.998182667935304138503930 On Fri, 9 Feb 2024 at 17:16, Georgi Guninski

Re: [sage-devel] Unable to `load` or `import/cimport` Cython files into Sage while developing

Dear Jing, Not being able to use Cython from this sage app is indeed problematic. However as Dima said this is more a problem of the app rather than a problem with sage itself. You would better open an issue at https://github.com/3-manifolds/Sage_macOS. If you do, please post the link of the

Re: [sage-devel] What's the point of GF(2, impl='ntl')?

ling to add all of the > doctests that should really be added? > > On Friday, September 29, 2023 at 12:32:14 AM UTC-7 Vincent Delecroix wrote: >> >> What is your sage version? How did you install it? Did you open an >> issue on github? >> >> Best >>

Re: [sage-devel] What's the point of GF(2, impl='ntl')?

What is your sage version? How did you install it? Did you open an issue on github? Best Vincent On Tue, 26 Sept 2023 at 07:00, John H Palmieri wrote: > > Setup: > > sage: F = GF(2, impl='ntl') > sage: m_ntl = identity_matrix(1, F) > sage: v_ntl = vector(F, (1,)) > > Now consider > > sage:

Re: [sage-devel] opinions requested on x + y behaviour for polynomials

Hi Frederic, My opinion is that if there is a single non-ambiguous canonical parent, then yes. In the case of polynomial rings I think that the priority is to fix the following kind of non-commutativity in coercion ``` sage: cm = get_coercion_model() sage: cm.common_parent(QQ['x,y'], QQ['y,x'])

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

n calling `__repr__` if `sort=True`. > The alternative is to sort at the initialization of the object and to cache > the sorted list of edges in the object. > Should we go for this alternative implementation ? > > On Wednesday, July 5, 2023 at 8:48:05 AM UTC+2 Vincent Delecroix

Re: [sage-devel] Re: Exception in `G=Graph([("A",1)]);G.faces()`

On Wed, 5 Jul 2023 at 17:51, Georgi Guninski wrote: > > On Wed, Jul 5, 2023 at 4:05 PM David Coudert wrote: > > > > I have opened https://github.com/sagemath/sage/issues/35902 to collect such > > kind of issues. > > Please use it to share new cases. > > > I just reported a bug on github, though

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

will > be set to False by default in the future See > https://github.com/sagemath/sage/issues/27408 for details. > Graph([('A','B'),(Integer(1),Integer(2))]).edges() > ) failed: TypeError: > unsupported operand parent(s) for <: 'Integer Ring' and ''> > > > On Tuesd

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

https://github.com/sagemath/sage/issues/35897 On Tue, 4 Jul 2023 at 16:25, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > This is a bug in the __repr__ method of EdgesView. Thanks for your report. > > On Tue, 4 Jul 2023 at 10:52, Georgi Guninski wrote: > > &

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

This is a bug in the __repr__ method of EdgesView. Thanks for your report. On Tue, 4 Jul 2023 at 10:52, Georgi Guninski wrote: > > Graph([('A','B'),(1,2)]).edges() > ) failed: > TypeError: unsupported operand parent(s) for <: 'Integer Ring' and > ''> > > I think this is related to sorting the

Re: [sage-devel] Isomorphic multi digraphs have distinct number of spanning trees, bug?

You could also check equality for all vertices with sage: ans, isom = G1.is_isomorphic(G2, certificate=True) sage: all(G1.spanning_trees_count(u) == G2.spanning_trees_count(isom[u]) for u in G1.vertices(sort=False)) True On Sun, 18 Jun 2023 at 10:09, Dima Pasechnik wrote: > > It could be an

Re: [sage-devel] Isomorphic multi digraphs have distinct number of spanning trees, bug?

sage: G1.spanning_trees_count(root_vertex=0) 27202601182632270746156805986464038912000 sage: G2.spanning_trees_count(root_vertex=6) 27202601182632270746156805986464038912000 On Sun, 18 Jun 2023 at 09:49, Georgi Guninski wrote: > > On Sun, Jun 18, 2023 at 10:16 AM Emmanuel Briand > wrote: > > >

Re: [sage-devel] compiling sage without documentation

Thanks Dima. Is there a way I can figure out by myself which info is up to date? On Thu, 16 Mar 2023 at 11:30, Dima Pasechnik wrote: > > On Thu, Mar 16, 2023 at 10:00 AM Vincent Delecroix > <20100.delecr...@gmail.com> wrote: > > > > Dear all, > > > &g

[sage-devel] compiling sage without documentation

Dear all, I would like to compile sage without the documentation. According to ./configure --help I supposed the following would just work ./configure --with-sage_docbuild=no --with-pplpy_doc=no --with-sagemath_doc_html=no --with-sagemath_doc_pdf=no But I got configure: WARNING: unrecognized

Re: [sage-devel] weird commits on top of develop

in develop > to fix such things. > We do have OK from Volker for these fixes. > > This time I got confused and pushed a totally irrelevant change (which did > not break develop, it just had no effect on anything at all). > > Dima > > > > > On Sun, 26 Feb 2023, 10:1

Re: [sage-devel] weird commits on top of develop

I do not understand why develop isn't protected against anybody but the release manager pushes. On Sun, 26 Feb 2023 at 11:16, Dima Pasechnik wrote: > > it was a mistake on my side - I thought develop branch was broken, but it was > not. > > On Sun, 26 Feb 2023, 10:13 Vincent De

[sage-devel] weird commits on top of develop

Hello, Why do we have commits on top of develop after the release commits? Namely commit 52a81cbd161ef4d5895325657c88a68590ea1d3b Author: Dima Pasechnik Date: Fri Feb 24 21:15:42 2023 + Revert "add missing # optional - gap3" This reverts commit

Re: [sage-devel] Procedure to be a member of sage github organization

I think that the needs_review positive_review tags do not fit well in the github workflow. These have been kept to mimic the trac workflow but are annoying. I support Edgar suggestion that the "needs review tag" should be replaced by "not a draft" status. Similarly, the "positive review tag" would

Re: [sage-devel] online talk about the github workflow

The video should be available at https://webconf.u-bordeaux.fr/b/vin-g33-6qy at the bottom of the page. Vincent https://visio.u-bordeaux.fr/playback/presentation/2.0/playback.html?meetingId=887e0bfc02a9a556a1ea79a2c1d59e3cb7717460-1675700189259 On 06/02/2023, Matthias Koeppe wrote: > The notes

Re: [sage-devel] online talk about the github workflow

Talk will start in about 10min from now at https://webconf.u-bordeaux.fr/b/vin-g33-6qy On 03/02/2023, Matthias Koeppe wrote: > Recording my talk is, of course, fine with me. > > On Friday, February 3, 2023 at 1:38:33 AM UTC-8 vdelecroix wrote: > >> This could be recorded (if Matthias

Re: [sage-devel] online talk about the github workflow

This could be recorded (if Matthias agree) and available on the BBB website. I do not know how to make a proper video out of the BBB recording and will not spend anytime on it. Anybody with this knowledge is welcome to make that happen. Best Vincent On Thu, 2 Feb 2023 at 22:36, François Bissey

[sage-devel] wiki access

Dear all, It seems that it is not possible anymore to log in for editing the SageMath wiki at https://wiki.sagemath.org/. This is the tool we were planning to use for sage days 117 starting on Monday. Does anyone know what happened? Best Vincent -- You received this message because you are

[sage-devel] online talk about the github workflow

Dear all, As part of the sage days 117 (https://wiki.sagemath.org/days117) Matthias Köppe will give on online talk about the new github workflow for SageMath development. It will happen on Monday Feb 6th at 17:30 CET (= UTC+1). For those who want to join, it will happen on

[sage-devel] Is R on the system needed to compile sage?

Hello, In a fresh cloned environment (9.8.beta7) I tried to build sage and it ended with the failure of r-none (as it is a dummy package). It appears that r is not installed on my system. Though is it a requirement? Nothing in configure warned me so. Best Vincent -- You received this message

Re: [sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

On Thu, 15 Dec 2022 at 01:42, Dima Pasechnik wrote: > > > > On Wed, 14 Dec 2022, 21:06 Vincent Delecroix, <20100.delecr...@gmail.com> > wrote: >> >> Note that in #34850 I execute the very same command, namely >> pari("quadclassunit(1 - 2^100)&q

Re: [sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

I vaguely recall something about the way gp is built, without linking > >> libpari dynamically, and something about gp getting slower if built with > >> threads. > >> > >> So, probably, more info is needed on how exactly your comparisons are > >&g

[sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

Dear all, Some strange phenomenon makes execution of PARI/GP up to twice slower when ran inside a Python process compared to its execution in GP. Though this is not systematic, in a fresh python environment timing are comparable with GP. The slowdown has been first observed in the context of

Re: [sage-devel] Re: sagelib fails to build (9.8.beta5)

I managed to build (though doc-build failed). Thanks. On Wed, 14 Dec 2022 at 19:53, Matthias Koeppe wrote: > > No, you need to apply it to the source tree using "patch -p1" > > On Wednesday, December 14, 2022 at 5:55:04 AM UTC-8 vdelecroix wrote: >> >> In order to build, is it fine to just add

Re: [sage-devel] Re: sagelib fails to build (9.8.beta5)

In order to build, is it fine to just add this patch to `SAGE_DIR/build/pkg/sagelib/patches/`? On Wed, 14 Dec 2022 at 14:50, Antonio Rojas wrote: > > That's the singular 4.3.1.p3 update. The patch [1] fixes the build, but there > are some regressions in the asymptotics ring that need looked

[sage-devel] about cypari2 development amd maintenance on github

Dear all, I am one of the maintainer of cypari2. Contrarily to Jeroen and Luca who left, I am not a number theorist and not a specialist of PARI/GP. I took over the maintainance responsability because it felt like a good thing for the math community and because PARI development happens in a

[sage-devel] cypari2 release 2.1.3

Dear all, There is a new release of cypari2 now on PyPI https://pypi.org/project/cypari2/2.1.3/ Thanks to the help of Isuru Fernando, Jerry James, Jonathan Kliem and Gonzalo Tornaría cypari2 supports the most recent Python and PARI versions. Best Vincent -- You received this message because

Re: [sage-devel] Re: Democratic issue: rushing decisions

Dear all, I do not interpret Thierry message as an attempt to change the issue of the vote. Most of the answers focused on this particular point and hence look completely off topic to me. More dramatically they are also very rude in that they try to discredit what Thierry attempted to share. I

Re: [sage-devel] is there a convention for _bool_ was: is it intentional that prod does not stop when it hits 0?

You are right of course (my bad): bool(expr) could be considered as being True according to these specifications (and anyway "True" is always a good answer). Though these are specifications for SR and does not apply to the entire library. It is not clear to me what global specification we could

Re: [sage-devel] is there a convention for _bool_ was: is it intentional that prod does not stop when it hits 0?

On Tue, 27 Sept 2022 at 11:58, 'Martin R' via sage-devel wrote: > > > > On Friday, 23 September 2022 at 20:09:55 UTC+2 Nils Bruin wrote: >> >> On Friday, 23 September 2022 at 10:37:01 UTC-7 axio...@yahoo.de wrote: >>> >>> OK, this is off topic, but: shouldn't it be this convention? At least:

Re: [sage-devel] Re: VOTE: move Sage development to Github

-1 On Fri, 23 Sept 2022 at 12:43, Marc Mezzarobba wrote: > > Emmanuel Charpentier wrote: > > +1 for Github > > > > Also wishing for contingency plan for re-migrating to self-hosted > > Gitlab. > > Same here. > > -- > Marc > > -- > You received this message because you are subscribed to the

[sage-devel] PARI/GP upgrade to 2.15

Dear all, The PARI/GP team is about to release a new version. I opened a ticket for that purpose at https://trac.sagemath.org/ticket/34537. It went relatively smoothly with respect to building. However there are a lot of doctest failures in a lot of different files that I am not familiar about.

Re: [sage-devel] A list of file with deprecation

> I have a question: given a trac ticket number, is there a way of recover the > "Merge In" field of the ticket with the command line? I'd like to > automatically add this info to the list. For that purpose, the git trac command line tool is very helpful ``` $ git trac find

Re: [sage-devel] Re: On changing Bernoulli(1) to +½

PARI/GP actually has a better convention : only even Bernoulli numbers exist ? bernvec(5) %1 = [1, 1/6, -1/30, 1/42, -1/30, 5/66] And the two conventions can be recovered as evaluations of Bernoulli polynomials at 0 and 1 respectively ? [subst(bernpol(n), x, 0) | n <- [1..6]] %2 = [-1/2, 1/6,

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Hello, I am in the same mood as Travis : if I was to consider a move to github I would like to have a clear and complete overview of the changes in the workflow (how do we set ticket dependencies? how reviews will work? management of releases? etc). For me the discussion in this thread is very

Re: [sage-devel] abort() in __gmpz_realloc of symbolic expression with `gmp: overflow in mpz type`

Indeed, there is something wrong with the error handling of exponents {{{ sage: a = 2 ** (2**63) Traceback (most recent call last): ... .../sage/rings/integer.pyx in sage.rings.integer.Integer._pow_ 2229 r = smallInteger(1) 2230 else: -> 2231 raise

Re: [sage-devel] Trac #34152 needs you (to vote)!

hybrid > copy files > sage pseudo package Vincent -- 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 view this

[sage-devel] Re: 9.7.beta8 build error jupyter_jsmol

Note that this looks like a network failure... but this is happening inside the jupyter_jsmol build which tries to install some javascript via npm. I thought that the package tarballs were supposed to contain everything to build by themselves. On Tue, 23 Aug 2022 at 18:27, Vincent Delecroix

Re: [sage-devel] Re: LazyPowerSeriesRing Replacement

On Mon, 15 Aug 2022 at 09:50, John Cremona wrote: > > On Mon, 15 Aug 2022 at 08:21, Kwankyu Lee wrote: > > > > If LazyTaylorSeriesRing could be a complete replacement of > > LazyPowerSeriesRing, then I think we should remove the old > > LazyPowerSeriesRing > > and rename LazyTaylorSeriesRing

Re: [sage-devel] Re: fractions of symmetric functions

On Tue, 9 Aug 2022 at 21:14, 'Martin R' via sage-devel wrote: > > I am guessing that part of the problem is > > sage: SymmetricFunctions(ZZ) in IntegralDomains() > False Though the following looks fine sage: SymmetricFunctions(ZZ).e() in IntegralDomains() True > The other problem is that

Re: [sage-devel] Proposal: make Furo a standard package

On Thu, 4 Aug 2022 at 08:16, Kwankyu Lee wrote: > > > > On Thursday, August 4, 2022 at 2:07:56 PM UTC+9 vdelecroix wrote: >> >> Let me add a note that I don't like so much the code blocks (ie >> EXAMPLES/TESTS). Namely, >> * the brackets and parenthesis are weirdly bold (maybe because of the >>

Re: [sage-devel] Proposal: make Furo a standard package

Thanks for working on this. +1 for making Furo standard. Let me add a note that I don't like so much the code blocks (ie EXAMPLES/TESTS). Namely, * the brackets and parenthesis are weirdly bold (maybe because of the fonts on my computer) * numbers appear in bold blue and we basically see only

[sage-devel] pplpy

Hello, Unless anyone disagrees, I will move the development of pplpy from gitlab (https://gitlab.com/videlec/pplpy) to github under the sagemath group. It will simplify the maintenance on my side. Best Vincent -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Error in matrix reduction

Indeed, calling previous_prime(p) with p=2 does not sound like a good idea :-) The following is very suspicious to me ~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/misc.pyx in sage.matrix.misc.matrix_rational_echelon_form_multimodular

Re: [sage-devel] sage -i normaliz fails on cygwin due to e-antic

Your compilation problem comes from the fact that antic (https://github.com/wbhart/antic) is not available. You should install it first. If you are familiar with (or curious about) compilation/installation in the sage environment you can install the full normaliz stack manually. Otherwise you

[sage-devel] docker image sagemath/sagemath-dev:develop performs full compilation

Dear all, When running $ docker run -it sagemath/sagemath-dev:develop the machine launches and starts compiling all of sage! Not sure when such behaviour started but something is definitely broken. Vincent -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] sage -i normaliz fails on cygwin due to e-antic

Hi Max, Could you try to build the last version of e-antic (1.2.1) in the sage environment ? In the sage shell, this is achieved with $ wget https://github.com/flatsurf/e-antic/releases/download/1.2.1/e-antic-1.2.1.tar.gz $ tar xf e-antic-1.2.1.tar.gz $ cd e-antic-1.2.1 $ ./configure

Re: [sage-devel] Adding a C or C++ Code to The SageMath

Autotools is convenient but definitely not mandatory. cmake does a similar job. Some projects (eg flint, PARI/GP) have a home made build system that works fine. What is required is: * a configuration step that let us specify the build directory, install directory, compilers, static versus dynamic

Re: [sage-devel] Re: Length of vectors in `plot_vector_field3d()`

On Mon, 20 Jun 2022 at 18:01, Niranjana K M wrote: > > @Vincent > > On Sun, Jun 19, 2022 at 5:52 PM Vincent Delecroix <20100.delecr...@gmail.com> > wrote: >> >> Nice catch indeed. I am not sure that "scaled=True/False" is the most >> flexible

Re: [sage-devel] Re: Length of vectors in `plot_vector_field3d()`

Nice catch indeed. I am not sure that "scaled=True/False" is the most flexible design. You might just want to apply *some* scale, not necessarily the one making the max length being one. I imagine that it would be nice to allow "scaled" to be a positive floating point number. In other words if

Re: [sage-devel] Sign issue in special values of Legendre Polynomials

There is indeed a problem sage: legendre_P(2, 0) 1/2 sage: legendre_P(2.0, 0.0) -0.500 On Mon, 6 Jun 2022 at 20:38, Dan Cross wrote: > > Hi, > It seems the special values of the Legendre Polynomials evaluated at zero are > hard coded to be positive, but the sign should alternate.

Re: [sage-devel] --patchbot

I guess this is https://wiki.sagemath.org/patchbot which has moved to https://trac.sagemath.org/wiki/patchbot Le 30/05/2022 à 14:37, ph h a écrit : Dear All, Is this link correct: https://wiki.sagemath.org/buildbot ? *This page does not exist yet. You can create a new empty page, or use one

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

Le 16/05/2022 à 12:35, Dima Pasechnik a écrit : On Mon, May 16, 2022 at 8:03 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: I would say that code with parallel computations + cypari2 should not be merged (as cypari2 does not support it). is it parallel multiproc

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

I would say that code with parallel computations + cypari2 should not be merged (as cypari2 does not support it). If you need parallel + PARI then use the C library directly with the appropriate threads locks. If the problem comes from somewhere else, then it would better be sorted out. Best

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

Probably related to https://github.com/sagemath/cypari2/issues/107 ? Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit : Hi everyone, On ticket #30423 , Dan, Willie, and I have been working on a parallel-computation based implementation

Re: [sage-devel] Jupyter Notebook requires Javascript

Dear Phiho, Please post your question on sage-support mailing list or the forum https://ask.sagemath.org/questions/. The sage-devel mailing list is, as its name suggests, about sage development. Best Vincent Le 10/05/2022 à 07:28, ph h a écrit : Dear All, This does not seem to work with IE

Re: [sage-devel] The SageMath developer map needs your (updated) information

It would be cool to have map locators for the quadruple (person, time, affiliation, trac id) (no affiliation being an option). That way we could make many maps out of one. And in particular visualize the evolution of sage development. Vincent Le 09/05/2022 à 09:59, David Roe a écrit : For

Re: [sage-devel] Closing the old Sage wiki

On the other hand, it was not clear to me that we would keep trac forever (eg moving to gitlab or github was mentioned several times). Migrating the wiki as you propose will make it harder to leave trac. 1) If it is just a problem of "login with github", why can't we provide github login to the

Re: [sage-devel] question on Python version when installing 9.6 beta 7

You could install the python3-dev Ubuntu package to fix the issue. Le 08/04/2022 à 05:32, 'Nasser M. Abbasi' via sage-devel a écrit : looking at config.log, it rejected the python version Python 3.10.4 I had because of this ## ## ##

Re: [sage-devel] ERROR In function "is_prime"

Which version of sage are you using? In a console I get sage: k=ZZ(18878585599102049192211644417) sage: k.is_prime() True sage: GF(k) Finite Field of size 18878585599102049192211644417 Le 02/04/2022 à 02:30, carlos ortiz a écrit : The number: 18878585599102049192211644417 = 61*2^88+1 but

[sage-devel] conventions about X.Graded() categories

Dear all, While fixing #33499 I wanted to implement a generic version at the level of categories (namely inside graded algebras). However, I did not find a place with the specifications of the Graded axiom... In particular - how do we specify the grading semi-ring on parents? - how do we access

[sage-devel] %lsmagic broken in sage interpreter

Dear all, The IPython magic %lsmagic is supposed to list the available magic functions. However, this does not seem to work within the sage interpreter $ sage -ipython [1]: %lsmagic Available line magics: %alias %alias_magic %autoawait ... But $ sage sage: %lsmagic Any idea on what is

Re: [sage-devel] Can we restore `mean`?

Le 13/02/2022 à 22:21, Matthias Koeppe a écrit : On Sunday, February 13, 2022 at 12:58:41 PM UTC-8 David Roe wrote: The documentation of Python's statistics module notes that "Unless explicitly noted, these functions support int, float, Decimal and Fraction. Behaviour with other types (whether

[sage-devel] documentation build complains about database Cremona (9.6.beta3)

Dear all, On a Ubuntu 20.04, documentation builds stops with [sagemath_doc_html-none] [plotting ] File "/home/debian/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/features/__init__.py", line 559, in absolute_path [sagemath_doc_html-none] [plotting ] raise

Re: [sage-devel] Possible bug: specifying category messes up coercion?

There is an explanation and a "solution" on the ticket. Best Vincent Le 03/02/2022 à 23:48, Akos M a écrit : Replacing 0 with self.zero() works perfectly, thank you! Best, Akos On Thursday, February 3, 2022 at 11:34:43 PM UTC+1 Akos M wrote: Thanks for the feedback. Indeed, defined as

Re: [sage-devel] Possible bug: specifying category messes up coercion?

Now I am thinking about it, I am not sure it is a bug. You did not defined any algebra structure (neither the unit nor the product on the basis). C is definitely a broken object. However, it would make sense for C(0) not to call C(1). Vincent Le 03/02/2022 à 21:49, Akos M a écrit : Thanks, I

Re: [sage-devel] Possible bug: specifying category messes up coercion?

Thanks for creating the ticket. Once the ticket is solved there are two routes to obtain a version of SageMath including the fix. * Either you obtain the corresponding git branch that will be attached to the ticket and compile this version of the source code * Or wait for a release of

Re: [sage-devel] Possible bug: specifying category messes up coercion?

It is definitely a bug. Do you know how to open a ticket on the trac server ? The infinite loop comes from C.one() calling C(1) calling C.one()... When you specify a category the inheritance is different and this explains the difference of behaviour. Best Vincent Le 03/02/2022 à 11:29, Akos M

Re: [sage-devel] Patchbot/CI improvements

Le 23/01/2022 à 18:35, Matthias Koeppe a écrit : Patchbot experts: 1) Currently the patchbot does not run on certain tickets that make changes to build/pkgs, so we do not have automatic testing for these tickets. Is this something that can be changed? I would say that this is doable (since if

Re: [sage-devel] not easily reproducible QQbar bug

I am not able to reproduce. I ran 1000 times the same code snippet you provided on all the sage that I have around me. Do you have the bug in a fresh session or after some hours of other unrelated computations? In the first case, you can try to reproduce with 1. In an instance where you have

Re: [sage-devel] not easily reproducible QQbar bug

Could you be more specific : Which sage version ? which setup ? Vincent Le 13/01/2022 à 15:05, 'Martin R' via sage-devel a écrit : I have some very strange behaviour of a substitution, which I don't know how to reproduce, but it happens from time to time, and is REALLY disturbing. I don't

[sage-devel] random doctest failure in BinaryQF.solve_integer

Dear all, In the following patchbot report https://patchbot.sagemath.org/log/32553/Linux/1_SMP_Debian_5.10.84-1_(2021-12-08)/x86_64/5.10.0-10-amd64/tmonteil-lxc3/2022-01-04%2017:18:22 one can see sage -t --long --random-seed=147150541496621216702880946653671608515

Re: [sage-devel] settings in github/sagemath

Le 26/12/2021 à 11:28, Dima Pasechnik a écrit : On Sun, Dec 26, 2021 at 9:42 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: Dear all, Jeroen kindly transfered pari_jupyter under the sagemath umbrella at https://github.com/sagemath/pari_jupyter However, I do not have

[sage-devel] settings in github/sagemath

Dear all, Jeroen kindly transfered pari_jupyter under the sagemath umbrella at https://github.com/sagemath/pari_jupyter However, I do not have enough the administrator rights for this repo. * Is there any administrator for the whole github/sagemath project that can grant me admistrator

Re: [sage-devel] patchbots open maxima threads and don't close them

More precisely I had 3 x 3 groups of processes (each time, killing one of them killed the other 2 in the same group). Vincent Le 13/12/2021 à 15:52, Vincent Delecroix a écrit : Are these really threads? I think they are independent processes (otherwise they would be closed at the time sage

Re: [sage-devel] patchbots open maxima threads and don't close them

Are these really threads? I think they are independent processes (otherwise they would be closed at the time sage terminates its test). I observe the same invasion on my patchbot. But they not only eat memory but also CPU. Vincent Le 13/12/2021 à 10:53, 'jonatha...@googlemail.com' via

[sage-devel] pari-jupyter is back

Dear all, The jupyter kernel for PARI/GP developed by Jeroen Demeyer was not maintained since he left sage development. Together with the PARI/GP team in Bordeaux I took over the maintainance and we now have a pari-jupyter 1.4.0 that is compatible with python 3.9 and PARI 2.13. See

Re: [sage-devel] permission denied on git.trac

All my keys were ssh-rsa. It appears that some server thinks it is not secure enough. Maybe it is the case for our git.trac. At least, I generated a ed25519 key and it now works. Vincent Le 25/11/2021 à 19:05, Vincent Delecroix a écrit : Le 25/11/2021 à 12:18, Dima Pasechnik a écrit

Re: [sage-devel] permission denied on git.trac

Le 25/11/2021 à 12:18, Dima Pasechnik a écrit : On Thu, Nov 25, 2021 at 11:08 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: Hello, Trying to fetch or push to the git server I today get $ git fetch g...@trac.sagemath.org: Permission denied (publickey). fatal: Could not rea

[sage-devel] permission denied on git.trac

Hello, Trying to fetch or push to the git server I today get $ git fetch g...@trac.sagemath.org: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. I did not change any ssh key on my

Re: [sage-devel] making primecount (and its dependency primesieve) standard

+1 for using standard and efficient libraries instead of slow and buggy sage implementations :-) Thanks Vincent Le 23/11/2021 à 11:26, Dima Pasechnik a écrit : primecount is a popular C++ library of efficient procedures to compute prime_pi(x), i.e. π(x), number of prime numbers <=x, and

[sage-devel] singular crash

Dear all, I just set up a patchbot but two tests related to singular fail. The singular it uses was compiled from source. See the patchbot report at https://patchbot.sagemath.org/ticket/32859/ sage -t --long --warn-long 42.4 --random-seed=24651699140802493978117085271929917492

  1   2   3   4   5   6   7   8   9   10   >