Do you mean sage tarballs for versions >= 1.0 < 2.10?
--
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 discus
I wonder if there exist those tarballs since those versions were made in
quick pace: https://www.sagemath.org/changelogs/pre-2.7.txt
--
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
Yes, It allows to use bigradings and it works as you would expect. We have
used that approach in some computations we have done. You can see some
examples in the documentation here:
https://doc.sagemath.org/html/en/reference/algebras/sage/algebras/commutative_dga.html#sage.algebras.commutative_d
There are some in gitlab: https://gitlab.com/sagemath/sage/-/tags?page=50
--
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.
They existed (yes, of course). Here is the list of old
versions: https://groups.google.com/g/sage-devel/c/s3C6V-7zef4/m/AQ5pUyEKEcgJ
--
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,
Hmm. The site http://old.files.sagemath.org/src-old/ is back. 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 v
May I get access right to the filesystem of the sage
wiki https://wiki.sagemath.org?
I may attempt to migrate release notes to github wiki.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
Oh, that is very nice. Thank you for the solution to my issue!
I would still classify the workaround as Very Clever, and not a solution
that an average user would come up with on their own.
Perhaps this could be stated more clearly in the documention.
On Sunday, August 18, 2024 at 7:35:21 PM UTC+
On Sunday, August 18, 2024 at 1:55:45 AM UTC-7 Kwankyu Lee wrote:
Do you mean sage tarballs for versions >= 1.0 < 2.10?
I created releases on GitHub for all stable versions >= 2.10.1, just to
include the links to the release tours / changelogs that used to be listed
in https://wiki.sagemath.o
See https://github.com/sagemath/sage/issues/31533 to coordinate the
migration
On Sunday, August 18, 2024 at 5:25:48 PM UTC-7 Kwankyu Lee wrote:
> May I get access right to the filesystem of the sage wiki
> https://wiki.sagemath.org?
>
> I may attempt to migrate release notes to github wiki.
>
I am adding some doc-tests to some code that is currently configured as a
package. My tests look like:
EXAMPLES::
sage: X(...) # needs my_package
sage: Y(...) # needs my_package
sage: Z(...) # needs my_package
Is there a way to avoid adding # needs my_package to every line? Idea
To answer my own question, I just found:
If # optional or # needs is placed right after the sage: prompt, it is a
block-scoped tag, which applies to all doctest lines until a blank line is
encountered.
On Monday 19 August 2024 at 1:51:29 pm UTC+10 Andrew wrote:
> I am adding some doc-tests to
12 matches
Mail list logo
