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

Should we jump into Python 3.10 ? #2589

Closed
oesteban opened this issue Oct 11, 2021 · 4 comments
Closed

Should we jump into Python 3.10 ? #2589

oesteban opened this issue Oct 11, 2021 · 4 comments
Labels

Comments

@oesteban
Copy link
Member

For much I would like to start using the walrus operator, I don't think any of the new features of Python 3.8-3.10 would justify that we pushed the current boundary beyond 3.7. However, the new error information features of 3.10 seem to me like an excellent reason to upgrade. I'm especially looking forward to not seeing the "tuple is not callable" errors from typos in nipype workflows anymore, along with other similar issues giving really bad feedback to the user.

WDYT?

@effigies
Copy link
Member

I would wait for 3.10.1. There are often critical bug fixes and the overall ecosystem support will be improved.

@effigies
Copy link
Member

So maybe for 22.0?

@oesteban
Copy link
Member Author

Sure, definitely not thinking of putting this into the 21.0 release mix, and considering the date, there will probably not be a 21.1.

@tsalo
Copy link
Collaborator

tsalo commented Dec 5, 2023

This was done in #3108.

@tsalo tsalo closed this as completed Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants