Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

On Tuesday, January 31, 2023 at 5:41:39 AM UTC+9 dim...@gmail.com wrote: Did you log out? Or you were basically kicked out? I didn't log out. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

On Tuesday, January 31, 2023 at 5:15:24 AM UTC+9 dim...@gmail.com wrote: that's cause I have to run "trac-admin" - and it breaks www access. I'll restore it after I am done. It's restored. Happily I cannot login to trac. -- You received this message because you are subscribed to the Google

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

For me, Trac is down, OSError: [Errno 13] Permission denied: '/srv/trac/sage_trac/gitolite-admin/conf/gitolite.conf' -- 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

Re: [sage-devel] Final call for GitHub user names

o). Therefore, I need replace Github > username `antoine-leudiere` with `Kryzar`. Could you help me with that (or > tell me if I can just do a new pull request or comment #357)? > > Apologies for the extra work. > Best, > Antoine Leudière > > Le vendredi 20 janvi

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

I am not sure if the "/ 1", "/ 2", "/ 3", "/ 4", "/ 5" postfixes are really helpful. Note that (1) As Matthias noticed, the priority labels are sorted in the correct order without those prefixes. (2) The label text and the label color already indicate the priority. (3) The numeral postfix is

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

There are duplicates of the same comments. See many comments below from https://34.105.185.241/sagemath/sage-all-2023-01-14-012/issues/34909#issuecomment-4477657 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

Re: [sage-devel] Final call for GitHub user names

Thanks, Emmanuel and Justin. This https://github.com/sagemath/trac-to-github/pull/145/files takes care of you. -- 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: Final call for GitHub user names

On Thursday, January 19, 2023 at 5:40:34 PM UTC+9 john.c...@gmail.com wrote: What should the policy be about those? If someone made a trac account without registering their full name, I am not sure that it is right for a 3rd party to later supply that real name. For a username with *known on

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

On Thursday, January 19, 2023 at 2:07:36 AM UTC+9 seb@gmail.com wrote: Since we can't be sure that all tickets have been converted correctly, I prefer to keep the link clickable for as long as possible! Furthermore, I think we should not erase the traces of the migration. As long as trac

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

In the issue description, I see "*Issue created by migration from https://trac.sagemath.org/ticket/ ...". * Would we remove this before migration? Perhaps we should because the link will be defunct eventually. -- You received this message because you

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

On Wednesday, January 18, 2023 at 4:08:15 AM UTC+9 Matthias Koeppe wrote: Tobias' initial proposal was to use the single letter "c: " as the prefix for components. I thought it would be too cryptic, so I went with the whole word "component: ". But I'd be happy to change it if "c: " (or some

[sage-devel] Attention wanted: component labels for issues in GitHub

Dear Sage developers, One of the first things we do when we create a new ticket is to choose the "Component" for which the ticket is. After we move to GitHub, we instead would choose a label of the form "component: ...". Like in Trac, the kind of labels will rarely change and you will be

[sage-devel] Attention wanted: GitHub migration

Happy new year! February this year, our migration ship to GitHub will skyrocket! There are lots of issues to discuss about github migration: https://github.com/sagemath/trac-to-github/issues Please come and share your thoughts! Thank you for attention. -- You received this message because

[sage-devel] Re: Status of the GitHub migration

> > The migration script accesses the Trac server via XMLRPC and does not need > privileged access. The first conversion of our 35000 tickets takes about 8 > hours. The migration script keeps a disk cache for the Trac data, so later > conversions are fast, enabling quick iterations when

[sage-devel] Re: Method 'latex.mathjax_avoid_list()' missing in the official docker image

On Tuesday, November 15, 2022 at 8:28:38 PM UTC+9 lucca@gmail.com wrote: > When using the official docker image, from within a Notebook the > methods > >- `latex.add_to_mathjax_avoid_list()` >- `latex.mathjax_avoid_list` > > are missing on the `latex` object. > These commands are

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

On Thursday, November 10, 2022 at 12:27:55 PM UTC+9 John H Palmieri wrote: > I think the use of Tachyon instead of Jmol must be particular to that > setup. When I build the docs with #34730, it looks the same as in the > develop branch, same as on sagemath.org. Right. It's the same here

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

Here is the link to the ticket #34730 https://trac.sagemath.org/ticket/34730 -- 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] Re: The documentation built for #34730 needs your attention for checking

By the way, please also review https://trac.sagemath.org/ticket/34710 to fix the cluttered TOCs. On Wednesday, November 9, 2022 at 2:22:43 PM UTC+9 Kwankyu Lee wrote: > Hi, > > Trac #34730 rebases sage_autodoc onto the upgraded Sphinx 5.3.0. It is > responsible for formatting

[sage-devel] The documentation built for #34730 needs your attention for checking

Hi, Trac #34730 rebases sage_autodoc onto the upgraded Sphinx 5.3.0. It is responsible for formatting Sage objects (functions, classes, etc.) to build documentation. Please check your favorite sections in our documentation

[sage-devel] Re: Help wanted: Merge all contributor information into contributors.xml

I made PR https://github.com/sagemath/website/pull/311 On Tuesday, October 11, 2022 at 8:42:07 AM UTC+9 Kwankyu Lee wrote: > On Tuesday, October 11, 2022 at 2:57:52 AM UTC+9 Matthias Koeppe wrote: > >> 3. Merge info from >> ​https://trac.sagemath.org/#AccountNamesMappedtoRe

[sage-devel] Re: Help wanted: Merge all contributor information into contributors.xml

On Tuesday, October 11, 2022 at 2:57:52 AM UTC+9 Matthias Koeppe wrote: > 3. Merge info from > ​https://trac.sagemath.org/#AccountNamesMappedtoRealNames > into > ​https://github.com/sagemath/website/blob/master/conf/contributors.xml >

[sage-devel] Please change https://doc.sagemath.org/index.html

to $SAGE_ROOT/local/share/doc/sage/index.html which looks tidy. Harald? -- 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.

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

On Friday, October 7, 2022 at 7:05:38 AM UTC+9 John H Palmieri wrote: > Dima, presumably you're not talking about me, although I proposed that "we > start a vote around October 1". > I guess he means: https://trac.sagemath.org/ticket/33725#comment:26 -- You received this message because

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

A suggestion for votes for sage development process: 1. Anyone can call for a vote for a relevant issue for sage development. 2. A vote must be preceded by a discussion on the issue on sage-devel, where the date and the duration of the vote is determined. A vote lasts at least a week. 3. If

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

On Monday, September 26, 2022 at 3:17:03 PM UTC+9 Kwankyu Lee wrote: > On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote: > >> Is there a vision for what Sage 10.0 means? > > Yes. See the headline of https://trac.sagemath.org/ticket/29705 -- You rec

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

On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote: > Is there a vision for what Sage 10.0 means? Sage X :) -- 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] DISCUSS: move Sage development to Github

> personally I still prefer Trac, but the bus factor argument and recruitment of new contributors are more important +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 it, send an

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

+1 for Github -- 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 discussion on the web visit

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

On Tuesday, September 20, 2022 at 8:09:33 PM UTC+9 dim...@gmail.com wrote: > > (by the way, by looking at this list I found that johanrosenkilde > works for GitHub now :-)) Surprise! Johan did much work in coding theory in academy and in sage. -- You received this message because you are

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

On Sunday, September 18, 2022 at 9:55:10 AM UTC+9 Matthias Koeppe wrote: > The conversion of the Trac tickets to GitHub Issues/PRs only works in one > shot. Incrementally syncing updates from Trac to existing issues is not > possible. > This means that we cannot continue to operate Trac after

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

On Friday, September 16, 2022 at 6:30:05 PM UTC+9 dim...@gmail.com wrote: I'd rather focus the vote primarily on the move away from trac, ... What would the move mean precisely? As there are two things to be done (1) The release manager declares to merge tickets only from Github, not from

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

On Friday, September 16, 2022 at 10:46:09 AM UTC+9 wst...@gmail.com wrote: > I just happened to stumble again on the original scrap of paper just > now where I made up the name > Sage back in 2004. > A good photo of it deserves to be permanently placed in the history section of the sagemath

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

According to https://trac.sagemath.org/ticket/30406#comment:15 trac continues to be running after migration to keep links to trac alive. Then do we really need to migrate (copy) tickets to github once and for all? I guess that the migrated tickets would be full of broken links internal or

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

On Saturday, September 10, 2022 at 6:26:29 PM UTC+9 dim...@gmail.com wrote: > Moving away from trac is basically a necessity now, as our devops are breaking down for some time, and it only gets worse. I wish that our trac survives the present crisis so that some people can have enough time to

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

> the futre of the trac software itself. > According to their developer mailing list https://groups.google.com/g/trac-dev the future of trac seems not so ominous to me. Perhaps publishing our fork of trac with customized plugins (?) to sagemath github repo may help increase the bus factor

[sage-devel] Re: BROADCAST MESSAGE

Trac is now in version 1.2. 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+unsubscr...@googlegroups.com. To view this discussion on the web

[sage-devel] Re: Trac no longer seems to push to sagetrac-mirror

> > Trac is currently running in *survival mode*. Is the database safe? Was it backed up? Or can it be cloned to other machine? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

Re: [sage-devel] trac.sagemath.org unreachable

On Thursday, September 1, 2022 at 1:00:23 AM UTC+9 j...@aims.ac.za wrote: > Or into gitlab, which we can host ourselves, > > https://github.com/tracboat/tracboat > > (I have no experience with tracboat) > Whether we upgrade trac or migrate to other platform, the process should be gradual so

Re: [sage-devel] trac.sagemath.org unreachable

On Wednesday, August 31, 2022 at 11:14:34 PM UTC+9 Kwankyu Lee wrote: > > We may need to plan migration while trac is still breathing... > https://www.redmine.org/ seems a successor of trac. -- You received this message because you are subscribed to the Google Groups "sag

Re: [sage-devel] trac.sagemath.org unreachable

On Wednesday, August 31, 2022 at 10:56:56 PM UTC+9 dim...@gmail.com wrote > Trac is a timesink. > Time spent on looking for fixes for it is time lost, that's for sure. The trac project seems not well maintained, according to its website. We may need to plan migration while trac is still

Re: [sage-devel] trac.sagemath.org unreachable

Trac is back. Anything lost? -- 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 discussion on the web visit

Re: [sage-devel] trac.sagemath.org unreachable

On Wednesday, August 31, 2022 at 6:41:19 PM UTC+9 Frédéric Chapoton wrote: > just be patient and spend your day doing something else, please It is a day to think about how precious our trac is. Just be careful when you touch its soft database. -- You received this message because you are

[sage-devel] Re: trac.sagemath.org unreachable

Perhaps need to update trac server ssh keys stored in github? On Wednesday, August 31, 2022 at 4:10:34 PM UTC+9 emanuel.c...@gmail.com wrote: > And an attempt to fetch a ticket also failed for related reasons : > > charpent@zen-book-flip:/usr/local/sage-9$ git trac checkout 34457 > Loading

Re: [sage-devel] trac.sagemath.org unreachable

This seems a different problem. The website is not accessible. On Wednesday, August 31, 2022 at 3:48:19 PM UTC+9 dim...@gmail.com wrote: > new ssh keys on the server, don't know how to tell this to "git trac" > > On Wed, 31 Aug 2022, 07:45 Emmanuel Charpentier, > wrote: > >> This morning (Aug

[sage-devel] Re: Useful methods for graphics objects

On Saturday, August 27, 2022 at 2:57:49 PM UTC+9 Nils Bruin wrote: > Do keep in mind that there is a basic command-driven interface behind > Geogebra as well. > Yes. Thank you. > which does not fully determine a circle in 3-space > I was careless. I should have listed two coordinates for

[sage-devel] Re: Useful methods for graphics objects

On Friday, August 26, 2022 at 8:04:02 AM UTC+9 Kwankyu Lee wrote: > On Friday, August 26, 2022 at 2:57:15 AM UTC+9 Nils Bruin wrote: > >> On Thursday, 25 August 2022 at 07:23:41 UTC-7 Kwankyu Lee wrote: >> >>> But an intuitive way (or an object-oriented way ?) i

[sage-devel] Re: Useful methods for graphics objects

On Friday, August 26, 2022 at 2:57:15 AM UTC+9 Nils Bruin wrote: > On Thursday, 25 August 2022 at 07:23:41 UTC-7 Kwankyu Lee wrote: > >> But an intuitive way (or an object-oriented way ?) is to get the >> necessary information from the line segment. Thus if L is the line s

[sage-devel] Re: Useful methods for graphics objects

Let me expand the example a bit. We are given two points. We draw a line segment connecting the two points. Then we want to draw a circle with a diameter the line segment. Certainly we need to compute the center and the radius of the circle. The standard way to do this with Sage is, as Travis

[sage-devel] Re: Useful methods for graphics objects

> > I have no idea what your argument is for the second part. Separations of > concerns means ... > I didn't use the phrase in its precise meaning (so I quoted it) I meant that you can write pythagorean formula, which is just what you need to compute the length of a line segment object,

[sage-devel] Re: Useful methods for graphics objects

On Thursday, August 25, 2022 at 4:06:14 AM UTC+9 Sébastien Labbé wrote: > Is there already a handy way to get the same result in Sage? >> > >> You can image other useful methods attached to a graphics object. >> > > For 2d lines, it returns a Graphics object which has a length. > Right. That

[sage-devel] Re: Useful methods for graphics objects

On Wednesday, August 24, 2022 at 9:18:06 AM UTC+9 Travis Scrimshaw wrote: > Éric, what do you think about adding such things to SageManifolds? Could > this be feasible? > It is embarrassing that an idea of attaching ".length()" method to a line segment graphics object leads to SageManifolds.

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

hybrid Hearty thanks for setting up the vote. -- 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 discussion on

[sage-devel] Re: Useful methods for graphics objects

On Monday, August 22, 2022 at 12:04:57 PM UTC+9 Travis Scrimshaw wrote: > I am not sure how much I support that because there is no metric. > It is of course euclidean, as you say > you can do > > sage: l = line3d([(1,2,3), (4,5,6)]) > sage: V = RR^3 > sage: (V(l.points[1]) -

[sage-devel] Useful methods for graphics objects

Hi, I wish that this would work: sage: l = line3d([(1,2,3),(2,2,3)]) sage: l.length() 1 Is there already a handy way to get the same result in Sage? You can image other useful methods attached to a graphics object. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Re: LazyPowerSeriesRing Replacement

On Tuesday, August 16, 2022 at 9:04:00 AM UTC+9 Travis Scrimshaw wrote: > the power series "is" a function (well, formally), we just usually think > of it as being equal to an "easier" function. > No. You know that a power series is an expression. It has variables, but not domain and

[sage-devel] Re: LazyPowerSeriesRing Replacement

If LazyTaylorSeriesRing could be a complete replacement of LazyPowerSeriesRing, then I think we should remove the old LazyPowerSeriesRing and rename LazyTaylorSeriesRing to LazyPowerSeriesRing. Do you mean this? Mathematically, Taylor series means power series derived from a function. So

[sage-devel] Re: Docstring Formatting Question: Bullet Points

As a fruit of this discussion, I made https://trac.sagemath.org/ticket/34348 Please review. -- 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] Re: Polling for sphinx background style

On Sunday, August 7, 2022 at 3:57:52 PM UTC+9 Travis Scrimshaw wrote: > I slightly protest that one day of voting at the end of the week is not a > lot of time for such a consequential vote. > I agree. Sorry about that. > That being said, I support grayish (but I also noticed there is so

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

Up to now, there were 4 positive, 1 implicitly positive, 1 implicitly negative votes. Thank you who voted. I think it is safe to conclude that the standard Furo package is accepted. The new standard package enables the new doc in Furo theme, which will be the default in the next sage

[sage-devel] Re: Polling for sphinx background style

Up to now, the voting counts (1) grayish: 5 (2) detoned: 1 (3) no opinion: 1 So I conclude that grayish is the winner. Let me close the voting. Once again, I thank you who participated. The new doc will be prepared according to the result. -- You received this message because you are

[sage-devel] Re: Polling for sphinx background style

On Friday, August 5, 2022 at 12:42:35 PM UTC+9 Matthias Koeppe wrote: > I didn't see a difference until I realized I need to switch to light mode If you look closely, there is a difference also in dark mode. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Polling for sphinx background style

On Friday, August 5, 2022 at 12:42:35 PM UTC+9 Matthias Koeppe wrote: > I didn't see a difference until I realized I need to switch to light mode It seems that a cookie is used to store the mode. It remembers the last mode I chose. -- You received this message because you are subscribed to

[sage-devel] Polling for sphinx background style

Hi, According to the recent decision, I applied sphinx style to our future doc in Furo theme. But it seem that a bit of tuning to the background style of code blocks would make doc look better. So I prepared another set of candidates for the background style. (1) original:

Re: [sage-devel] Re: Polling for pygments style for our future doc

Up to now, the voting counts (1) tango: 1 (2) default: 2 (3) sphinx: 10 and sphinx is the clear winner. So I close the voting. Thank you who participated. Accordingly, I will update #33833 "Make furo sage standard doc theme" to use the sphinx pygments style. As I noted elsewhere, we don't

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

On Thursday, August 4, 2022 at 8:46:28 PM UTC+9 David Joyner wrote: > This seems to allow dark mode when viewed in a browser on a cellphone, > which the old documentation did not seem to allow. Yes. The dark mode and the responsive design are some of the strong points of the Furo theme!

Re: [sage-devel] Polling for pygments style for our future doc

For your informed decision, visit (1) tango: https://2505ea042169d8a179d4b1f28a0c0baeabdd421a--sagemath-tobias.netlify.app/tutorial/tour_linalg.html (2) default: https://54ea9f6ae8fa30e96afa5304e0c11cf99f055158--sagemath-tobias.netlify.app/tutorial/tour_linalg.html (3) sphinx:

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

On Thursday, August 4, 2022 at 4:46:59 PM UTC+9 john.c...@gmail.com wrote: > Yes, please at least (1) turn off the italics for output, and (2) > don't put numbers in the input in a different colour. > > For such a change I think it is appropriate and would follow precedent > to put up at least

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

> Is it your personal decision to use tango for the (future) sage > documentation? Yes. > As a very personal opinion, I prefer better the default style. Note that tango is a style with lower contrast which is another argument > against it. Okay. As far as I know, currently these are

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

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 > fonts on my computer) > * numbers appear in bold blue and

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

Dear Sage developers, Furo is a clean customisable Sphinx documentation theme. It has been an optional pip package since Sage 9.7.beta2. Meanwhile we made efforts to make Furo a new theme for our documentation through https://trac.sagemath.org/ticket/33601

[sage-devel] Re: Docstring Formatting Question: Bullet Points

On Wednesday, July 13, 2022 at 12:13:28 PM UTC+9 John H Palmieri wrote: > I am "no" to having a Sage policy dictating blank lines, and I am also > "no" to having a policy dictating no blank lines. > We do have conventions in the developer manual by which sage developers are "dictated".

[sage-devel] Re: Docstring Formatting Question: Bullet Points

Bullet points are used in sage mainly in two places: (1) AUTHORS section in the doc string of a file (2) INPUTS section in the doc string of a class or function definition In (1), we usually look from the top to the bottom. This list may get longer and longer. So no blank line between points

Re: [sage-devel] closed tickets

On Saturday, July 2, 2022 at 12:33:38 PM UTC+9 Kwankyu Lee wrote: > ... I think this should be explained somewhere, perhaps in the notice > itself. > Added to https://trac.sagemath.org/ticket/33849 which needs review. -- You received this message because you are s

Re: [sage-devel] closed tickets

On Friday, July 1, 2022 at 1:02:32 AM UTC+9 dim...@gmail.com wrote: > Volker is against this. > (while such a branch exists, it's likely to get rewritten a lot before > it becomes a beta) When I first saw the notice of merge conflicts with Volker's branch and my positively-reviewed ticket,

[sage-devel] Working directory of github actions in Build & Test badge

Hi, If you look at the report of doctest failures there, you see for instance sage -t --warn-long 68.6 --random-seed=... sage/structure/dynamic_class.py Then if you copy this into your sage root directory, it doesn't work since "src/" prefix is missing in the path of the source file. It

[sage-devel] Emacs sage user wanted

Hi, The ticket https://trac.sagemath.org/ticket/33996 fixes the issue "ascii_art fail in jupyter notebook" raised in https://groups.google.com/g/sage-support/c/1a7cBp580CM We worry that the fix would have a bad side effect with other user interfaces, like emacs. So please test the

[sage-devel] Re: Help --> Sage Tutorial, Reference etc doesn't load in JupyterLab

On Wednesday, May 25, 2022 at 4:03:52 PM UTC+9 Eric Gourgoulhon wrote: > Thanks for the report. > I confirm the bug with Sage 9.7.beta0 on Ubuntu 20.04. > This is not new. At least, Sage 9.5 had the problem. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Sage 9.6 Release Tour moved to the Trac wiki - let's finalize it!

This page https://doc.sagemath.org/index.html seems still in old format, though local Sage 9.6 has an improved page accessible from "*here*" from here: https://doc.sagemath.org/html/en/index.html Harald? -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Virtual SageDays June 1–3: Call for contributed presentations and activities

Does everyone, except me, know why it is numbered 112.358? I have no clue... -- 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] A bug with modules with basis

On Friday, May 20, 2022 at 1:38:02 AM UTC+9 dim...@gmail.com wrote: > > which surprises me by its presence in the basic level. I looked through > the code, but it is not obvious where and what to fix. I suspect there is a > flaw in the design of modules with basis since this "order" thing is

[sage-devel] A bug with modules with basis

Hi, I encountered this bug sage: S. = PolynomialRing(QQ) sage: A = S**2 sage: A Ambient free module of rank 2 over the integral domain Multivariate Polynomial Ring in x, y, z, w over Rational Field sage: A.submodule([vector([x-y,z-w]), vector([y*z, x*w])]) ... TypeError: _vector_() got an

[sage-devel] Re: difference between PermutationGroup.has_element and PermutationGroup.__contains__

On Tuesday, May 10, 2022 at 6:35:10 AM UTC+9 axio...@yahoo.de wrote: > Exactly this is what I meant with "alias", and why I think that its > documentation is misleading, if not wrong. I just checked, has_element is > not used in the sage library at all. I thus propose to deprecate it. +1.

[sage-devel] Re: Building sage fails with the latest xcode command line tools update

On Saturday, April 30, 2022 at 4:57:47 AM UTC+9 Matthias Koeppe wrote: > We don't support the new versions of givaro/fflas_ffpack/linbox yet. > That's https://trac.sagemath.org/ticket/32959 Just did "brew uninstall givaro fflas-ffpack m2". Now sage building works well again. -- You

[sage-devel] Re: Building sage fails with the latest xcode command line tools update

On Saturday, April 30, 2022 at 4:57:47 AM UTC+9 Matthias Koeppe wrote: > We don't support the new versions of givaro/fflas_ffpack/linbox yet. > That's https://trac.sagemath.org/ticket/32959 Our configure script should have rejected these versions and built its own > copies of these

[sage-devel] Re: Building sage fails with the latest xcode command line tools update

The givaro at /usr/local was the one installed by homebrew, as a dependency of Macaulay2, which I installed recently. Somehow this does not work well with either sage or the xcode compilers. -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

[sage-devel] Building sage fails with the latest xcode command line tools update

Hi, On Mac, perhaps after automatic-installing the latest Xcode command line tools, building sage from scratch fails with many errors, first of which is [sagelib-9.6.rc2] [ 1/10] In file included from build/cythonized/sage/libs/singular/polynomial.cpp:775: [sagelib-9.6.rc2] In file included

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

There is this tool https://trac-hacks.org/wiki/MoinToTracScript I don't know if this still works. If so, then it would be a better strategy to move to trac first (using the script) and then consolidate. -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] Notebook for testing display

Dear sage developers, Let me advertise the nice notebook for testing display in Jupyter, https://nbviewer.org/github/egourgoulhon/SageMathTest/blob/master/Notebooks/test_display.ipynb prepared by Eric Gourgoulhon. This is also accessible through the ticket

[sage-devel] Re: Cannot compile sage on macosx 12.3

This occurred to me from time to time, I just do "sage -i openblas" and "make" again. -- 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] Re: Build fails at scipy on mac after latest os update

On Friday, March 18, 2022 at 12:26:59 PM UTC+9 Matthias Koeppe wrote: > See https://trac.sagemath.org/ticket/33522 It works like a charm. Thank you! -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Build fails at scipy on mac after latest os update

Sage build fails with the following log. I am not sure if this is caused by the latest os update (macOS Monterey 12.3). Is there a quick fix? ... [scipy-1.7.3] 85 warnings and 2 errors generated. [scipy-1.7.3] error: Command "g++ -Wno-unused-result -Wsign-compare -Wunreachable-code

[sage-devel] Latex displays will be aligned left in Jupyterlab

By the positive-reviewed ticket #32942, https://trac.sagemath.org/ticket/32942 latex displays will be aligned left in Jupyterlab, by default. We made this change to align with the behaviors of latex displays elsewhere, in particular, in classic Jupyter notebooks. But if you prefer the

Re: [sage-devel] trac is not accessible now

On Thursday, February 10, 2022 at 9:00:19 AM UTC+9 wst...@gmail.com wrote: > I get alerts from "uptimerobot" when trac goes up and down. It was > down for 27 minutes, but is up now. Trac goes down for a while about > once a week. See attached screenshot with data for 2022. Yes, it is back

[sage-devel] trac is not accessible now

at least from where I am, Korea. Ping reports that the server is running though. Kwankyu -- 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] Improved documentation webpages

Hi, In https://trac.sagemath.org/ticket/33309 I tried to fix many defects of current sage documentation webpages. As this would affect most Sage users, you are welcome to visit and make suggestions. Thank you in advance. Kwankyu -- You received this message because you are subscribed

[sage-devel] Re: Patchbot/CI improvements

On Monday, January 24, 2022 at 2:35:54 AM UTC+9 Matthias Koeppe wrote: > 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 think

Re: [sage-devel] Whats the plan for random doctests with floating point numbers?

On Thursday, December 30, 2021 at 8:40:35 AM UTC+9 dmo...@deductivepress.ca wrote: > In the long run, we want to fix the doctests so they always pass (as > described in the previous comment). > > However, in the short run, I think it is fine to add > > set_random_seed(0) # failed doctest - see

[sage-devel] Re: commits

On Friday, December 24, 2021 at 2:17:35 AM UTC+9 wst...@gmail.com wrote: > - There are 15 people with over 1000 commits, which is a healthy range > of distinct "top contributors" for an open source project. > Much thanks to the leaders! The graph clearly shows that there was a critical point

[sage-devel] Re: Master plan of sage modularization

Thank you for answers, and starting the ticket https://trac.sagemath.org/ticket/32899 to add a section on modularization in the sage developer manual. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Re: Master plan of sage modularization

Questions on "Features": We are introducing Features for packages in the sage library, like sage__combinat, sage__graphs, sage__plot, etc. How is this related with distributions? If a package is included in a distribution (other than sagemath-standard), a Feature for the package is introduced?

<    1   2   3   4   5   6   7   8   >