You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
breakingTaking the requested action is a breaking change (caution)discussWay forward is unclear; discussion is neededtodoMaintainers should do something, but there is no defect
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.
The text was updated successfully, but these errors were encountered:
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
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.
breakingTaking the requested action is a breaking change (caution)discussWay forward is unclear; discussion is neededtodoMaintainers should do something, but there is no defect
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):
I hereby run up the flagpole that under examples/ we don't care about 2.7 to the point that we should
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.
The text was updated successfully, but these errors were encountered: