-
Notifications
You must be signed in to change notification settings - Fork 37
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
Update build to fix CI #472
Conversation
There are some sphinx internal warnings that are time consuming to debug and don't affect the quality of the tutorial page, so we ignore them by treating warnings as warnings.
The current pinned version in the requirements do not work anymore so all pinning of versions have been removed.
c51943e
to
a14060e
Compare
- pipx has been updated - virtual box does not work for the moment so we have to ignore it. - the underscore explanation link works but somehow is marked as broken so we replace with an explanation from realpython - big-map.eu does not work but is sponsor so cannot be replaced/removed
Update to python 3.11 and update sphinx and subsequent dependencies.
RTD wants that the version is now specified in the build.tools. Updated to python 3.12
Uses latest version, also the python version should not matter for a formatter.
a14060e
to
5387dc4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really an expert on CI stuff, but changes look reasonable to me. If this fixes the broken CI, and we can merge the other PRs, I'd say we can go for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we pin the versions here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can pin them. Sometimes it is more annoying than helpful to pin verison if a repo changes frequently and needs to update its dependencies. But I guess in this case we only need to update the occasionally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I usually had the same experience so far, and ended up not pinning them usually :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can pin them. Sometimes it is more annoying than helpful to pin verison if a repo changes frequently and needs to update its dependencies. But I guess in this case we only need to update the occasionally.
Mostly just updating all the files and dependencies.
Maybe controversial change is that I removed the
-W
flag during the sphinx-build process, so warnings are treated as warnings and not as errors. The reason for this is because I got sphinx warnings which in my experience are very hard to debug and only marginal add to the quality to the doc page. I will not fix these warnings.