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

chore: drop python<=3.7 support #783

Closed
wants to merge 5 commits into from
Closed

chore: drop python<=3.7 support #783

wants to merge 5 commits into from

Conversation

kloczek
Copy link

@kloczek kloczek commented Apr 1, 2024

Checklist

  • I acknowledge that all my contributions will be made under the project's license
  • I have made a material change to the repo (functionality, testing, spelling, grammar)
  • I have read the Contribution Guidelines and my PR follows them
  • I have titled the PR appropriately
  • I have updated my branch with the main branch
  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary documentation about the functionality in the appropriate .md file
  • I have added inline documentation to the code I modified

According to https://endoflife.date/python python 3.7 is EOSed since
27 Jun 2023.
Filter all code over `pyupgrade --py38`.

Signed-off-by: Tomasz Kłoczko <[email protected]>
Remove `mock` from test suite requirements.`

Signed-off-by: Tomasz Kłoczko <[email protected]>
@tiwarishubham635
Copy link
Contributor

Is this Python 3.7 has reached its EOL?

@tiwarishubham635 tiwarishubham635 changed the title drop python<=3.7 support chore: drop python<=3.7 support Apr 4, 2024
@tiwarishubham635
Copy link
Contributor

I think you should also remove testing against python 3.7 here

@a-detiste
Copy link

Do you still want to support 3.7 ?

https://bugs.python.org/issue45028

@tiwarishubham635
Copy link
Contributor

Do you still want to support 3.7 ?

https://bugs.python.org/issue45028

I mean we can remove it since its EOL, would need to remove it from test file as well

@tiwarishubham635 tiwarishubham635 added the status: waiting for feedback waiting for feedback from the submitter label Apr 5, 2024
@tiwarishubham635
Copy link
Contributor

As this is an extension of #781, it states:

According to https://endoflife.date/python python 3.7 is EOSed since 27 Jun 2023.
Filter all code over pyupgrade --py38.

However, since we want to maintain support for python>=3.8, shouldn't we use the flag --py38-plus?

@kloczek
Copy link
Author

kloczek commented Apr 5, 2024

As this is an extension of #781, it states:

According to https://endoflife.date/python python 3.7 is EOSed since 27 Jun 2023.
Filter all code over pyupgrade --py38.

However, since we want to maintain support for python>=3.8, shouldn't we use the flag --py38-plus?

It is an mistake in commit comment.

$ pyupgrade --help
usage: pyupgrade [-h] [--exit-zero-even-if-changed] [--keep-percent-format] [--keep-mock] [--keep-runtime-typing] [--py3-plus] [--py36-plus] [--py37-plus] [--py38-plus] [--py39-plus]
                 [--py310-plus] [--py311-plus] [--py312-plus]
                 [filenames ...]

positional arguments:
  filenames

options:
  -h, --help            show this help message and exit
  --exit-zero-even-if-changed
  --keep-percent-format
  --keep-mock
  --keep-runtime-typing
  --py3-plus, --py3-only
  --py36-plus
  --py37-plus
  --py38-plus
  --py39-plus
  --py310-plus
  --py311-plus
  --py312-plus

@kloczek
Copy link
Author

kloczek commented Apr 5, 2024

However, since we want to maintain support for python>=3.8, shouldn't we use the flag --py38-plus?

That is exact option which I've used 😋

@tiwarishubham635
Copy link
Contributor

tiwarishubham635 commented Apr 5, 2024

Cool. Please remove the python 3.7 from test file and then I can review.

@kloczek
Copy link
Author

kloczek commented Apr 22, 2024

done

@tiwarishubham635 tiwarishubham635 linked an issue Apr 22, 2024 that may be closed by this pull request
@tiwarishubham635
Copy link
Contributor

Hey @kloczek! There are some files in rest folder that are auto generated. For those files to reflect this change, we need to make changes in our generator repo. I'll do the same and update it here. Thanks!

@kloczek
Copy link
Author

kloczek commented Apr 22, 2024

OK. No problem. I understand 😄
Just cancel this PR and do how it should be done 😋

@tiwarishubham635
Copy link
Contributor

I have created an internal ticket for this issue to be fixed. Thanks!

@tiwarishubham635
Copy link
Contributor

Closing this as not planned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting for feedback waiting for feedback from the submitter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8.11.1: pytest fails
3 participants