Skip to content

Update pyproject.toml.jinja to drop python 3.8 and 3.9 #22

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

Closed
wants to merge 8 commits into from

Conversation

willingc
Copy link
Collaborator

@willingc willingc commented Feb 25, 2025

Depends on #24

@willingc willingc mentioned this pull request Feb 25, 2025
7 tasks
@willingc willingc changed the title Update pyproject.toml.jinja to target version py39 Update pyproject.toml.jinja to drop python 3.8 and 3.9 Feb 25, 2025
@willingc
Copy link
Collaborator Author

Thanks @jni and @Czaki for the review.

@jni
Copy link
Member

jni commented Feb 26, 2025

Just waiting for CI

@jni
Copy link
Member

jni commented Feb 26, 2025

Ah, we'll need to merge #24, then merge it into this one. I've updated the description.

@jni
Copy link
Member

jni commented Feb 26, 2025

😕 I don't understand why there's still py3.9 tests...

@Czaki
Copy link
Contributor

Czaki commented Feb 26, 2025

There are still here:

python-version: ["3.9", "3.10", "3.11", "3.12"]

python-version: ["3.9", "3.10", "3.11", "3.12"]

One needs to update workflows, not only tox.

@jni
Copy link
Member

jni commented Feb 26, 2025

Ah, I missed that they ran in #24! 🤦

Copy link
Collaborator

@TimMonko TimMonko left a comment

Choose a reason for hiding this comment

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

Was about to come in and make an issue since the toml didn't appear up to date in my new plugin. As far as I can tell this fixes and clarifies everything I saw was wonky 👍

Wait, I think tox.ini also needs updated to drop 39 and add 313 (in addition to Grzegorz suggestions)

@DragaDoncila
Copy link
Contributor

@willingc do you want to update this PR to remove the 3.9 mentions in the github workflows? I think that's all we need to get it green.

@TimMonko
Copy link
Collaborator

TimMonko commented Mar 6, 2025

Here's a PR to your fork @willingc that updates the workflows:
willingc#1

@willingc willingc force-pushed the patch-1 branch 3 times, most recently from 0ef50db to 1df69f0 Compare March 7, 2025 02:35
@willingc
Copy link
Collaborator Author

willingc commented Mar 7, 2025

I'm going to troubleshoot this in a separate PR.

@TimMonko
Copy link
Collaborator

TimMonko commented Mar 7, 2025

I'm going to troubleshoot this in a separate PR.

Sounds good, just ping me when its ready or you need it looked at

@willingc
Copy link
Collaborator Author

willingc commented Mar 7, 2025

Replaced by #35

@willingc willingc closed this Mar 7, 2025
TimMonko added a commit that referenced this pull request Mar 7, 2025
This PR replaces #22. It does the following:
- add support for Python 3.13
- drop support for Python 3.8 and 3.9
- update templates to be consistent with these versions
- add pre-commit config file to the repo. Includes argument to ruff format single quote style to match napari's pyproject.toml config
- fix linting errors flagged by pre-commit
- exclude jinja files from the repo's pre-commit check for end-of-file fixes since it requires changes to the end-of-file for template jinja files. When an extra newline is placed on the jinja files, it causes the generated-from-template files to fail testing.
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.

5 participants