Thanks!
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit
I set
https://github.com/sagemath/sage/pull/37390
to blocker. Please merge #37390 to the next rc.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Congrats!
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Succeeded after sage -pip install meson-python.
On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote:
> Incremental build failed
>
> [scipy-1.11.2]
> [..]
> [scipy-1.11.2] scipy-1.11.2
Incremental build failed
[scipy-1.11.2]
[..]
[scipy-1.11.2] scipy-1.11.2
[scipy-1.11.2]
[sagelib-10.2.beta3] Removing file or directory
Thanks a lot!
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit
#35919 and #35951 merged here are dependent on #35749 not merged yet.
#35749 is ready to be merged.
It's a mistake that #35919 and #35951 did not declare #35749 as a
dependency.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe
Congratulations!
On Sunday, May 21, 2023 at 8:10:07 AM UTC+9 Volker Braun wrote:
The "master" git branch has been updated to Sage-10.0. As always, you can
get the latest beta version from the "develop" git branch. Alternatively,
the self-contained source tarball is at
On Tuesday, May 16, 2023 at 6:13:03 AM UTC+9 John H Palmieri wrote:
I consistently see these failures on various OS X machines:
sage -t --long --random-seed=244618093388694547212515065258622925284
src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed
sage -t --long
The release tour for the upcoming 10.0 release is at
https://github.com/sagemath/sage/wiki/Sage-10.0-Release-Tour
and needs your care.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails
Congratulations for the first release on GitHub!
> We haven't quite settled on what I'll do with positively reviewed tickets
that end up not building correctly ... My current plan is to re-request
review, i.e. reset the approval of the reviewer(s).
>
> Also, the de-facto "positive review"
Congratulations for the first release on GitHub!
We haven't quite settled on what I'll do with positively reviewed tickets
that end up not building correctly ... My current plan is to re-request
review, i.e. reset the approval of the reviewer(s).
Also, the de-facto "positive review" criterion
Nice tip! Done also for 9.7, 9.6.
On Tuesday, February 14, 2023 at 5:14:50 AM UTC+9 William Stein wrote:
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
That is a nice summary of the GitHub migration efforts. Thank you.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To
Thanks. Done.
On Saturday, February 11, 2023 at 1:46:33 AM UTC+9 matthia...@gmail.com
wrote:
The link to it from https://wiki.sagemath.org/ReleaseTours will have to be
adjusted after the renames.
On Friday, February 10, 2023 at 1:11:18 AM UTC-8 Kwankyu Lee wrote:
The release tour
The release tour for the upcoming 9.8 release is now found at
https://github.com/sagemath/sage/wiki/Sage-9.8-Release-Tour
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an
Please consider #34873 for this release.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on
It's time to work on the release tour for the upcoming 9.8 release
https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an
> However, I don’t understand the difference between the list of features to
> be detected (indicated before running the tests) and the list of detected
> features (indicated after doctesting).
>
A feature is not detected until a doctest that requires the feature is
encountered (if I
On Wednesday, September 28, 2022 at 5:45:47 PM UTC+9 Clemens Heuberger
wrote:
> I encountered one doctest error in
> src/sage/schemes/toric/sheaf/klyachko.py
> which depends on the random seed:
>
> Failing seed: 76370439031557170215448337120651728168
This is being tracked in
On Tuesday, September 20, 2022 at 11:25:43 PM UTC+9 emanuel.c...@gmail.com
wrote:
> Upgrade from a detached head 9.7.rc1 to 9.7 successful : passes ptestlong
> wit "All tests passed !".
You are fortunate. I constantly have
sage -t --random-seed=174323800149221866205482120593739177259
Fixed in #34557
https://trac.sagemath.org/ticket/34557
which needs review.
On Monday, September 19, 2022 at 5:38:59 PM UTC+9 Clemens Heuberger wrote:
> On most of my machines, ptestlong passes (except for the usual transient
> failures in src/sage/interfaces/process.pyx ).
>
> However, on
This is fixed in #34467,
https://trac.sagemath.org/ticket/34467,
which is critical.
On Sunday, September 18, 2022 at 6:03:12 AM UTC+9 list...@gmail.com wrote:
>
> The second one appears almost all the time (and always when run alone),
> but I have been unable to find a pattern of failure:
>
Great! Thanks.
On Thursday, September 8, 2022 at 8:39:00 AM UTC+9 Volker Braun wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> 08202bc1ba7 (HEAD ->
We post the link again here for visibility and easy access:
https://trac.sagemath.org/wiki/ReleaseTours/sage-9.7
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
./bootstrap
?
On Wednesday, August 10, 2022 at 5:22:28 PM UTC+9 emanuel.c...@gmail.com
wrote:
> When trying to upgrade from (vanilla) 9.7.beta6 running on Debian testing
> :
>
> harpent@zen-book-flip:/usr/local/sage-9$ ./configure --help | grep edit
> --enable-editable use an
It would make a sense to release sage beta8 quickly that just contains
https://trac.sagemath.org/ticket/34252
so that developers can make use of the revived Build Documentation badge in
trac.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
On Monday, July 11, 2022 at 2:53:36 PM UTC+9 tdumont wrote:
> When upgrading from beta 4 to beta5, I got the following error, which
> persists after doing: make doc-clean doc-uninstall; make
>
> (Unbuntu 22-04, up to date).
>
> I got this error massage:
> [sagemath_doc_html-none] [misc ]
On Wednesday, January 12, 2022 at 11:56:52 AM UTC+9
dmo...@deductivepress.ca wrote:
> I installed this version of python yesterday, by downloading a MacOS
> installer from https://www.python.org/downloads/macos/. I did this
> because my first failed attempt to build 9.5.rc0 was with Python
> Finally, I would suggest to make sure that the Xcode Command Line
> Tools are up to date (using softwareupdate)
>
In my case, usual "xcode-select --install" and software update reported
that the command line tools was up to date, but sage make still failed. I
finally succeeded after having
With this release, the command
sage -docbuild all pdf
stops with the failure below. How about others?
Building it/a_tour_of_sage.
[a_tour_of] building [latex]: all documents
[a_tour_of] Merging environment/index files...
[a_tour_of] ... done (0 todos, 1 index, 0 citations, 0 modules)
...
Thanks for the beta release.
It seems unusual that the tickets included in the release are not yet
closed in Trac.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
It is the greatest release of Sage ever. Thank you!
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To view this
Thanks for the release.
Incremental build from 9.3.rc1 on mac pro with Big Sur succeeded with no
problem. All doctests passed.
On Wednesday, April 7, 2021 at 7:33:00 AM UTC+9 Volker Braun wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively,
>
> Looks like the command line tools might actually be Xcode 12 beta. This is
>> not supported yet -- see https://trac.sagemath.org/ticket/30494 (which
>> needs help)
>>
>
Solved by downgrading to Xcode 11.5. Thank you!
--
You received this message because you are subscribed to the Google
Hi,
I am failing to build from scratch Sage 9.2 beta11 since beta10 or perhaps
even earlier beta. My system is macOS 10.15.6 with Xcode 11.7. The log
follows:
...
...
[gf2x-1.3.0] /Users/kwankyu/GitHub/sage/build/bin/sage-spkg: line 73:
warning: setlocale: LC_ALL:
Wow! I would take the honour to be the second person to celebrate the
release of Sage on Python 3 by default.
I thank the great people in the Sage developer community who made this!
A nice present for the new year!
--
You received this message because you are subscribed to the Google Groups
On Monday, June 10, 2019 at 4:40:52 PM UTC+9, Sébastien Labbé wrote:
>
> Testing the following optional and external packages:
>
> External software detected for doctesting:
> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc
>
> Using
>
On Wednesday, October 3, 2018 at 10:01:40 PM UTC+9, Samuel Lelievre wrote:
>
> Wed 2018-10-03 12:36 UTC+2, Travis Scrimshaw:
> >
> > On Wednesday, October 3, 2018 at 7:35:08 PM UTC+10, Kwankyu Lee wrote:
> >>
> >> On Wednesday, October 3, 2018 at 3:14:32
On Wednesday, October 3, 2018 at 3:14:32 PM UTC+9, tsc...@ucdavis.edu wrote:
>
> I believe there is a Heisenbug in src/sage/rings/function_field/ideal.py.
> Here is a specific test that can sometimes fail:
>
> sage: K. = FunctionField(GF(3^2)); R. = K[]
> sage: F. = K.extension(t^3 + t^2 - x^4)
I noticed this:
$ sage -t src/sage/rings/finite_rings/*
Running doctests with ID 2017-11-17-23-04-49-f065787a.
Git branch: finite_field_extension_trac24195_dev
Using --optional=mpir,python2,sage
Traceback (most recent call last):
File "/Users/Kwankyu/GitHub/sage/src/bin/sage-runtests", line
On Friday, November 17, 2017 at 6:53:41 PM UTC+9, Thierry wrote:
>
>
> How much available RAM do you have ? Building the documentation is no
> longer the last step, hence if that fails, everything after that is not
> built.
Ah, I didn't know that. This (building the documentation is no
On Thursday, November 16, 2017 at 8:38:52 PM UTC+9, Jeroen Demeyer wrote:
>
>
> It seems that sympy simply wasn't built. I am not aware of any bug in
> the build system (especially not specific to OS X) which could cause that.
>
The fresh build (of actually Sage 8.1rc1) finished with no
>
> Sorry to ask a silly question, but are you sure that
>
> (1) You actually ran "make"
>
Yes. But this was not a fresh one. I ran "make distclean", and then "make".
> (2) That run of "make" succeeded without errors
>
There was an error in building doc. I ignored this as there was no
Then I created a new directory at SAGE_ROOT/src/ext/directory and put a
file "test.txt"
$ ls -l src/ext/
total 0
drwxr-xr-x 3 Kwankyu staff 102 Nov 16 15:42 directory
drwxr-xr-x 4 Kwankyu staff 136 Apr 15 2015 doctest
drwxr-xr-x 5 Kwankyu staff 170 Apr 14 2016 gap
drwxr-xr-x 3
So I ran
sage -i sympy
and Sage installed sympy. Then now this works fine.
$ sage -t src/sage/rings/function_field/*
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an
I get the following just after "make",
Hera:sage$ sage -t src/sage/rings/function_field/*
Running doctests with ID 2017-11-16-15-36-55-9cd5f354.
Git branch: develop
Using --optional=mpir,python2,sage
Doctesting 8 files.
Traceback (most recent call last):
File
Hi,
Does this release support Xcode 9.1 on mac?
I built this release with Xcode 9.1, and the Sage built shows strange
behaviors. Is this because of Xcode 9.1?
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group
Indeed.
sage -t --long --warn-long 75.4 src/sage/rings/function_field/function_field
.py
**
File "src/sage/rings/function_field/function_field.py", line 69, in sage.
rings.function_field.function_field
Warning, slow doctest:
I just noticed
sage$: sage -t src/sage/rings/function_field/*
...
ValueError: unknown file extension '.pyc'
This worked fine previously...
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving
50 matches
Mail list logo
