Title | Can't build manual with Python 3 |
Status | closed |
Priority | optional |
Assigned user | Gareth Rees |
Organization | Ravenbrook |
Description | Trying to do so results in the following error: Extension error: Could not import extension extensions.mps (exception: No module named 'designs') |
Analysis | Need "from . import designs" instead of "import designs" in extensions/mps/__init__.py, but is that portable to Python 2.7? |
How found | manual_test |
Evidence | None as yet. |
Created by | Gareth Rees |
Created on | 2014-02-18 17:15:16 |
Last modified by | Gareth Rees |
Last modified on | 2018-10-24 12:12:40 |
History | 2014-02-17 GDR Created. |
Change | Effect | Date | User | Description |
---|---|---|---|---|
195335 | closed | 2018-10-24 12:12:40 | Gareth Rees | Backport the fixes for job003675 (Can't build manual with Python 3) and for job004061 (Manual does not build with Sphinx 1.6) to custom CET versions 1.113 and 1.114 so that the infosys robot can build the manuals for these versions using the python3-sphinx package on Ubuntu 16.04. |
195334 | closed | 2018-10-24 12:06:21 | Gareth Rees | Delete the built manual for version 1.111. Backport the fixes for job003675 (Can't build manual with Python 3) and for job004061 (Manual does not build with Sphinx 1.6) to version 1.111 so that the infosys robot can build the manual for this version using the python3-sphinx package on Ubuntu 16.04. |
195322 | closed | 2018-10-23 22:21:11 | Gareth Rees | Backport the fix for job003675 (Can't build manual with Python 3) to version 1.112 and the fix for job004061 (Manual does not build with Sphinx 1.6) to versions 1.112-1.116 so that the infosys robot can build the manuals for these versions using the python3-sphinx package on Ubuntu 16.04. |
184032 | closed | 2014-01-16 17:07:56 | Gareth Rees | Make portable to Python 3.3. |