Dear Antonio, First of all: thank for your work for Sage on archlinux! I like very much to have SageMath together with my system Python environment.
Many developers are actually using Sage with Python3 (as I do). Also a Python3 version of Sage is available on conda-forge. There was also some effort towards a docker image at Cernay few weeks ago. I don't think that we are that far from a switch. Any patch is more than welcome. For now, we do not have any mechanism for py2/py3 version forks of packages. By what you said, it seems reasonable to introduce one. At the level of packages (sage/build/pkgs/) we could for example have an optional checksums-py2.ini that would be used if present and Python2 is used. And we keep the checksums.ini for Python3. Please open a ticket for this. It is definitely reasonable. Best Vincent Le 13/07/2019 à 11:56, Antonio Rojas a écrit :
Hi all, Today I tested building Sage on Arch against our python3 packages. Not surprisingly, it failed to even start. This is due to our python3 ipython package being at version 7 already, with includes some API changes that require some porting in Sage. More and more python modules are completely dropping python2 support: ipython, sphinx, networkx, scipy, matplotlib... These packages can't be upgraded in sage-the-distribution and are therefore stuck to an old version until python2 support is dropped in Sage, which presumably won't happen for at least a couple of years. This is going to be a big problem for distributions in the period when Sage defaults to Python3 but still supports Python 2: much patching will probably be needed to support the newer versions of python3 modules with are still not upgraded in Sage due to not supporting python2. My first question is: would Sage accept patches to support this newer version of python modules (while still keeping compatibility with the older versions shipped by Sage)?. That would allow to reduce the patching required by distros. However, this would still not be completely satisfactory - the updated version code path would not be tested so the risk of regressions would be quite high. Ideally, Sage should allow to ship different versions for the python2 and python3 versions of these modules, so when compiling with python3 it would use the latest versions. Are there any plans in this direction, or are these packages going to be stuck to old versions until python2 support is dropped? --Antonio
-- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8d539fa8-15df-76a9-98a7-e1c3ddcaad4e%40gmail.com. For more options, visit https://groups.google.com/d/optout.
