Skip to content
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

Drop support for Python 3.8 #591

Merged

Conversation

alexted
Copy link
Contributor

@alexted alexted commented Oct 24, 2024

@nycholas nycholas linked an issue Oct 26, 2024 that may be closed by this pull request
requirements/tests.txt Outdated Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
Copy link
Member

@nycholas nycholas left a comment

Choose a reason for hiding this comment

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

Great job, just a few changes...

@alexted alexted changed the title Python 3.8 removed as not supported Drop support for Python 3.8 due to end of life Oct 26, 2024
@alexted alexted changed the title Drop support for Python 3.8 due to end of life Drop support for Python 3.8 Oct 26, 2024
@alexted alexted requested a review from nycholas October 26, 2024 22:18
tests/utils.py Outdated
from typing import Any


class EqMock:
Copy link
Member

Choose a reason for hiding this comment

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

It isn't being used in any place, you can remove this file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought you might need it in tests later on. Well, if not, I'll delete it.

'terminal_id': 1,
'headers': {
'User-Agent': EqMock(),
Copy link
Member

Choose a reason for hiding this comment

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

Very interesting approach! 👏

Copy link
Member

@nycholas nycholas left a comment

Choose a reason for hiding this comment

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

Awesome! Only one comment...

Copy link
Member

@nycholas nycholas left a comment

Choose a reason for hiding this comment

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

🚀

@alexted
Copy link
Contributor Author

alexted commented Oct 27, 2024

There are doubts as to whether it is worth ‘spreading’ tests in different directories. In addition to the classic tests/ in the project, they are now also in /examples. And there is a lot of boilerplate code and copypaste there. Is it really a good idea?

@alexted alexted requested a review from nycholas October 27, 2024 12:25
@nycholas
Copy link
Member

@alexted The issue here is that I never revisited the examples to test them and ensure they remain supported by the library as changes have occurred. I’m aware of the duplicate code, but I believe it’s necessary to keep everything testable. You can see the related issue here and the proposed solution here.

@nycholas
Copy link
Member

@alexted If you have another approach for that, we can create a GitHub discussion topic and debate there, what do you think?

@alexted
Copy link
Contributor Author

alexted commented Oct 27, 2024

@alexted If you have another approach for that, we can create a GitHub discussion topic and debate there, what do you think?

Thanks, I'm looking into the links you shared, but I can't yet see the connection between the above problem and keeping examples up to date. I think it's really worth a separate discussion. At least in the context of how ci/cd and testing part in particular can be simplified by unifying and parameterising configuration and manifests.

Copy link
Member

@nycholas nycholas left a comment

Choose a reason for hiding this comment

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

🚀

@nycholas nycholas merged commit f5d60c5 into cenobites:master Oct 28, 2024
10 checks passed
@alexted alexted deleted the feature/remove-unsupported-python38 branch November 3, 2024 13:30
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.

Remove support to Python 3.8
2 participants