Skip to content

Conversation

@JeppeKlitgaard
Copy link

I was a bit sloppy and included Python 3.10 in the range of supported Pythons. It has actually reached end-of-life last year, so it would be fine (perhaps even preferable) not to support it anymore. Apologies for the noise!

@AnderBiguri
Copy link
Member

Hum, I think I may leave it as is actually.

When I started python TIGRE I needed to support python 2 because while it was 8 years deprecated, institutions like the Diamond Light Source had so much tech debt that they could not update to Python 3.
So while I am quite keen in making sure modern pythons are supported, I want to keep backwards compatibility as wide as possible. If supporting python 3.10 doeas not break anything extra that I am not aware of, I am happy to have as much back-compatibility as possible

@JeppeKlitgaard
Copy link
Author

That's perfectly fine as well, feel free to close this.

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.

2 participants