On 5/27/20 4:08 PM, Volker Braun wrote:
> Which python versions do we want to be compatible with now? Please separate
>
>
> A)Supported Python versions for building Sage
>
> Note that I'm already seeing f-strings in #29547 so unless a policy is
> formulated real soon the de-facto answer is going to be Python 3.6+
This is OK, see below.
> B) Supported Python versions for running Sage
>
> The default answer for B) is whatever is
> in build/pkgs/python3/package-version.txt, of course
I think we should make the two agree, to avoid pointless complexity. We
should base this (ongoing) decision off of (a) what is supported by
python upstream and (b) what is supported by the distributions that
consistently package and contribute to sage.
A rough list of the distributions that we should be nice to is,
$ find ./build/pkgs/ -path '*/distros/*.txt' -exec basename '{}' \; \
| sort -u
alpine.txt
arch.txt
centos.txt
conda.txt
cpan.txt
cygwin.txt
debian.txt
fedora.txt
freebsd.txt
gentoo.txt
homebrew.txt
nix.txt
opensuse.txt
slackware.txt
And the upstream list is at,
https://devguide.python.org/#branchstatus
A policy like "we support the latest security release branch, and all
bugfix release branches" looks like it will do the trick presently.
(Ignoring the intermediate bugfix branches won't be much easier, since
the newest security release lacks all of the same features.)
--
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 discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/67324bb0-ff24-7e2b-a06f-e2c693424795%40orlitzky.com.
