Skip to content

Conversation

@JoeZiminski
Copy link
Member

@JoeZiminski JoeZiminski commented Nov 28, 2025

Further to #635 this PR pins fancylog to avoid the release in which package versions was logged by default, that included a subprocess call. This slowed down tests a lot. Tests are now running at their usual duration.

TODO: reverse CI changes before merging

pyproject.toml Outdated
Comment on lines 29 to 30
"fancylog >= 0.7.0; python_version >= '3.11'",
"fancylog < 5; python_version < '3.11'",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why <5 when we're on 0.7.0? Why not just make it >0.7.0 across all python versions?

Copy link
Member Author

@JoeZiminski JoeZiminski Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought I saw that the dependency resolver failed and installed older versions of fancylog for old versions of python. But I think I might have made this up 🤔 will do a quick check now

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By why <5 when we haven't even released v1? 🤣

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't even notice that 😂 it should be 0.5.0, I think it still worked because fancylog 0.5.0 doesn't support python 3.9 or 3.10 (?, just checking) and so it installs <0.5.0 on these runners and is fine.

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.

3 participants