On Mon, Jan 16, 2023 at 3:34 PM Dima Pasechnik wrote:
>
> I don't know. Perhaps Matthias changed something in the setup of the repos.
I doubt it's some sort of metadata poisoning that happened in the
latest iteration so that the search broke - it's probably general
flaki
-all-2023-01-14-004/issues?q=34782+
>
> -Aram
>
> On Mon, 16 Jan 2023 at 11:56, Dima Pasechnik wrote:
>>
>> On Mon, Jan 16, 2023 at 9:07 AM John Cremona wrote:
>> >
>> >
>> >
>> > On Mon, 16 Jan 2023 at 07:45, Matthias Koeppe
>>
On Saturday, December 17, 2022 at 7:42:34 PM UTC Dima Pasechnik wrote:
On Sat, Dec 17, 2022 at 2:49 PM Dima Pasechnik wrote:
>
> See https://trac.sagemath.org/ticket/34854 to fix this.
has been merged, should be in Sage 9.8.
Ready for review
>
> On Sat, Dec 17, 2022 at
author:JohnCremona
This gives me 9 open and 248 closed issues.
>
> John
>
> On Mon, 16 Jan 2023 at 11:59, Dima Pasechnik wrote:
>>
>> On Mon, Jan 16, 2023 at 9:07 AM John Cremona wrote:
>> >
>> >
>> >
>> > On Mon, 16 Jan 2023 at 07:45, Matth
On Mon, Jan 16, 2023 at 11:55 AM Dima Pasechnik wrote:
>
> On Mon, Jan 16, 2023 at 9:07 AM John Cremona wrote:
> >
> >
> >
> > On Mon, 16 Jan 2023 at 07:45, Matthias Koeppe
> > wrote:
> >>
> >> Next iteration:
> >> https://34.105
On Mon, Jan 16, 2023 at 9:07 AM John Cremona wrote:
>
>
>
> On Mon, 16 Jan 2023 at 07:45, Matthias Koeppe
> wrote:
>>
>> Next iteration:
>> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues
>> with much improved labels
>
>
> The label component: elliptic curves is empty, which does
On Mon, Jan 16, 2023 at 9:07 AM John Cremona wrote:
>
>
>
> On Mon, 16 Jan 2023 at 07:45, Matthias Koeppe
> wrote:
>>
>> Next iteration:
>> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues
>> with much improved labels
>
>
> The label component: elliptic curves is empty, which does
On Fri, 13 Jan 2023, 19:26 Matthias Koeppe,
wrote:
> We have just completed the first full trial migration of all ~35000 open
> and closed Trac tickets (as of late December) into a temporary GitHub
> Enterprise Server instance.
>
> Please take a look at:
> https://34.105.185.241/sagemath/sage-all
No, no bug (yet).
The problem is that you are not careful constructing the correct subgroups
to use.
E.g. if you want groups[2] to be a subgroup of groups[5]=<(1,2,3,4)>
you must take groups[2]=<(1,3)(2,4)>, not groups[2]=<(1,2)(3,4)>.
You can start with the maximal subgroups of S_5, and intersec
First of all, you're really on your own as far as Python2 is concerned.
We've moved on, there is no reason to use it on anything but
unupgradable old software.
It's not clear from your message whether you saw any difference from
python3 vs "sage --python".
Could you clarify?
Could you please also
On Wed, Jan 11, 2023 at 2:02 PM 'Julian Nowakowski' via sage-devel
wrote:
>
> Hi Dima,
>
> thank you for your suggestion.
>
> We still think that this issue is Sage-related.
> We have already tried to figure out, whether the slowdown is simply an issue
> of fpylll.
> If that was the case, then th
A part of SageTeX is sensitive to LaTeX representations of Sage
objects - one of the macros requires that it's not split into several
paragraphs.
This was reported on https://github.com/sagemath/sagetex/issues/64
In this case it turned out that tikz represention of polyhedra are to
blame - easily
This does not appear to be Sage-related.
You can run the code above in Python shell.
(e.g. you can start Sage's python as "sage --python")
HTH
Dima
On Tue, Jan 10, 2023 at 3:48 PM 'Julian Nowakowski' via sage-devel
wrote:
>
> Hi Martin,
>
> the slowdown also appears in other contexts. In particu
On Thu, Jan 5, 2023 at 5:38 PM Minho Song wrote:
>
> I'm installing sagemath using Ubuntu in Windows 10.
> After doing 'make build', I got errors building Sage.
> Please check the attached log files.
You are having a lot of "/mnt/c/..." entries in your PATH, which might
break things - e.g. it mak
On Fri, Dec 23, 2022 at 10:10 PM Matthias Koeppe
wrote:
>
> Our GitHub contact has advised us that it will be helpful to set up a
> temporary GitHub Enterprise Server for the purpose of our migration from Trac
> to GitHub. There is a 45-day free trial -
> https://enterprise.github.com/trial, wh
On Sat, Dec 17, 2022 at 2:49 PM Dima Pasechnik wrote:
>
> See https://trac.sagemath.org/ticket/34854 to fix this.
Ready for review
>
> On Sat, Dec 17, 2022 at 2:01 PM Dima Pasechnik wrote:
> >
> >
> >
> > On Mon, 12 Dec 2022, 23:58 'Travis Scrimshaw&#x
See https://trac.sagemath.org/ticket/34854 to fix this.
On Sat, Dec 17, 2022 at 2:01 PM Dima Pasechnik wrote:
>
>
>
> On Mon, 12 Dec 2022, 23:58 'Travis Scrimshaw' via sage-devel,
> wrote:
>>
>> The entire computation in PermutationGroup.molien_series()
On Mon, 12 Dec 2022, 23:58 'Travis Scrimshaw' via sage-devel, <
sage-devel@googlegroups.com> wrote:
> The entire computation in PermutationGroup.molien_series() all appears to
> be done in libgap. Sage's wrapper around characters is never really invoked
> at all AFAICS. Here is a curious data poin
On Fri, Dec 16, 2022 at 4:58 PM David Lowry-Duda wrote:
>
> On Thu, Dec 15, 2022 at 12:19:28PM +, Dima Pasechnik wrote:
> >On Thu, Dec 15, 2022 at 12:05 PM John Cremona wrote:
> >>
> >> A propos, which Sage developers will be in Luminy for the COUNT
> >&
On Thu, Dec 15, 2022 at 12:05 PM John Cremona wrote:
>
> On Thu, 15 Dec 2022 at 12:00, Dima Pasechnik wrote:
> >
> > On Thu, Dec 15, 2022 at 9:30 AM Vincent Delecroix
> > <20100.delecr...@gmail.com> wrote:
> > >
> > > On
On Thu, Dec 15, 2022 at 9:30 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> 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:
>
g
Sage without it?
In particular, I do not see any relations between
> #31572 (which tests two pari versions) and #34850 (which tests a
> single pari version). Could you either read carefully the description
> of #34850 or explain the link between #31572 and #34850 if any?
>
ld be related to #31572, which notes a dramatic speed regression based
> on pari being compiled with pthread.
> David
>
> On Wed, Dec 14, 2022 at 3:30 PM Dima Pasechnik wrote:
>>
>> I vaguely recall something about the way gp is built, without linking
>> libpari dyna
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 done,
in regard of using, or not, threads, and dynamic linking.
On Wed,
On Fri, Dec 9, 2022 at 2:55 AM 'Travis Scrimshaw' via sage-devel
wrote:
>
> By running the code in molien_series() directly in Sage, I can do the
> computation, but not by calling the method. So it seems to be something
> within Sage with the interface with libgap.
not really, it's just the cha
Something I stumbled upon on #34804 - vanilla Python's doctest
framework plays much nicer with decorators than Sage's one.
Help from anyone knowledgeable about these matters in Sage woud be
much appreciated.
Dima
--
You received this message because you are subscribed to the Google Groups
"sag
but you can use Set() (a Sage's class for sets), which is much more sane here:
sage: f in Set(P)
True
sage: g in Set(P)
True
On Fri, Dec 2, 2022 at 5:13 PM Dima Pasechnik wrote:
>
> in fact, you can see that
>
> sP=set(P)
> sP.add(g)
> len([t for t in sP])==len
in fact, you can see that
sP=set(P)
sP.add(g)
len([t for t in sP])==len(P)+1
gets you True...
On Fri, Dec 2, 2022 at 5:08 PM Dima Pasechnik wrote:
>
> On Fri, Dec 2, 2022 at 5:05 PM 'Martin R' via sage-devel
> wrote:
> >
> > OK, thank you, but is this re
On Fri, Dec 2, 2022 at 5:05 PM 'Martin R' via sage-devel
wrote:
>
> OK, thank you, but is this really intentional? I would have thought that x
> in P and x in set(P) should give the same result.
I guess that hashing is done using a .parent()...
>
> On Friday, 2 December 2022 at 16:57:50 UTC+1
On Fri, Dec 2, 2022 at 2:44 PM 'Martin R' via sage-devel
wrote:
>
> a hashing problem, maybe?
to me, is't a problem of different "types" (.parent(), to be precise.
See my reply on the ticket)
>
> On Friday, 2 December 2022 at 15:43:33 UTC+1 Martin R wrote:
>>
>> I need help with https://trac.sag
On Sun, Nov 27, 2022 at 8:10 AM being nobody00 wrote:
>
> > What OS?
> $ uname -a
> Linux PC1 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021
> x86_64 x86_64 x86_64 GNU/Linux
>
this is a guest OS of WSL, as far as I know, and very old one (4+
y.o., and unsupported since early
On Fri, Nov 25, 2022 at 12:48 PM being nobody00 wrote:
>
> > If you start ./sage -sh
>
> (sage-sh):b4.0$ pip --version
> pip 22.0.2 from /home/hph/.sage/local/lib/python3.10/site-packages/pip
> (python 3.10)
this is wrong pip! (there should be no local/ in your ~/.sage/ at all)
pip should be i
It could be that at this point for some reason Sage's wheel package wasn't
built yet.
Can you run
make wheel && make jupyter_jsmol
On Friday, November 25, 2022 at 11:14:44 AM UTC Dima Pasechnik wrote:
> On Fri, Nov 25, 2022 at 5:10 AM being nobody00
> wrot
On Fri, Nov 25, 2022 at 5:10 AM being nobody00 wrote:
>
> Dear SageMath,
>
> SageMath 9.8 beta 4 failed to build on this system:
>
> $ uname -a
> Linux 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021
> x86_64 x86_64 x86_64 GNU/Linux
> $ which python3
> /usr/bin/python3
> $ pyth
On Fri, Nov 25, 2022 at 9:49 AM being nobody00 wrote:
>
> Hi,
>
> > please post the latest logs/pkgs/jmol-*.log here.
> Please find attached 'jmol-14.29.52.log.7z'
Sorry, I meant all logs/pkgs/*jmol-*.log
- it's not jmol's bug, most likely, but the wheel building of the
corresponding python pac
On Fri, Nov 25, 2022 at 5:10 AM being nobody00 wrote:
>
> Dear SageMath,
>
> SageMath 9.8 beta 4 failed to build on this system:
>
> $ uname -a
> Linux 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021
> x86_64 x86_64 x86_64 GNU/Linux
> $ which python3
> /usr/bin/python3
> $ pyth
These pexpect-based GAP classed in Sage are a mess.
The only reason they are still there is that few things are actually
implemented in Cython, avoiding GAP,
and they are somehow faster (while many things are much slower)...
(one needs to update https://trac.sagemath.org/ticket/26902 here)
Anyhow,
et/31563
to your source tree - but, why?
Why can't you just build/use Sage 9.7 instead?
You might also try
./configure --disable-giac
make build
> Am Sa., 5. Nov. 2022 um 11:47 Uhr schrieb Dima Pasechnik <
> dimp...@gmail.com>:
>
>> Are you trying to build an old version
I've opened https://trac.sagemath.org/ticket/34724 to deal with this
On Sat, Nov 5, 2022 at 11:08 AM Dima Pasechnik wrote:
>
> Well, applying a naive exact linear algebra routine to inexact data,
> and that's what Sage is doing here, is prone to errors.
> sage: A=m.augmen
Well, applying a naive exact linear algebra routine to inexact data,
and that's what Sage is doing here, is prone to errors.
sage: A=m.augment(identity_matrix(RR,2))
sage: A
[-6.12323399573677e-17 -1.72508242466029 1.00
0.000]
[0.579682446302195 6.1232339957367
Are you trying to build an old version of Sage? In the current 9.7 we
have giac 1.9, not 1.6,
see https://trac.sagemath.org/ticket/31563
On Sat, Nov 5, 2022 at 10:39 AM Jan V. wrote:
>
> Hello again,
>
> I reinstalled sage after I had some issues with my computer, and even after
> several tries
avoid building gcc. You don't need it. Read advice on packages printed by
./configure at the end of run, and follow it.
I'd give you more details over a teams or google meet call.
(Bruno is one of our 3rd year students I advise this year).
Dima
On Fri, 4 Nov 2022, 18:29 'bruno edwards' via sage-
On Wed, 26 Oct 2022, 11:47 Eloi Torrents, wrote:
> I generated a new key pair, I added it to trac but I keep getting the same
> error message when pushing:
>
apologies, it should be u/gh-Eloitor...,
not u/gh_Eloitor...
> remote: FATAL: W refs/heads/u/gh_Eloitor/QuaternionOrder_fix sage
> gh-E
On Sat, 22 Oct 2022, 06:24 Eloi Torrents, wrote:
> yes... I tried to add it and I got the message "Key is already in use".
>
please see
https://docs.github.com/en/authentication/troubleshooting-ssh/error-key-already-in-use
looks like you need to generate a new key pair and upload a new key.
On Fri, Oct 21, 2022 at 8:30 PM Eloi Torrents wrote:
>
> I followed your instructions but I got this message when pushing:
I assumed you have ssh key uploaded to your github account.
Do you have any keys here:
https://github.com/settings/keys
?
>
> $ git push trac HEAD
> Enumerating objects: 13
On Fri, Oct 21, 2022 at 11:29 AM Eloi Torrents wrote:
>
> When constructing a quaternion order over a number field I get this error:
>
> from sage.algebras.quatalg.quaternion_algebra import QuaternionOrder
> F. = NumberField(x**2-x-1)
> A. = QuaternionAlgebra(F, -1, -1)
>
> QuaternionOrder(A, [1,
Could it be it's the same default for univariate and multivariate cases? In
the latter case, it's easier to blow off memory usage to store zeros...
On Wed, 19 Oct 2022, 21:06 David Ayotte, wrote:
> I agree with this suggestion. Whenever I am looking for the coefficients
> of a polynomial, I also
Sunday, October 9, 2022 at 1:15:57 PM UTC+1 Dima Pasechnik wrote:
> On Sun, Oct 9, 2022 at 9:23 AM David Joyner wrote:
> >
> > On Sun, Oct 9, 2022 at 3:25 AM Florian Königstein
> wrote:
> > >
> > > I have equations for the analysis of an electric circuit. They c
On Sun, Oct 9, 2022 at 9:23 AM David Joyner wrote:
>
> On Sun, Oct 9, 2022 at 3:25 AM Florian Königstein
> wrote:
> >
> > I have equations for the analysis of an electric circuit. They contain at
> > several places the term w*I (I is the imaginary unit). I get a solution for
> > the currents I
why do you
./configure --with-system-sqlite3=no --with-system-python3=no
?
python3.9 on your system is good enough, why do you try to build
Python 3.10 on a very old OS?
Also, why do you instist on building sqlite3?
On Fri, Oct 7, 2022 at 6:19 AM Andreas wrote:
>
> Hello,
> I've been trying
On Fri, Oct 7, 2022 at 12:19 AM Kwankyu Lee wrote:
>
>
>
> 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/ti
On Thu, 6 Oct 2022, 20:21 Jonathan Thornburg, wrote:
> On Thu, Oct 6, 2022 at 8:45 AM John H Palmieri
> wrote:
> > There is nothing in our department's bylaws to provide for a delay of
> > voting, but we have a chair and we have an executive committee, and the
> > hope is that they care not only
I hope we don't introduce something akin to the US Senate filibuster :-)
On Thu, Oct 6, 2022 at 5:26 PM William Stein wrote:
>
> On Thu, Oct 6, 2022 at 8:45 AM John H Palmieri wrote:
> > Hi William,
> > There is nothing in our department's bylaws to provide for a delay of
> > voting, but we hav
I don't think it is feasible to design a system to delay voting. If we
don't limit the delaying powers of participants, effectively every vote can
be put off indefinitely.
If we limit such powers, e.g. allowing just one delaying request per year
per person, then another vote can be called on a sli
I must have been what Dutch would call "direct", English "undiplomatic" and
French "violent", I guess.
On Wed, 5 Oct 2022, 20:31 Matthias Koeppe, wrote:
> Sorry, bad link, I meant to paste this link:
> https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/5jotDDgyBwAJ
>
> On Wednesday, October
20:15 UK (i.e. 21:15 Paris) is quite inconvenient slot for me, as that's
close to bedtime for my son.
On Mon, 3 Oct 2022, 20:45 Matthias Koeppe, wrote:
> I was running late today from another meeting -- glad I still caught you
> when you were online!
>
> Matthias
>
> On Monday, October 3, 2022 a
On Sat, Oct 1, 2022 at 9:30 AM seb@gmail.com wrote:
>
> Hi,
>
> at least since 9.8.beta1 I get:
>
> (base) gitpod@sagemath-sagetracmirror-bkjzz4skuj7:/workspace/sagetrac-mirror$
> sage
> bash: sage: command not found
> (base) gitpod@sagemath-sagetracmirror-bkjzz4skuj7:/workspace/sagetrac-mirr
On Fri, Sep 30, 2022 at 8:59 AM Marc Mezzarobba wrote:
>
> John H Palmieri wrote:
> > You would think that this would be a solved problem: others in the
> > open source community must have be in the practice of backing up their
> > GitHub info.
>
> The following tools seem fairly complete:
>
> - h
On Thu, Sep 29, 2022 at 4:38 PM Sette Diop wrote:
>
> Hi:
>
> I am building sage-9.7 on macOS 12.6 (Monterey) and run through this error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
do you use pari from Ho
that's cause Homebrew pari is too new, and it's used in the build.
This version is not yet supported by
Sage, and we don't have a fix in place that rejects it.
Try
make -j8 pari
make -j8 build
On Thu, Sep 29, 2022 at 4:17 PM 'Mary Claire Simone' via sage-devel
wrote:
>
> Thank you Dima, this
On Thu, Sep 29, 2022 at 6:17 AM David Coudert wrote:
>
> The command t.pdf() is not working for me for the following reason:
>
> Warning: `tkz-graph.sty` is not part of this computer's TeX installation.
> This package is required to render graphs in LaTeX.
> Visit 'https://www.ctan.org/pkg/tk
You can't use gsl from Homebrew, as you already have openblas (a dependency
of gsl) installed from Sage.
Install openblas in Homebrew (if not yet installed)
and remove Sage's built openblas:
make openblas-clean
then re-run ./configure
It should pick up gsl from Homebrew then.
HTH
Dima
On
Thanks for the report!
On Wed, Sep 28, 2022 at 6:49 AM Александр Каренин (alexKar)
wrote:
> Having trouble with the matrix multiplication which I first explained in
> https://ask.sagemath.org/question/64194/determinants-over-cyclotomic-fields-are-broken/
> If I define two matrices (L and U) over
On Tue, 27 Sep 2022, 21:12 Tobias Diez, wrote:
> Just to make sure we are talking about the same thing. Imagine a currently
> open ticket with a linked branch. How is this going to be migrated? My
> assumption has been that this will create a PR from
> sagemath/sagetrac-mirror/branch into sagemat
On Tue, Sep 27, 2022 at 8:16 PM Ben Salisbury wrote:
>
> Hi all,
>
> I'm having trouble with the view method. For example,
>
> sage: G = graphs.PetersenGraph()
> sage: view(G)
works for me with Sage 9.8.beta0
>
> produced the following error.
>
> An error occurred.
> This is pdfTeX, Version 3.1
On Tue, 27 Sep 2022, 18:38 Andrey Novoseltsev, wrote:
> On Tuesday, 27 September 2022 at 11:11:00 UTC-6 dim...@gmail.com wrote:
>
>> Basically, we should deprecate and remove tmp_dir() and tmp_filename()
>> from Sage.
>> Does Sagecell use them? It should not, Python3 has perfectly good
>> replace
Basically, we should deprecate and remove tmp_dir() and tmp_filename()
from Sage.
Does Sagecell use them? It should not, Python3 has perfectly good
replacements...
On Tue, Sep 27, 2022 at 6:06 PM Matthias Koeppe
wrote:
>
> Previous discussion -- in the ticket that made these changes to SAGE_TMP -
On Tue, 27 Sep 2022, 15:45 John H Palmieri, wrote:
> One of the issues is that code in Sage is using this temporary directory
> in the background; the user is not doing it and has no control over it.
> Regardless of the context manager approach, apparently some browsers refuse
> to open local fil
On Tue, 27 Sep 2022, 14:08 Tobias Diez, wrote:
> Yes, the target repo of these PRs will be the (new) sagemath/sage, but the
> source will be sagemath/sagetrac-mirror, right?
Hmm, I might have missed something - what is the need to have 2 repos here,
if 1 is sufficient?
Any fork of sagemath/sa
On Tue, Sep 27, 2022 at 11:29 AM Tobias Diez wrote:
>
> One more question: The current plan is to use the sagetrac-mirror repo as the
> base for creating PRs but also to archived it. However, if I'm not mistaken,
> that makes all branches in sagetrac-mirror readonly and thus one cannot
> contin
On Tue, Sep 27, 2022 at 3:58 AM Andrey Novoseltsev wrote:
>
> Hello!
>
> I've run into this while testing upgrades to Ubuntu 22.04 from 20.04, but it
> seems that it comes from how temporary files are handled in Sage 9.7:
>
> TMP_DIR_FILENAME_BASE=tempfile.TemporaryDirectory()
>
> this temporary
On Mon, Sep 26, 2022 at 10:26 AM Tobias Diez wrote:
>
>
>
>> 2. Convert all tickets to Issues in a new repo. (This preserves the ticket
>> numbers as Issue numbers.)
>
>
> Would it make sense to convert tickets with branches directly to
> pull-requests?
only open tickets.
Closed tickets are ser
Do we require everyone willing to vote to do so on sage-devel, or it
could be done elsewhere (not every contributor to Sage or its
dependencies/packages is there) ?
On Wed, Sep 21, 2022 at 6:23 PM David Roe wrote:
>
> Dear Sage developers,
> As announced in a parallel thread, we are voting to mov
+1 to GitHub
On Wed, Sep 21, 2022 at 6:23 PM David Roe wrote:
>
> Dear Sage developers,
> Following extensive discussion, both recently (prompted by issues upgrading
> the trac server) and over the last decade, we are calling a vote on switching
> Sage development from Trac to Github. We've cr
t, I guess, about 1300 contributors (quite a few by the same
person, but different emails etc),
see attachment
>
> I'm sure we could get a full list of author names from git.
> David
>
> On Tue, Sep 20, 2022 at 12:35 PM Dima Pasechnik wrote:
>>
>> On Tue, Sep 20, 2
nce grad
>>>> students and postdocs may have used academic email accounts that are no
>>>> longer active).
>>>>
>>>> I'm sure we could get a full list of author names from git.
>>>> David
>>>>
>>>> On Tue, Sep
On Tue, Sep 20, 2022 at 5:30 PM William Stein wrote:
>
> On Tue, Sep 20, 2022 at 4:09 AM Dima Pasechnik wrote:
> >
> > On Tue, Sep 20, 2022 at 11:51 AM kcrisman wrote:
> > >
> > >
> > >>> "Subscribed to sage-devel" might not be a go
On Tue, Sep 20, 2022 at 11:51 AM kcrisman wrote:
>
>
>>> "Subscribed to sage-devel" might not be a good criteria. For example,
>>> Harald Schilly has been the webmaster of Sage since 2007 and likely
>>> cares about this switch since it can impact him, but I don't think he
>>> reads sage-devel.
>>>
What's the state of building Sage under conda (with its packages installed)?
On Mon, Sep 19, 2022 at 8:26 PM Matthias Koeppe
wrote:
>
> Previous release tours had code examples (and graphics) for new features,
> which made them a nice read - see for example
> https://trac.sagemath.org/wiki/Rele
On Mon, 19 Sep 2022, 15:35 William Stein, wrote:
> Here is a 3-minute section of a PyCon 2022 keynote by the steering
> council discussing migration of CPython to GitHub:
>
> https://youtu.be/m2R5shF1pLc?t=535
>
> In particular, they talk about how much effort went into the
> migration, and just
On Mon, Sep 19, 2022 at 1:46 AM John H Palmieri wrote:
>
>
>
> On Sunday, September 18, 2022 at 2:55:34 PM UTC-7 dim...@gmail.com wrote:
>>
>>
>>
>> On Sun, 18 Sep 2022, 22:44 John H Palmieri, wrote:
>>>
>>> William, this is exactly why I search in the sage-trac Google group rather
>>> than on t
On Sun, 18 Sep 2022, 22:44 John H Palmieri, wrote:
> William, this is exactly why I search in the sage-trac Google group rather
> than on the trac website.
it's looks easy to set up posting of issues/comments to a google group.
The sage-trac group is also good for browsing to see recent activi
On Sun, 18 Sep 2022, 01:44 Kwankyu Lee, wrote:
> 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 manag
On Sat, 17 Sep 2022, 13:22 kcrisman, wrote:
>
> I think the 1st vote should be on moving from trac to Git**b; besides it
>> appears that, technically, move to Github is much easier than to Gitlab
>> (while there are migration tools available for trac->github, I could not
>> find anything for trac
On Fri, 16 Sep 2022, 19:54 John H Palmieri, wrote:
> A few comments:
>
> - We have a strong history in Sage of conducting votes, and I absolutely
> think we need to do that for this issue. We also have a history (with
> perhaps a small number of exceptions) of having majority rule, and I think
>
On Fri, 16 Sep 2022, 17:20 kcrisman, wrote:
>
> I'd rather focus the vote primarily on the move away from trac, not
>> specifying whether it's GitHub or GitLab.
>>
>>
>>
>> > Given that, we face Arrow's theorem in picking a voting system
>> (especially if we also want to allow people to abstain).
IMHO ./bootsrtap should not be invoked by any of our 'make' targets.
same for ./configure (I can't recall any real reason, apart from
convenience, that we do this)
On Fri, 16 Sep 2022, 16:43 Martin Pépin, wrote:
> Hi all,
>
> I had a weird issue with sage recently which boiled down to `make
On Fri, Sep 16, 2022 at 9:19 AM David Roe wrote:
>
> I've started working on a list of pros and cons to be included in the email
> proposing a vote. Even though I favor the switch, I've tried to accurately
> and neutrally describe the arguments in each direction. I welcome help and
> addition
Hi Seb,
On Fri, Sep 16, 2022 at 7:57 AM seb@gmail.com wrote:
>
> Matthias Koeppe schrieb am Donnerstag, 15. September 2022 um 21:22:25 UTC+2:
>>
>> On Thursday, September 15, 2022 at 2:09:23 AM UTC-7 Samuel Lelievre wrote:
>>>
>>> c. Several people refuse to open a GitHub account
>>
>>
>> I d
On Thu, 15 Sep 2022, 15:53 William Stein, wrote:
> On Thu, Sep 15, 2022 at 2:17 AM Samuel Lelièvre
> wrote:
> > Increasingly, services such as GitHub and Google require
> > users to have a mobile phone number, to share it with them,
> > and to be able to receive text messages on them in order
>
On Thu, Sep 15, 2022 at 3:54 PM William Stein wrote:
>
> Reminder -- that 30 minute Sage zoom meeting thing that Matthias
> organized is happening in a few minutes from right now at
>
> https://ucdavis.zoom.us/j/92371662861?pwd=TDZKR0lKb2xzTGhiM0l3cnFmaGRadz09
>
link doesnt work for me
> (8:15 p
On Thu, Sep 15, 2022 at 12:38 PM Marc Mezzarobba wrote:
>
> Samuel Lelièvre wrote:
> > a. The company operating GitHub can block access to GitHub,
> > block account creation, or terminate accounts for individuals,
> > companies or countries without prior notice on discriminatory
> > grounds, see l
On Thu, Sep 15, 2022 at 2:47 PM Eric Gourgoulhon wrote:
>
> Le jeudi 15 septembre 2022 à 15:32:22 UTC+2, dim...@gmail.com a écrit :
>>
>>
>>
>> On Thu, 15 Sep 2022, 14:21 Eric Gourgoulhon, wrote:
>>>
>>> I would like to ask about a point that does not seem to have been discussed
>>> before (apol
On Thu, 15 Sep 2022, 14:21 Eric Gourgoulhon, wrote:
> I would like to ask about a point that does not seem to have been
> discussed before (apologies if it was):
> If the migration to Gihub takes place, would there remain somewhere a
> read-only copy of Trac? more precisely, of all the Trac ticke
On Thu, Sep 15, 2022 at 10:17 AM Samuel Lelièvre
wrote:
>
> One more thought.
>
> Increasingly, services such as GitHub and Google require
> users to have a mobile phone number, to share it with them,
> and to be able to receive text messages on them in order
> to be able to log in or access certa
On Thu, Sep 15, 2022 at 10:09 AM Samuel Lelièvre
wrote:
>
> On Friday, 09 Sep 2022, 09:54 UTC, Dima Pasechnik wrote:
> >
> > I am resurrecting this thread, as in addition of trac continuing to eat up
> > funds
> > (at a rate of over US$ 10 per day at the momen
On Thu, 15 Sep 2022, 07:40 seb@gmail.com, wrote:
> What is the proposed workflow to merge the develop branch after a new
> release into PR (or other) branches of your fork (i.e re-basing)? Obviously
> this is possible by pushing on sync in the web interface or typing gh
> repo sync USERNAME/s
Have you forgotten to
source .homebrew-build-env
?
On Wed, 14 Sep 2022, 15:10 Dima Pasechnik, wrote:
> this
>
> https://bitbucket.org/malb/m4rie/issues/23/trying-to-compile-on-apple-m1
>
> and trac tickets mentioned there might be related.
>
>
> On Wed, 14 Sep 2
this
https://bitbucket.org/malb/m4rie/issues/23/trying-to-compile-on-apple-m1
and trac tickets mentioned there might be related.
On Wed, 14 Sep 2022, 14:51 Ben Salisbury, wrote:
> I'm trying to build from source on a MacBook Air with the new m2 chip, and
> the build fails at m4ri. I've tried
On Wed, 14 Sep 2022, 03:15 Nils Bruin, wrote:
> On Tuesday, 13 September 2022 at 14:04:24 UTC-7 dim...@gmail.com wrote:
>
>>
>>
>> On Tue, 13 Sep 2022, 21:56 Nils Bruin, wrote:
>>
>>> I'd actually be interested in knowing what the substitute for "git trac
>>> checkout ..." is. Because with trac,
601 - 700 of 5310 matches
Mail list logo
