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 python 3.6 and 3.7 which are past end of life upstream #23

Merged
merged 4 commits into from
Dec 3, 2023

Conversation

Pierre-Sassoulas
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas commented Nov 4, 2023

Cherry-picked from #8, I'm doing things progressively so it's reviewable.

Closes #11

@Pierre-Sassoulas Pierre-Sassoulas added the enhancement New feature or request label Nov 4, 2023
Copy link

codecov bot commented Nov 4, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (48212e2) 94.16% compared to head (f6e9b9e) 93.97%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
- Coverage   94.16%   93.97%   -0.19%     
==========================================
  Files          18       18              
  Lines         548      548              
  Branches      106      106              
==========================================
- Hits          516      515       -1     
  Misses         23       23              
- Partials        9       10       +1     
Flag Coverage Δ
3.10 93.97% <ø> (ø)
3.11 93.97% <ø> (ø)
3.6 ?
3.7 ?
3.8 93.97% <ø> (ø)
3.9 93.97% <ø> (ø)
macos-latest 93.97% <ø> (ø)
ubuntu-20.04 ?
ubuntu-latest 93.97% <ø> (ø)
windows-latest 93.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Pierre-Sassoulas
Copy link
Member Author

@stdedos I think it could be merged even with the negative coverage change.

@Pierre-Sassoulas
Copy link
Member Author

@stdedos could you review this, please :) ? The CI is red because of an indirect coverage changes that I think we can ignore.

@stdedos stdedos added this to the Release v2 milestone Nov 11, 2023
@stdedos
Copy link
Collaborator

stdedos commented Nov 11, 2023

@stdedos could you review this, please :) ? The CI is red because of an indirect coverage changes that I think we can ignore.

Yeah, this seems to be the problem:
image
https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/23/indirect-changes

I'd be nice to figure out why is this happening, but it is definitely not a priority - given the benefits of this PR.

"I am not reviewing this" since it's not scheduled to go in yet.
Otherwise all looks golden to me and it is approved 💚


Plan is:

Question:

  1. Can Add python 3.12 support in CI and metadata #24 become thinner? I could consider it for v1
  2. Can Support pylint v3 #12 be fixed for v1? I lost track on what was the pylint issue 😅

@Pierre-Sassoulas
Copy link
Member Author

Can #24 become thinner? I could consider it for v1

We can remove the drop of python 3.6 / 3.7 (probably)

Can #12 be fixed for v1? I lost track on what was the pylint issue 😅

Need to support 3.12 maybe something else

@stdedos
Copy link
Collaborator

stdedos commented Nov 17, 2023

Can #24 become thinner? I could consider it for v1

We can remove the drop of python 3.6 / 3.7 (probably)

I'd consider it for v1 - but it doesn't have to wait "the usual" 1w-period.

So next week we release master, and a thin #24 afterwards

@Pierre-Sassoulas
Copy link
Member Author

Hey, I tried dropping the removal of python 3.6 / 3.7 and simply adding python 3.12, but this is non trivial (https://github.com/pylint-dev/pylint-pytest/actions/runs/7010519218/job/19071209667?pr=24). It's been nearly two months since the release of python 3.12 / pylint 3.0 and python 3.6 / 3.7 have been EOL for a long time, maybe we could just drop EOL interpreters and release 2.X serie, what do you think ?

@Pierre-Sassoulas
Copy link
Member Author

See this issue in vscode/pylint : microsoft/vscode-pylint#460 for example

@stdedos
Copy link
Collaborator

stdedos commented Nov 28, 2023

Thank you for trying ❤️

Sadly, my OSS time has been near-zero these days.
I will make it my first priority to merge these.

@Pierre-Sassoulas
Copy link
Member Author

No problem. This one is ready the coverage drop is acceptable imo.

@stdedos stdedos mentioned this pull request Dec 1, 2023
pyproject.toml Show resolved Hide resolved
Copy link
Collaborator

@stdedos stdedos left a comment

Choose a reason for hiding this comment

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

Must be merged after #27, if it becomes ready for a Monday release

@stdedos stdedos added the blocked label Dec 2, 2023
@stdedos
Copy link
Collaborator

stdedos commented Dec 3, 2023

I took the liberty to prepare this for tomorrow 🙃

* master:
  Update/Prepare Changelog for v1.1.7
  use pylint v3 in the repo
  remove support of pylint v1
  Support pylint v3

Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>

Additionally, some minor format modifications at `CHANGELOG.md`
@Pierre-Sassoulas
Copy link
Member Author

Thank you @stdedos :)

@Pierre-Sassoulas Pierre-Sassoulas merged commit 57a868b into master Dec 3, 2023
30 of 31 checks passed
@Pierre-Sassoulas Pierre-Sassoulas deleted the drop-eol-python-add-3.12 branch December 3, 2023 21:12
This was referenced Dec 3, 2023
@stdedos stdedos restored the drop-eol-python-add-3.12 branch December 4, 2023 06:48
@stdedos
Copy link
Collaborator

stdedos commented Dec 4, 2023

Thank you @Pierre-Sassoulas for all your contributions and patience 😁 🙏

@Pierre-Sassoulas Pierre-Sassoulas deleted the drop-eol-python-add-3.12 branch December 6, 2023 21:02
stdedos added a commit that referenced this pull request Feb 2, 2024
# Added

* Migrate setup.py to pyproject.toml (#8)
* Support for Python 3.12 (#3,
  "side effect" of #8)
* Introduced @dependabot (part of #28)
* Improved reliability of the `FixtureChecker` class (#29)

# Removed

* Support for Python 3.6 & 3.7 (#23)

# Improved

* Increased reproducibility of the project, by using `pip-compile` for the development dependencies
  (#28, small bugfix in #39)
* Minor CI + License updates (in 29f0c33, e0e529a, 8f56d1c)

Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos added a commit that referenced this pull request Feb 2, 2024
# Added

* Increased reproducibility of the project, by using `pip-compile` for the development dependencies
  (#28, small bugfix in #39)
* Introduced @dependabot (part of #28)

# Removed

* Support for Python 3.6 & 3.7 (#23)

# Improved

* Migrate setup.py to pyproject.toml (#8)
* Support for Python 3.12 (#3,
  "side effect" of #8)
* Improved reliability of the `FixtureChecker` class (#29)
* Minor CI + License updates (in 29f0c33, e0e529a, 8f56d1c)

Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
stdedos added a commit that referenced this pull request Feb 2, 2024
# Added

* Increased reproducibility of the project, by using `pip-compile` for the development dependencies
  (#28, small bugfix in #39)
* Introduced @dependabot (part of #28)

# Removed

* Support for Python 3.6 & 3.7 (#23)

# Improved

* Migrate setup.py to pyproject.toml (#8)
* Support for Python 3.12 (#3,
  "side effect" of #8)
* Improved reliability of the `FixtureChecker` class (#29)
* Minor CI + License updates (in 29f0c33, e0e529a, 8f56d1c)

Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Drop Python 3.6 + 3.7
2 participants