Skip to content

Conversation

@jacomago
Copy link
Contributor

@jacomago jacomago commented Feb 6, 2026

No description provided.

@jacomago jacomago self-assigned this Feb 6, 2026
@jacomago jacomago marked this pull request as ready for review February 6, 2026 14:20
@jacomago
Copy link
Contributor Author

jacomago commented Feb 6, 2026

I tried to get this check in the pre-commit, but adding all ruff lints wasn't enough, I had to add type checking... Which made the PR huge. So I'll stick with just this change for now.


[tool.ruff]
line-length = 120
target-version = "py39"
Copy link
Contributor

Choose a reason for hiding this comment

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

This doesn't mesh well with your attempt to externalise python version into a variable

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not sure I can fix that.

Copy link
Contributor

Choose a reason for hiding this comment

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

You can abandon the idea to externalise it :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You mean out of the dockerfile?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah


[tool.pytest.ini_options]
log_cli = true
log_cli_level = "DEBUG"
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we really need this as default?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Its used to make the logs published by docker appear in the ci logs.

Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't this setting global, i.e. would apply also if I clone and run locally?
Can't it be specified on the command-line when executing pytest?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, you can override it. But sure tests running with debug enabled makes sense?

Copy link
Contributor

Choose a reason for hiding this comment

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

IMO no, since pytest is configured by default to display log messages over a certain verbosity only for failing tests, and since it is an easy modification for any user to alter the verbosity if necessary.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm with @jacomago on this one. If the tests are failing for some reason in CI but are not reproducible locally, this is pretty useful.

Copy link
Contributor

Choose a reason for hiding this comment

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

My point is not to remove it from CI, but that this is a global config. We can still lower the verbosity for CI.

Copy link
Contributor

Choose a reason for hiding this comment

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

@jacomago jacomago force-pushed the set-default-python-version-lower branch from 7dd8ea3 to e3862b6 Compare February 11, 2026 09:54
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarQube Cloud

Copy link
Contributor

@tynanford tynanford left a comment

Choose a reason for hiding this comment

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

It's too bad the 1.8 release already included the update that was >= 3.11 but oh well. Let's make a new release after this PR is merged

Also can you update the README with the new minimum python version?

strategy:
matrix:
include:
- python-version: "3.6"
Copy link
Contributor

Choose a reason for hiding this comment

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

should remove 3.6 - 3.8 in the CI

import logging
import random

from zope.interface import implementer
Copy link
Contributor

Choose a reason for hiding this comment

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

is moving these imports necessary? same goes for all the other import changes

description="resync server"
version="1.5"
readme = "README.md"
requires-python = ">=3.6"
Copy link
Contributor

Choose a reason for hiding this comment

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

update to >=3.9

version="1.5"
readme = "README.md"
requires-python = ">=3.6"
classifiers = [
Copy link
Contributor

Choose a reason for hiding this comment

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

remove 3.6. - 3.8

"Programming Language :: Python :: 3.13",
"Programming Language :: Python :: 3.14",
]
dependencies = [
Copy link
Contributor

Choose a reason for hiding this comment

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

with >= 3.9 , we could use StrEnum and use this pip package like you mentioned? https://pypi.org/project/StrEnum/

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.

4 participants