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

Formally deprecate python2.7, enabling gcing support #3019

Open
gdt opened this issue Aug 3, 2024 · 2 comments
Open

Formally deprecate python2.7, enabling gcing support #3019

gdt opened this issue Aug 3, 2024 · 2 comments
Labels
breaking Taking the requested action is a breaking change (caution) discuss Way forward is unclear; discussion is needed todo Maintainers should do something, but there is no defect

Comments

@gdt
Copy link
Collaborator

gdt commented Aug 3, 2024

Right now, changes to examples/*.py are tested under relatively recent python 3.x and we are ignoring 2.7. At least I am.
And, we say (I said):

Generally, python scripts should work with relatively recent Python 3.
(While they might work with 2.7, no one is paying attention to that.)

I hereby run up the flagpole that under examples/ we don't care about 2.7 to the point that we should

  • document that example scripts are for python3 only even harder than the current text.
  • greenlight removal of 2.7 accomodations

At this point it is hard to conceive of anyone not being able to have python3, and these are examples anyway. (People running LTS that doesn't have python3 and not wanting to build it and prereqs themselves is in my view something we should not cater to, 4 years after python2.7 extended EOL, and "LTS considered troublesome" anyway.)

This would just be an edit to examples/README.md.

This might or might not actually be a breaking change because we don't know if any scripts work with 2.7, because... nobody cares if they do.

@gdt gdt added todo Maintainers should do something, but there is no defect breaking Taking the requested action is a breaking change (caution) discuss Way forward is unclear; discussion is needed labels Aug 3, 2024
@zuckschwerdt
Copy link
Collaborator

Agreed. Perhaps start with changing to a shebang of #!/usr/bin/env python3 in all scripts.

@gdt
Copy link
Collaborator Author

gdt commented Aug 3, 2024

I'll let this sit a week for others to comment, and the dedup changes land, and then open a PR to change docs and #! change. Then we can after another while start ripping out from future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Taking the requested action is a breaking change (caution) discuss Way forward is unclear; discussion is needed todo Maintainers should do something, but there is no defect
Projects
None yet
Development

No branches or pull requests

2 participants