Closed strogdon closed 12 months ago
With the KeyError
s sage will start with the above.
The sage-doc build thing started with either the latest furo or sphinx 7.1. I do not remember which one. I enabled them almost at the same time.
The keyerror stuff is new and I have not noticed it. Will inspect ASAP.
I thought sphinx
was maybe the reason but I hadn't noticed the furo
upgrade. I'm now using furo-2023.9.10
.
The previous version of furo was causing trouble and would not work with sphinx 7.1.
OK, a "good" action never goes unpunished. As a simplification of the stuff I do to sage-conf, I have let it install the sage-config
executable. It is executed by the sage start up script when found and it is the cause of the complaints. I will make it disappear again.
keyerror fixed by 36e29168bc6202873670571cd39dde260e97d013, sync and rebuild sage-conf. The offending messages should go away.
Looks good here.
The first item is probably cosmetic but I'm curious as to the origin.
The terminal output is now very disorderly. This has been present for several betas now where certain output lines seem to be preceded by multiple tabs.
I'm now seeing multiple
KeyError
s when building the docs. These errors prevent Sage from starting