Skip to content

Update build to fix CI#472

Merged
agoscinski merged 10 commits intomainfrom
fix/build
Sep 11, 2024
Merged

Update build to fix CI#472
agoscinski merged 10 commits intomainfrom
fix/build

Conversation

@agoscinski
Copy link
Contributor

@agoscinski agoscinski commented Sep 10, 2024

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.

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.
@agoscinski agoscinski changed the title Treat warnings not anymore as errors Update build to fix CI Sep 10, 2024
@agoscinski agoscinski force-pushed the fix/build branch 5 times, most recently from c51943e to a14060e Compare September 10, 2024 06:12
- 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.
Copy link
Contributor

@GeigerJ2 GeigerJ2 left a 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.

Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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

Copy link
Contributor Author

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.

@agoscinski agoscinski merged commit 78c3534 into main Sep 11, 2024
@agoscinski agoscinski deleted the fix/build branch September 11, 2024 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants