Le 09/02/2021 à 02:22, Matthias Koeppe a écrit :
On Monday, February 8, 2021 at 10:42:59 AM UTC-8 Matthias Koeppe wrote:
I think it should be the responsibility of the downstream package to
define a versioning policy - define when they plan to drop support for a
particular Sage version.
Then we can use an appropriate version constraint in the
"install-requires.txt" file for this package in build/pkgs.
Another thing that a downstream package can do is declare an
"install_requires" on the Sage library, specifying a supported range of
versions. Then we should be able to use the dependency resolution by pip to
be sure to install a compatible version.
>
Note https://trac.sagemath.org/ticket/30912 updates the metadata of the
Sage library, defining the distribution name "sagemath-standard". (Another
distribution that could be used for versioning is "sage_conf".)
Also note the pip dependency resolver has just changed with the update to
pip 20.3.3 in #30589 (see
https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020).
I think that the most important thing we care about is the answer to
What is the most recent version of package X that
runs on Sage version Y?
On the downstream side, one could just add a requirement
sagemath>=Y
meaning that sagemath < Y is not supported.
However, I don't know enough of pip to understand how to make
"pip install X" retrieve the information. Would that work out
of the box with sage 9.3.beta7?
Best
Vincent
--
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/0d4438e8-7332-4680-50d0-380715320394%40gmail.com.
