-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.6: Fix locale/encoding issues in docbuild, then re-enable Python 3.6 #30576
Comments
comment:1
Posting my branch containing few changes that need to be done in order to build doc with ubuntu 18.04 bionic and python 3.6. The changes are not sufficient. Other similar issues arise when sphinx is running... New commits:
|
Branch: public/30576 |
Commit: |
comment:2
Two comments here:
|
comment:3
Warnings one keeps getting are errors in processing function arguments, i.e. in introspecting Python code. Ignoring them would give you a broken doc.
I think the problems come from a new(ish) sphinx which is run as a backend for our custom docbuilder, and anyway the move from Python 3.6 to 3.7 was somewhat big as far as utf-8 support is concerned. I really think that fully supporting 3.6 is hard, and we have better things to do. Python has solved this problem by moving to 3.7, let's not reinvent the wheel here. |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Dependencies: #30053 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:11
Replying to @dimpase:
There are 2 things I don't understand here:
|
comment:12
With the current branch with no hacky changes, I can build the documentation with the flag
I am now trying to see what is wrong with the output doc... |
Attachment: error.log |
comment:13
the command
gives relatively few errors (see 112 lines error.log attached). Very often it is the same error, for example, 60 of them are related to crystals code either I still do no know to which doc string these positions are refering to. |
comment:14
Hint:
|
comment:15
But these symbols do not occur in the crystals code:
|
Changed dependencies from #30053 to none |
This comment has been minimized.
This comment has been minimized.
Dependencies: #30008 |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Author: Matthias Koeppe |
comment:22
On Ubuntu 18.04, after uninstalling python3.8 so that python3.6 gets picked up by
I confirm that I let someone change the status to positive review if no problem occurs on the github actions side. |
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/267855732, ... to Sébastien Labbé, https://github.com/mkoeppe/sage/actions/runs/267855732, ... |
Changed reviewer from Sébastien Labbé, https://github.com/mkoeppe/sage/actions/runs/267855732, ... to Sébastien Labbé |
comment:24
Thanks for testing! Also |
Changed branch from public/30576 to |
Follow-up from #15791, #29033, #30053, the latter of which disabled use of system Python 3.6.
With Python 3.6, there is a failure building the documentation on
ubuntu-bionic-standard
(using/usr/bin/python3.6
, https://github.com/mkoeppe/sage/runs/1106251169):This is coming from #30002 "force C locale in docbuild and remove some obsolete stuff", which added this:
In the present ticket, we rework the fix in #30002 so that it works with Python 3.6 too (in which setting the "C" locale sabotages UTF-8 operation.)
Supporting Python 3.6 allows Sage to use the system Python on some older Linux distributions that are still in widespread use in scientific computing, including centos-8 and fedora-{26,27,28} (although Python 3.7.x packages are also available for these). See #29033 for more details.
For the unrelated failures in the Sphinx package installation that #29033 tried to work around, see #30008.
(#30008 is a dependency of this ticket merely for the convenience of testing.)
References:
Depends on #30008
CC: @antonio-rojas @dimpase @slel @orlitzky @kiwifb @embray @fchapoton
Component: build
Author: Matthias Koeppe
Branch/Commit:
945c8c5
Reviewer: Sébastien Labbé
Issue created by migration from https://trac.sagemath.org/ticket/30576
The text was updated successfully, but these errors were encountered: