Hi,
I looks like Volker just put together a release, but hasn't pushed the
corresponding git repo to github. If you download that tarball you
link to, it contains a git repo with a 10.3.beta5 tag, lots of merged
code, etc.
William
On Sun, Jan 14, 2024 at 9:50 AM Gonzalo Tornaría wrote:
>
> A
GPT-4 quick summary: "The SageMath 10.0.beta9 release features
numerous updates, improvements, and bug fixes, including faster
computation of Frobenius powers and Kohel isogenies, refactored poset
examples for better code coverage, updated documentation and developer
manual, fixes for pycodestyle
Hi,
I added py and sh after all the fenced code blocks (triple backticks),
so now all the code and shell examples are syntax highlighted.
William
On Sat, Feb 11, 2023 at 4:58 PM Kwankyu Lee wrote:
>
> That is a nice summary of the GitHub migration efforts. Thank you.
>
> --
> You received this
Hi,
Thanks for the new release!
I built the cocalc-docker images [1] using sage-9.6 on both x86-64 and
amd64 (Apple Silicon) and the builds worked fine, and everything I
tested regarding integration with CoCalc also worked fine. I've
updated these images on Dockerhub.
CoCalc-docker is
For what it's worth, I use a free app from the MacOS app store called
Amphetamine:
https://apps.apple.com/us/app/amphetamine/id937984704?mt=12
This makes it easy to make the laptop stay on indefinitely, even if
the lid is closed. It works very robustly.
-- William
On Tue, Feb 22, 2022 at 1:32
Trying to build on an M1 ARM Mac with MacOS 12.x finally gets past the
very first package (GMP), due to upgrading to 6.2.1. It fails with
gfortran, with an error about this version of macOS being "unreleased"
(which is not true, of course -- it is released):
[gfortran-10.3.0] checking if mkdir
I think the develop branch is regularly changing with new commits each
day (hopefully) as Volker merges positively reviewed tickets. You can
browse pages and pages of commits that came after 9.5.beta6 to the
develop branch here:
https://github.com/sagemath/sage/commits/develop
It looks like he
On Wed, Nov 3, 2021 at 9:30 AM Matthias Köppe
wrote:
> On Tuesday, November 2, 2021 at 10:13:14 PM UTC-7 William Stein wrote:
>
>> On Tue, Nov 2, 2021 at 9:00 PM Matthias Köppe
>> wrote:
>>
>>> It's really just the command "tox -e
>>&g
don't know,
though "grep -i tachyon tox.ini" doesn't output anything, so I'm guessing
it doesn't.
William
>
> On Tuesday, November 2, 2021 at 8:37:54 PM UTC-7 William Stein wrote:
>
>> What did you do exactly? For example did you install tachyon
>> systemwide
tly
> newer than ubuntu-focal (20.04)
>
> sage -t --random-seed=0
> src/sage/algebras/quatalg/quaternion_algebra_cython.pyx
>[10 tests, 0.17 s]
>
> --
>
> All tests passed!
>
>
>
>
> On T
platforms, e.g.,
recent Rasberry Pi?
On Tue, Nov 2, 2021 at 10:55 AM William Stein wrote:
> Here's how "make test" ended:
>
> sage -t --random-seed=225297532770316936918573996029610176361
> src/sage/groups/class_function.py # Timed out
> sage -t --random-seed=22529753277031
stuck
at 0 percent for a long time and manually killed it.
So it looks like nothing is giving wrong answers, but a couple of things
are randomly hanging.
-- William
On Tue, Nov 2, 2021 at 10:31 AM William Stein wrote:
>
>
> On Tue, Nov 2, 2021 at 10:21 AM Matthias Köppe
> wrote:
>
On Tue, Nov 2, 2021 at 10:21 AM Matthias Köppe
wrote:
> On Tuesday, November 2, 2021 at 9:13:25 AM UTC-7 William Stein wrote:
>
>> This is a quick update about building the 9.5.beta5 version of Sage on an
>> M1 Mac under Docker aarch64 Linux.
>>
>>
> A quick
trix/matrix_integer_dense.pyx", line 1, in init
sage.matrix.matrix_integer_dense
(build/cythonized/sage/matrix/matrix_integer_dense.cpp:57704)
ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in
static TLS block
On Mon, Nov 1, 2021 at 5:33 PM William Stein wrote
On Mon, Nov 1, 2021 at 4:35 PM Dima Pasechnik wrote:
>
>
> On Mon, Nov 1, 2021 at 11:28 PM William Stein wrote:
>
>> Great idea. Thanks Dima!
>>
>> On Mon, Nov 1, 2021 at 3:37 PM Dima Pasechnik wrote:
>>
>>>
>>>
>>> On Mon,
Great idea. Thanks Dima!
On Mon, Nov 1, 2021 at 3:37 PM Dima Pasechnik wrote:
>
>
> On Mon, Nov 1, 2021 at 10:18 PM William Stein wrote:
>
>> I tried to build sage-9.5.beta5 on a very clean Linux Ubuntu:20.04 image
>> with standard dev packages (in Docker) but on an
I tried to build sage-9.5.beta5 on a very clean Linux Ubuntu:20.04 image
with standard dev packages (in Docker) but on an ARM aarch64 architecture
instead of Intel. It fails with Tachyon simply saying "Error: Sorry, your
platform isn't supported by Tachyon and/or Sage. Exiting...". I don't
know
Hi,
The official non-beta OpenSSL 3.0.0 release just happened. Finally!
On Wed, Sep 15, 2021 at 3:20 PM 'Justin C. Walker' via sage-release
wrote:
>
>
>
> > On Aug 31, 2021, at 15:38 , Volker Braun wrote:
> >
> > As always, you can get the latest beta version from the "develop" git
> >
On Mon, Oct 29, 2018 at 5:46 AM Erik Bray wrote:
>
> On Mon, Oct 29, 2018 at 1:25 PM Eric Gourgoulhon
> wrote:
> >
> > Le lundi 29 octobre 2018 13:18:11 UTC+1, Eric Gourgoulhon a écrit :
> >>
> >> I've noticed something new in this release, certainly introduced by
> >> 6d6c459c6b Trac #26174:
it this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>
--
-- William Stein
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this
On Fri, Mar 17, 2017 at 2:19 PM, William Stein <wst...@gmail.com> wrote:
> I pulled sage-7.6.rc1, typed 'time MAKE="make -j1" make ', and the
> build got stuck on ECL. This is how top looked, with nearly 3 hours
Hitting control+c, then typing just plain "make&quo
There is really no good way to deal with this besides proper OS packages or
rebuild sage from source when you do nontrivial system upgrades.
On Sat, Nov 26, 2016 at 11:27 AM Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:
> libvpx has stung before. When we upgraded linbox I made sure
OK, something will happen by next Monday...
On Wed, Nov 2, 2016 at 2:17 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2016-11-02 21:12, William Stein wrote:
>>
>> Jereon - is this script the thing you want from
>> disk.math.washington.edu?
>
>
Jereon - is this script the thing you want from
disk.math.washington.edu? Is that the only copy? If so, next time
I'm on campus I can turn that machine on and get the script...
On Wed, Nov 2, 2016 at 9:34 AM, Samuel Lelièvre
wrote:
> The changelog is produced after
On Fri, Jul 1, 2016 at 9:52 AM, Volker Braun <vbraun.n...@gmail.com> wrote:
> On Friday, July 1, 2016 at 6:36:49 PM UTC+2, William Stein wrote:
>>
>> The build still failed due to libpynac issues
>> "/projects/sage/dev/sage-7.3.beta6/local/lib/li
On Thu, Jun 30, 2016 at 11:53 PM, William Stein <wst...@gmail.com> wrote:
> Hi,
>
> Since the build failed with "> [pynac-0.6.7] /usr/bin/ld: cannot find
> -lao", I installed libao-dev, which is an Ubuntu package:
>
> libao-dev - Cross Platform Audio Out
der libao-dev something I have to
install before Sage, given that I have also installed giac.I'm
sure this will cause great confusion to other people who like to
install lots of math software on the same system in the future though.
William
>
> On Fri, Jul 1, 2016 at 8:39 AM William Stei
Ubuntu 15.10 and I said 16.04 before.
William
On Thu, Jun 30, 2016 at 11:38 PM, William Stein <wst...@gmail.com> wrote:
> Hi,
>
> On sagemathcloud (Ubuntu 16.04+lots) I've built all the betas up to
> 7.3.beta4 fine. 7.3.beta5 (via upgrade) won't build, nor will
> 7.3.beta6. The
Builds for me.
(On SMC you can type sage-develop in a terminal to use this version
immediately.)
On Sat, May 21, 2016 at 1:30 PM, Volker Braun wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source
Either my build is completely hosed, or "sage -bdist" is completely broken:
salvus@compute7-us:/projects/sage/sage-develop$ time ./sage -bdist tmp
sage-run received unknown option: -bdist
usage: sage [options]
Try 'sage -h' for more information.
salvus@compute7-us:/projects/sage/sage-develop$
Hi,
I built this but "anything??" results in a traceback. This looks like
a serious bug, which doctesting might not catch. Is it just me (quite
possible, since I built 7.2.beta5 first)? Sorry for the noise if this
is just me.
~/tmp$ sage-develop
In case you want to quickly try something out, this release is now
sage-develop on SageMathCloud (if you use the terminal).
William
On Fri, Apr 29, 2016 at 3:22 AM, Dima Pasechnik wrote:
>
>
> On Friday, April 29, 2016 at 10:41:51 AM UTC+1, Dima Pasechnik wrote:
>>
>> docs
Hi,
If you type "sage-develop" in a terminal on sagemathcloud, it'll run
this 7.2.beta5.
(Note tested: To make it work with worksheets you would do "cd ~;
mkdir -p bin; cd bin; ln -s /usr/local/bin/sage-develop sage" and
restart the sage worksheet server.)
-- William
On Thu, Apr 21, 2016 at
On Monday, September 28, 2015, Volker Braun wrote:
> Hmm but /usr/lib/x86_64-linux-gnu/libpari-gmp-tls.so.2.7.2 brings just a
> slightly different version of Pari's concat. It may very well be that it
> doesn't trigger libkpathsea crashing but thats just by chance; the
On Mon, Sep 28, 2015 at 11:00 AM, William Stein <wst...@gmail.com> wrote:
> In Sage-6.7 this library (which is *pure python*) works well:
>
>https://github.com/datasift
>
> In Sage-6.9.beta6 (for me) this library crashes with the following
> weird traceback. Any ideas
On Mon, Sep 28, 2015 at 11:28 AM, Volker Braun wrote:
> Symbol collision. Unless TeX's libkpathsea really intends to use concat()
> from Pari...
That makes sense. Basically you're noticing this part of the traceback:
...
In Sage-6.7 this library (which is *pure python*) works well:
https://github.com/datasift
In Sage-6.9.beta6 (for me) this library crashes with the following
weird traceback. Any ideas?
(sage-sh) [m 4a5f054258734eeda85ca18c706e8bcd@compute4-us:tmp$ which
[Kpython
Python 2.7.9
Hi,
Sage-6.7 is now the default on SageMathCloud.
William
On Thu, May 21, 2015 at 10:03 PM, Justin C. Walker jus...@mac.com wrote:
On May 21, 2015, at 19:03 , kcrisman wrote:
Justin, could you perhaps contribute a binary for the 10.6.8 platform?
We
certainly still get people on older
On Wed, May 20, 2015 at 7:53 AM, Eric Gourgoulhon
egourgoul...@gmail.com wrote:
Thank you very much Thierry !
Do you know when these binaries will be on the official Sage mirrors?
Harald is working on it right now...
Regards,
Eric.
--
You received this message because you are
On Wed, May 13, 2015 at 4:57 PM, Volker Braun vbraun.n...@gmail.com wrote:
As usual, get the develop git branch. We now measure the fastest mirror
and download packages from there, this should result in a net speedup. Let
us know if you encounter any problems.
Alternatively, the
Hi,
I built sage-6.7.beta4 fine, then did git pull, then build
sage-6.7.beta5 fine, which passed all tests. But I can't do ./sage
-bdist ...:
sage -t --long --warn-long 64.2
local/lib/python2.7/site-packages/sagenb-0.11.4-py2.7.egg/sagenb/misc/sphinxify.py
[14 tests, 1.23 s]
On Thursday, April 23, 2015, Harald Schilly harald.schi...@gmail.com
wrote:
So, here it is:
http://dx.doi.org/10.5281/zenodo.17093
LaTeX:
@misc{w_a_stein_et_al_2015_17093,
author = {W. A. Stein et al.}
title= {SageMath 6.6},
month= apr,
year =
On Wed, Apr 8, 2015 at 7:26 AM, leif not.rea...@online.de wrote:
On 04/08/2015 12:48 PM, Daniel Krenn wrote:
Am 2015-04-08 um 12:28 schrieb Vincent Delecroix:
At least, does 'sage -i openssl' before 'make' work?
Seems to be possible (tried; but still compiling).
It used to work and hence
On Sat, Mar 21, 2015 at 7:05 AM, Volker Braun vbraun.n...@gmail.com wrote:
As usual, get the develop branch or the source tarball from
http://www.sagemath.org/download-latest.html
7f1fbd5 Updated Sage version to 6.6.rc0
Hi,
On SageMathCloud, make ptestlong worked perfectly and all tests
On Sat, Mar 21, 2015 at 8:39 AM, Volker Braun vbraun.n...@gmail.com wrote:
One more design issue is the lack of a top margin ...
Yes, put in this when fixing the color:
margin-top: 6px;
On Saturday, March 21, 2015 at 3:27:25 PM UTC+1, William Stein wrote:
On Sat, Mar 21, 2015 at 7:05
On Sat, Mar 14, 2015 at 8:11 AM, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
This is the hard part:
well-defined subset of the optional packages and tests
Once you fill this in, the testing can trivially be done on the buildbot.
These are the optional packages I care about (the ones
On Monday, March 16, 2015, Volker Braun vbraun.n...@gmail.com wrote:
Maybe its not quite as trivial since optional packages won't build on
every supported platform, so what is the winning criterion? Perhaps with
docker we could require that an optional package comes with a Dockerfile
that
On Fri, Mar 13, 2015 at 11:42 AM, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2015-03-13 18:37, William Stein wrote:
M = self._new_uninitialized_matrix(self._ncols,B._ncols)
It seems that your machine is extremely slow: Sage is still constructing the
matrix to contain
On Fri, Mar 13, 2015 at 10:16 AM, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2015-03-13 18:10, William Stein wrote:
On 64-bit Ubuntu 14.10, make ptestlong yields one doctest failure.
Since it's something that I think absolutely anybody who ran the
doctest on any system would see, I guess
On Sat, Mar 7, 2015 at 9:25 AM, leif not.rea...@online.de wrote:
On 03/07/2015 04:56 PM, William Stein wrote:
(1) the group for that directory is the user (which is standard on
Linux, btw, but not other os's) and
Well, obviously checking which users belong to the file's group would be
too
On Sat, Mar 7, 2015 at 7:43 AM, Volker Braun vbraun.n...@gmail.com wrote:
Should be fixed in 6.6.beta3. However if you built 6.6.beta2 then setuptools
created the directory with wrong permissions, and installing 6.6.beta3 on
top will not change the permissions. Just delete .sage/.python-eggs
On Tue, Jan 6, 2015 at 2:50 PM, William Stein wst...@gmail.com wrote:
On Tue, Jan 6, 2015 at 2:38 PM, Volker Braun vbraun.n...@gmail.com wrote:
Do you have /scratch/wstein/sage-6.5.beta5/src/setup.py? I just checked and
that is definitely in the tarball.
Nope --
/scratch/wstein/sage-6.5
...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
Total time for all tests: 15.4 seconds
cpu time: 2.2 seconds
cumulative wall time: 15.2 seconds
Just out of curiosity, does it fail repeatedly for you?
--
William Stein
Professor of Mathematics
University of Washington
at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
sage-release group
cpu time: 1.3 seconds
cumulative wall time: 1.3 seconds
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving
On Sun, Nov 2, 2014 at 3:20 PM, Volker Braun vbraun.n...@gmail.com wrote:
#17278
Thanks; positively reviewed.
On Sunday, November 2, 2014 7:54:59 PM UTC, William Stein wrote:
On Sat, Nov 1, 2014 at 3:52 PM, Volker Braun vbrau...@gmail.com wrote:
This is the second release candidate. Most
**
1 item had failures:
1 of 27 in sage.combinat.combinat.stirling_number2
[396 tests, 1 failure, 14.48 s]
William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed
Hi Volker,
I just realized that it seems to be well over 3 months since sage-6.2 was
released, and there still isn't a sage-6.3 release candidate. Is there any
sort of plan or timetable for when you sage-6.3 will get released? 4+
months between releases seems a bit long to me. Do you need
Building this from scratch on SageMathCloud and applying all my
optional stuff worked
well. There were no problems with building R graphics support, and I
didn't have to do anything to hack around that issue.
-- William
--
William Stein
Professor of Mathematics
University of Washington
http
/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group
61 matches
Mail list logo