t's been there for quite a while but certainly the surroundings have
> been modified quite a bit since then.
>
> If you want to create a PR to change that link, I am happy to give it
> positive review.
>
> julian
>
> On Wednesday, April 10, 2024 at 11:56:23 AM UTC+3 John Cremon
In the first line of
https://doc.sagemath.org/html/en/installation/source.html#sec-installation-from-sources
the words "source code" are a link to the wikipedia page for "source code",
which is not very helpful. I was expecting it to be a link to page shoing
where to download a tarball. I
Should there not be separate projects for documenting (1) building and
installing Sage; (2) using Sage (perhaps with some subject-specific
tutorials, some of which exist but might be worth updating) and (3)
documenting individual Sage functions and methods.
These require different expertise, for
I'm going to forward this to sage-nt as there may be people who read that
but not this.
Meanwhile I would recommend getting something to work correctly before
worrying too much about what is most efficient.
John
On Wed, 6 Mar 2024, 12:52 Giacomo Pope, wrote:
> *=== Summary*
>
> Arithmetic of
Mathematically, the degree of a nonzero polynomial is the negative of its
valuation at infinity, i.e. the valuation for which 1/x is a uniformiser.
On Fri, 1 Mar 2024, 19:29 Travis Scrimshaw, wrote:
> Some quick data points:
>
> - The general graded modules (and hence algebras) code raises an
On Fri, 1 Mar 2024 at 11:03, Dima Pasechnik wrote:
>
>
> On Fri, Mar 1, 2024 at 10:24 AM John Cremona
> wrote:
>
>>
>>
>> On Fri, 1 Mar 2024 at 10:04, Dima Pasechnik wrote:
>>
>>>
>>>
>>> On 1 March 2024 09:07:26 GMT, 'Martin R'
On Fri, 1 Mar 2024 at 10:04, Dima Pasechnik wrote:
>
>
> On 1 March 2024 09:07:26 GMT, 'Martin R' via sage-devel <
> sage-devel@googlegroups.com> wrote:
> >I'd be OK with raising an exception or with -oo, but it should be
> uniform,
> >and I think it should be the same for polynomials, Laurent
There may be case for leaving deg(0) undefined both for polynomials and
Laurent polynomials (and power series and Laurent series): it's at best a
shorthand (pace Nils' comment about dimensions) and needs to be handled
separately in code. So calling deg(0) could raise a ValueError or
Try not using the system's eclib. I don't think that any Linux
distribution has an up to date eclib (but I don't keep track of this).
Sage does now have a very up to date eclib, and building it will not take
long.
John Cremona
On Mon, 15 Jan 2024 at 21:59, Aurore Guillevic
wrote:
> D
:
>
>>
>>
>> On 19 December 2023 14:49:19 GMT, John Cremona
>> wrote:
>> >On Tue, 19 Dec 2023 at 14:20, Dima Pasechnik wrote:
>> >
>> >> On Tue, Dec 19, 2023 at 1:54 PM John Cremona
>> >> wrote:
>> >> >
>>
On Tue, 19 Dec 2023 at 14:20, Dima Pasechnik wrote:
> On Tue, Dec 19, 2023 at 1:54 PM John Cremona
> wrote:
> >
> > I am finding it impossible to get simple PRs to get past the automatic
> testing workflow system, which are repeatedly failing for reasons which
> have no
I am finding it impossible to get simple PRs to get past the automatic
testing workflow system, which are repeatedly failing for reasons which
have noting to do with any code I have changed.
Two current examples are
- https://github.com/sagemath/sage/pull/36786 ( a simple bugfix which I
On Thu, 16 Nov 2023 at 12:15, Michael Orlitzky wrote:
> On 2023-11-16 09:23:15, John Cremona wrote:
> >
> > If no-one has any reason to keep things as they are I will make a PR with
> > the relevant changes to build/pkgs/eclib.
>
> From a packaging standpoint, f
On Thu, 16 Nov 2023 at 09:44, Dima Pasechnik wrote:
>
>
> On 16 November 2023 09:23:15 GMT, John Cremona
> wrote:
> >Currently the eclib spkg has pari, ntl and flint as dependencies. The
> >first two are essential, but flint is currently hardly used and eve
Currently the eclib spkg has pari, ntl and flint as dependencies. The
first two are essential, but flint is currently hardly used and everything
works without it. (It is only used at all to compute the ref of a matrix
(with entries int or long int) mod p and if flint is not available it just
Please all cool it down.
John
On Wed, 15 Nov 2023 at 04:59, John H Palmieri
wrote:
> If I respond using "verb" as a verb, do you really think I'm seriously
> criticizing you about using "vendor" as a verb? You're telling me to get a
> life? Get a sense of humor.
>
> On Tuesday, November 14,
git grep foobar
>
> etc
>
> On Tue, Nov 14, 2023 at 2:33 PM John Cremona
> wrote:
> >
> > I have machines I have been building Sage on (and using for development)
> for 10 years or more, and they have several environment variables of the
> form SAGE* which I set i
I have machines I have been building Sage on (and using for development)
for 10 years or more, and they have several environment variables of the
form SAGE* which I set in my .bashrc script. I suspect that all or most of
these are redundant; some may even be harmful. Is there a list somewhere
of
On Thu, 9 Nov 2023 at 09:46, Dima Pasechnik wrote:
> On Thu, Nov 9, 2023 at 9:25 AM John Cremona
> wrote:
> >
> > OK, so compiling he one-line file produces the same set of error
> messages as in Sage's log.
> >
> > Adding -E and examining the result sh
chance?
>
> Can you try running
>
> g++ -c foo.cpp
>
> on the 1-line file foo.cpp,like this:
>
> /* cut here: foo.cpp */
> #include
> /* cut here */
>
>
> Dima
>
>
>
>
>
>
>
> On Wed, Nov 8, 2023 at 4:57 PM John Cremona
> wrote
On Wed, 8 Nov 2023 at 15:31, Dima Pasechnik wrote:
> On Wed, Nov 8, 2023 at 3:20 PM John Cremona
> wrote:
> >
> >
> >
> > On Wed, 8 Nov 2023 at 12:51, John Cremona
> wrote:
> >>
> >>
> >>
> >> On Wed, 8 Nov 2023, 11:46 Dim
On Wed, 8 Nov 2023 at 12:51, John Cremona wrote:
>
>
> On Wed, 8 Nov 2023, 11:46 Dima Pasechnik, wrote:
>
>> On Wed, Nov 8, 2023 at 11:37 AM John Cremona
>> wrote:
>> >
>> > PS OK, my bug was fixed in pari-2.15.4 which is what is in Sage 10.2rc0
&g
On Wed, 8 Nov 2023, 11:46 Dima Pasechnik, wrote:
> On Wed, Nov 8, 2023 at 11:37 AM John Cremona
> wrote:
> >
> > PS OK, my bug was fixed in pari-2.15.4 which is what is in Sage 10.2rc0
> so I am happy with that -- though I would still like to know how to use my
>
PS OK, my bug was fixed in pari-2.15.4 which is what is in Sage 10.2rc0 so
I am happy with that -- though I would still like to know how to use my
system-installed 2.16.1.
On Wed, 8 Nov 2023 at 11:28, John Cremona wrote:
> Two things:
>
> 1. After
>
> ./configure --enable-pari_el
Two things:
1. After
./configure --enable-pari_elldata --enable-pari_galpol
--enable-pari_jupyter --enable-pari_nftables --enable-pari_seadata
and make build I had an error installing pari_jupyter (which I had never
used before). See attched log.
2. I really need to build Sage to use my own
I assume that deprecation means that for a year or so people can still use
the backslash but will see a deprecation warning. This could last for quite
a long time, so existing code would not immediately break.
On Wed, 4 Oct 2023, 18:41 Thierry Dumont,
wrote:
> In "Computational Mathematics with
Deprecate
On Sun, 1 Oct 2023, 04:17 Nils Bruin, wrote:
> Deprecate please.
>
> --
> 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
On Thu, 31 Aug 2023 at 15:00, John Cremona wrote:
> Thanks for the report, you are correct and there is a bug in the code.
> When reducing the cusp 6/7 it first reduced 6 and 7 mod the level 7 to get
> 6 and 0, then calls an internal function _lift_pair() which assumes that
>
Thanks for the report, you are correct and there is a bug in the code.
When reducing the cusp 6/7 it first reduced 6 and 7 mod the level 7 to get
6 and 0, then calls an internal function _lift_pair() which assumes that
the new pair of integers is coprime.
I will raise an issue and (probably) fix
rac.sagemath.org/22349 is not
> there, http://trac.sagemath.org/ticket/22349 still works (well, with a
> little bump).
>
> On Wed, May 10, 2023 at 3:22 PM John Cremona
> wrote:
> >
> > In a jupyter notebook cell running Sage 9.8 I see the following:
> >
> > /tmp/ipy
In a jupyter notebook cell running Sage 9.8 I see the following:
/tmp/ipykernel_2055107/2497908513.py:2: DeprecationWarning: parameter
'sort' will be set to False by default in the future
See http://trac.sagemath.org/22349 for details.
P.vertices(), P.edges()
There is also M.echelon_basis() which does that. I don't know why we need
two, does anyone?
John
On Mon, 17 Apr 2023 at 17:13, Ralf Hemmecke wrote:
> Hello,
>
> is there any particular reason why the term 12/5*q is not subtracted
> away by the first basis element?
>
> Ralf
>
>
Even in the light of the detailed explanations already given, I do find it
hard to see how these outputs are so different:
sage: RealField(200)(RR(11/10))
1.100088817841970012523233890533447265625000
sage: RealField(200)(RR(1.1))
Can this specific example be found in the online documentation?
On Thu, 23 Mar 2023 at 11:02, Dima Pasechnik wrote:
> On Thu, Mar 23, 2023 at 10:03 AM Kwankyu Lee wrote:
> >
> > I asked "in sagemath, how can i compute the genus of a curve", and this
> is its reply:
> >
> > which is perfect.
Surely it is just a question of precedence of variables. In Sage you are
dividing by a quadratic in y and getting a remainder which is linear in y.
In pari you are dividing by a cubic in x and getting a remainder which is
of degree <3 in x.
If you swap x and y in both polynomials, sage's
We could also have a branch called release which is separate from develop.
Normal developers would make PRs to be merged into develop like now, but
the release manager could make PRs from develop to release. That's the way
we do things in the LMFDB (with different names for the branches). So
assume that after every merge
of a PR which passes all tests, they have to wait for all the other PRs to
be retested.
> On Thu, 16 Feb 2023, 15:54 John Cremona, wrote:
>
>>
>>
>> On Thu, 16 Feb 2023 at 15:53, John Cremona
>> wrote:
>>
>>> Depreca
On Thu, 16 Feb 2023 at 15:53, John Cremona wrote:
> Deprecation warnings have a parameter which is interpreted as a trac
> ticket number, and output a second line after the warning text, of the form
>
> See https://trac.sagemath.org/12345 for details.
>
> Is the solution
Deprecation warnings have a parameter which is interpreted as a trac ticket
number, and output a second line after the warning text, of the form
See https://trac.sagemath.org/12345 for details.
Is the solution simply to replace the template for that output with a
suitable GitHub issue number (or
and I might get distracted before finishing...
>
> On Thu, Feb 16, 2023 at 9:04 AM John Cremona
> wrote:
> >
> > I was about to open a new issue for work I have done which will
> implement a greatly improved method for something already implemented in
> Sage (twice
I was about to open a new issue for work I have done which will implement a
greatly improved method for something already implemented in Sage (twice,
both by me...). When you click on the button to create a new issue, there
are three categories listed: Bug Report, Failure Building from Source,
Strong yes from me.
#34987 concerns a 3-line doctest where only the first has a #long time tag
thought the other lines depend on the first having been run, so causes a
failure when tested without --long. The fix adds two # long time tags
#34964 trims some whitespace and changes "" to r""" in a
get that suggestion!
> David
>
> On Tue, Feb 7, 2023 at 5:39 PM John Cremona
> wrote:
>
>> Re David's #1: Could we only allow PRs to be made by members? (Or is
>> that against the spirit of open source?) Then, a new contributor would
>> first ask to become a me
Re David's #1: Could we only allow PRs to be made by members? (Or is
that against the spirit of open source?) Then, a new contributor would
first ask to become a member, and then would be able to make a PR.
John
On Tue, 7 Feb 2023 at 16:29, Eric Gourgoulhon
wrote:
> Thanks for your reply.
n Mon, Feb 6, 2023 at 12:13 PM John Cremona
> wrote:
> >
> > I am unable to pull from upstream, I get a timeout:
> >
> > $ git pull upstream develop
> > fatal: unable to connect to github.com:
> > github.com[0: 140.82.121.3]: errno=Connection timed out
> &
I am unable to pull from upstream, I get a timeout:
$ git pull upstream develop
fatal: unable to connect to github.com:
github.com[0: 140.82.121.3]: errno=Connection timed out
I can ping the same IP address OK. I think I have my remote set OK:
$ git remote -v
origin
Nathan Cohen stopped contributing to Sage definitively around the time
William started SageMathCloud (now cocalc) as he thought that William was
profiting from his work.
I couldn't find any posts from him since 2013.
John
On Sat, 4 Feb 2023, 16:29 Matthias Koeppe, wrote:
> On Saturday,
On Fri, 3 Feb 2023 at 11:15, Kwankyu Lee wrote:
> Again. Sorry.
Never mind, it is not that important.
> --
> 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
A few people who post to this list have their email configured so that
quoted text is in a different colour, instead of having quoted text
prefixed by > or similar.
I am partly colourblind and this confuses me as I literally cannot see that
some text is in a different colour (for some
On Thu, 2 Feb 2023, 09:55 Matthias Koeppe, wrote:
> I think in general the SageMath organization will welcome public
> visibility of membership, but in the end it is merely a matter of
> individual contributors' personal preference whether to display SageMath
> org membership to the public.
>
In case anyone else was caught out as I was following links in this thread
-- I am a member (and apparently have been for some time) but my membership
is for some reason private, so I don't see myself in the list unless I am
logged in to github.
Is there any reason I (or anyone) would need to be
On Mon, 30 Jan 2023, 16:02 Dima Pasechnik, wrote:
> Could someone with a "legacy" trac account quickly check whether they
> can modify tickets. (me and mkoeppe are still able, but that's the
> current setup)
>
I could not login, the username cremona and my password were deemed invalid.
John
On Tue, 24 Jan 2023 at 13:17, 'Martin R' via sage-devel <
sage-devel@googlegroups.com> wrote:
> Because sage 9.8.beta7 (more specifically, #34547) breaks emacs'
> sage-shell-mode, I would like to know whether there are any other emacs
> users out there. Are there alternatives to sage-shell-mode?
I think there are many trac names whose real names are known (I saw
several) but either do not have github accounts or are no longer active in
Sage development. 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
Thanks Matthias for the detailed replies. I, and I'm sure all other sage
developers, are extremely grateful for the work you and the others have
done for this migration.
John
On Tue, 17 Jan 2023, 19:23 Matthias Koeppe,
wrote:
> On Tuesday, January 17, 2023 at 2:10:24 AM UTC-8
s new version.
> > >
> https://34.105.185.241/sagemath/sage-all-2023-01-12-003/issues?q=34782+
> > > vs
> > >
> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues?q=34782+
> > >
> > > -Aram
> > >
> > > On Mon, 16 Jan 2
On Mon, 16 Jan 2023 at 12:35, Dima Pasechnik wrote:
> On Mon, Jan 16, 2023 at 12:22 PM John Cremona
> wrote:
> >
> > Thanks, Dima. I do now see 64 issues when I first view all issues and
> then filter on that, so I don't know what was happening earlier.
> >
&g
6 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, Matthias Koeppe
> wrote:
> >>
> >> Next iteration:
> https://34.105.185.241/sagema
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 not seem right.
On trac there are 64 open elliptic curve tickets. One
On Thu, 15 Dec 2022 at 12:19, Dima Pasechnik wrote:
>
> 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.de
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 Thu, 15 Dec 2022 at 01:42, Dima Pasechnik wrote:
> > >
> > >
> > >
> > > On Wed, 14 Dec 2022, 21:06 Vincent Delecroix,
My suggestion was only for univariate polynomials. I am certainly not
proposing this for multivariate polynomials. I still cannot think of
a use case for the current default for univariate polynomials. (And,
more than one person has complained to me about this "very annoying
and
Does anyone ever use pol.coefficients() and not
pol.coefficients(sparse=False)? I mean, why is the default option
sparse=True? There must be very few occasions for the default,and I
get tired of typing sparse=False I do know that pol.list() is the
same as pol.coefficients(sparse=False).
I
If you really have a list and not just a generator, might it be worth
a first pass to see if there's a 0 in the list before forming the
product? With the tree structure for efficiently computing the
product, you might be doing a lot of multiplication before hitting the
zero item. I think that
On Thu, 22 Sept 2022, 19:21 Antonio Rojas, wrote:
> Specifically, help is needed from someone who understands genus2reduction
> code in order to solve the (almost) last remaining issue.
>
I'll take a look tomorrow.
John
> El jueves, 15 de septiembre de 2022 a las 20:58:19 UTC+2, vdelecroix
>
+1 for GitHub
On Wed, 21 Sept 2022, 20:56 Ricardo Buring,
wrote:
> +1 for GitHub
>
> On Wednesday, September 21, 2022 at 7:23:36 PM UTC+2 David Roe wrote:
>
>> Dear Sage developers,
>> Following extensive discussion, both recently
>>
GH issues can also be used as "metatickets" on trac, with a checklist of
things to do which can be checked off as they are dealt with by various
PRs. We often do this with the LMFDB whose code development is done on GH
via issues and PRs as described by others here. We have fewer developers
of
To me, as a contributor of code to Sage who has not contributed at all
to the backend support, it seems that there is a clear majority in
favour of moving to github. As an ordinary developer I would be very
happy with that.
It looks to me as if Frédéric's main issue with github is his final
Whenever a pexpect interface is created, there's an optional parameter to
say whether or not to make a log file. The default should always be not to
do so. So we should look to see which ones may have the opposite default.
It may be something left over from a debugging session which got committed
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 to LazyPowerSeriesRing. Do you mean this?
>
> Mathematically, Taylor
On Fri, 5 Aug 2022 at 10:06, Eric Gourgoulhon wrote:
>
> grayish > detoned > original.
I have no strong opinion on this choice!
John
>
> Eric.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop
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 two different possible themes and ask people on
sage-devel to vote.
John
On Thu, 4
I forwarded this to sage-nt in case there are people there with an opinion.
I'll give my answer there too.
Thanks for working on this,
John
On Wed, 27 Jul 2022, 10:49 Jing Guo, wrote:
> Hi,
>
> I am implementing the `logarithmic_embedding` function [0] (based on
> Krumm's code) for my GSoC
On Tue, 26 Jul 2022 at 08:13, Dima Pasechnik wrote:
>
> On Tue, Jul 26, 2022 at 8:24 AM Nils Bruin wrote:
> >
> > On Monday, 25 July 2022 at 12:53:08 UTC-7 Matthias Koeppe wrote:
> >>
> >> Have you tried the existing instructions that I pointed you to?
> >
> >
> > I have now. I'm stuck on
On Tue, 12 Jul 2022 at 19:41, Barinder Banwait wrote:
>
> Thanks John -- ticket raised here:
> https://trac.sagemath.org/ticket/34174#ticket
As a workaround, you can do two things (which will not be necessary
after I have finished with that ticket):
(1) replace E by E.integral_model(), or
Barinder, I'll look into this (tomorrow) -- it's my code. Please open
a ticket and CC me. It's happening in the code to reduce a model with
respect to scaling by units.
John
On Tue, 12 Jul 2022 at 16:19, Barinder Banwait wrote:
>
> Dear sage-devel,
>
> I am running into an issue with
On Tue, 12 Jul 2022 at 14:14, Josh Mundinger wrote:
>
> Alright, thank you.
>
> On Tuesday, July 12, 2022 at 2:08:42 AM UTC-4 dim...@gmail.com wrote:
>>
>>
>>
>> On Tue, 12 Jul 2022, 02:37 Josh Mundinger, wrote:
>>>
>>> When I run conjugacy_classes_representatives() on a sufficiently large
>>>
On Wed, 6 Jul 2022 at 10:28, John Cremona wrote:
>
> The problem is in lines 3373-3374 and 3382 of
> src/sage/schemes/elliptic_curves/heegner.py. The floating point
> approximation of the point has x-coordinate 0.500 -
> 1.32287565553229*I and the code tries to fi
:18, John Cremona wrote:
>
>
>
> On Tue, 5 Jul 2022, 23:21 'Justin C. Walker' via sage-devel,
> wrote:
>>
>>
>>
>> > On Jul 5, 2022, at 07:00 , Debanjana wrote:
>> >
>> > sage: E = EllipticCurve('11a1')
>> > sage: P = E
On Tue, 5 Jul 2022, 23:21 'Justin C. Walker' via sage-devel, <
sage-devel@googlegroups.com> wrote:
>
>
> > On Jul 5, 2022, at 07:00 , Debanjana wrote:
> >
> > sage: E = EllipticCurve('11a1')
> > sage: P = E.heegner_point(-7)
> > sage: t = P.point_exact()
> > sage: t.domain()
> > Spectrum of
Thanks -- sorry for not having searched on trac before posting.
John
On Fri, 24 Jun 2022 at 11:06, Samuel Lelievre wrote:
>
> Seems to have been addressed already for Sage 9.7.
>
> Indeed, this query
>
> https://trac.sagemath.org/query?order=id=1=~randrange
>
> returns in particular this
Running one of my scripts with 9.6 I notice several warnings like this:
/home/jec/sage/local/var/lib/sage/venv-python3.10.3/lib/python3.10/site-packages/sage/schemes/elliptic_curves/period_lattice.py:238:
DeprecationWarni
ng: non-integer arguments to randrange() have been deprecated since
Python
On Thu, 23 Jun 2022 at 05:24, Jing Guo wrote:
>
> Hi,
>
> I am contributing to Sage via GSoC this summer. As part of my work, I am
> implementing the (global) height on polynomials for number fields. After
> looking into relevant functions, such as degrees and coefficients, my mentors
> and I
, see e.g.
> https://gist.github.com/jlblancoc/99521194aba975286c80f93e47966dc5
>
> But it's better to upgrade to a more recent OS.
>
>
> >
> > > On 22/06/2022, at 22:56, John Cremona wrote:
> > >
> > > On a machine (Ubuntu 16.04.7 LTS) on which I have do
On a machine (Ubuntu 16.04.7 LTS) on which I have done a lot of Sage
development before, and successfully built sage from source, from
scratch, just a month ago (May 17 when 9.6 was released) with no
problems.
Now, I made a new clone of the source using
git clone
On Sat, 18 Jun 2022, 10:23 Dima Pasechnik, wrote:
> On Sat, Jun 18, 2022 at 9:40 AM John Cremona
> wrote:
> >
> >
> >
> > On Sat, 18 Jun 2022, 08:33 Dima Pasechnik, wrote:
> >>
> >> On Fri, Jun 17, 2022 at 11:41 AM John Cremona
> wrote:
>
On Sat, 18 Jun 2022, 08:33 Dima Pasechnik, wrote:
> On Fri, Jun 17, 2022 at 11:41 AM John Cremona
> wrote:
> >
> > Works for me --with MPIR and MPFR already installed, and also using
> Do you still use MPIR rather than GMP?
>
Yes but it's a pain in the neck having libg
Works for me --with MPIR and MPFR already installed, and also using
./configure --extensions=/hmod_mat (am I the only person using
hmod_mat?)
John
On Fri, 17 Jun 2022 at 10:02, 'Bill Hart' via sage-devel
wrote:
>
> Hi all,
>
> I have just tagged release candidate 2 of Flint version 2.9, see
On Mon, 25 Apr 2022 at 11:18, G. M.-S. wrote:
>
>
> On macOS: A wonderful app, thanks to Marc Culler.
>
> On Windows: Too complex for my far from savvy students. We are stuck with
> SageMath 9.3 for the time being.
>
> On Linux: It depends on the distribution, some have totally outdated
>
I volunteer.
John
On Thu, 14 Apr 2022, 16:10 William Stein, wrote:
> I also volunteer to be on the committee.
>
> On Thu, Apr 14, 2022 at 2:01 AM Samuel Lelievre
> wrote:
> >
> > Excellent idea. I volunteer to be on the committee. --Samuel
> >
> > --
> > You received this message because you
On Sat, 2 Apr 2022, 10:50 Andrew, wrote:
> There does seem to be a problem:
>
> sage: k = 61*2^88+1 ; k
> 18878585599102049192211644417
> sage: k.is_prime()
> True
> sage: k.factor()
> 18878585599102049192211644417
> sage: k == 61*2^88+1
> True
> sage: GF(k)
> Finite Field of size
On Thu, 24 Feb 2022 at 15:55, William Stein wrote:
>
> And then your paper appears at
> https://www.sagemath.org/library-publications.html
>
> On Thu, Feb 24, 2022 at 7:22 AM Dima Pasechnik wrote:
> >
> > Ideally, do a PR at https://github.com/sagemath/publications, our
> > GitHub repo
On Mon, 31 Jan 2022 at 20:07, Dima Pasechnik wrote:
>
>
>
> On Mon, 31 Jan 2022, 20:01 John Cremona, wrote:
>>
>>
>>
>> On Mon, 31 Jan 2022, 17:12 Sébastien Labbé, wrote:
>>>
>>> The "./configure" part of the installa
January 31, 2022 at 5:57:08 PM UTC+1 john.c...@gmail.com wrote:
>
>> [copied from sage-release]
>>
>> -- Forwarded message -
>> From: John Cremona
>> Date: Mon, 31 Jan 2022 at 13:47
>> Subject: Re: [sage-release] Re: Sage 9.5 released
>> To
[copied from sage-release]
-- Forwarded message -
From: John Cremona
Date: Mon, 31 Jan 2022 at 13:47
Subject: Re: [sage-release] Re: Sage 9.5 released
To:
I just successfully built 9.5 from a fresh tarball. After completing
the build I installed (as I usually do) an optional
On Tue, 18 Jan 2022 at 13:53, Samuel Lelievre wrote:
>
> 2022-01-18 10:54:34 UTC, John Cremona:
> >
> > I see that there are now over 2^32 trac tickets.
>
> The power of two that is near 32000 is really 2^15.
> : )
You are right of course. We had 16-bit arithmetic so
I see that there are now over 2^32 trac tickets. Wow. When I started
computing you couldn't have integers greater than 32767...
John
--
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
On Thu, 13 Jan 2022 at 14:05, 'Martin R' via sage-devel
wrote:
>
> 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 even know what to write into a ticket, so I'm asking here first.
On Wed, 29 Sept 2021 at 11:54, Dima Pasechnik wrote:
>
>
>
> On Wed, Sep 29, 2021 at 11:35 AM Ralf Hemmecke wrote:
>>
>> I seem to have a problem with building sage 9.4 via.
>>
>> MAKE='make -j12' make -j12
>>
>> It stops during the build of dochtml. Obviously because of too many open
>>
More generally uf all the coefficients can be coerced into AA then the
roots in QQbar not in AA come in pairs.
On Wed, 22 Sep 2021, 09:23 Dima Pasechnik, wrote:
>
>
> On Wed, Sep 22, 2021 at 9:19 AM Dima Pasechnik wrote:
>
>>
>>
>> On Wed, Sep 22, 2021 at 8:10 AM Tracy Hall wrote:
>>
>>> I
1 - 100 of 2352 matches
Mail list logo
