-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix!: use check_nested_command, drop python 3.9 #1632
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
Conversation
We should also pin the click version. |
Should we pin it to 8.2.0 or the 8.1.8 |
I guess |
Shall we follow click in dropping support for python3.9? I'd say yes. |
This comment was marked as resolved.
This comment was marked as resolved.
I think the easy install check fails because the error that this PR tries to fix is part of the latest docker image that is used in the test case. So the failure should be safe to ignore. |
v14+ requires py310+, so seems fine |
🎉 This PR is included in version 5.25.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Summary: This pull request addresses an issue where the bench CLI fails to initialize a new bench due to an incompatibility with the click package. The _check_multicommand import used in bench is no longer available in newer versions of click. Changes Introduced: Pins click to version 8.1.3 to ensure compatibility with bench. Updates Dockerfile/environment setup to include the fixed click version before installing bench. Reason for Change: Without this fix, running bench init throws an ImportError, breaking the build and preventing Frappe environments from being initialized properly. frappe/bench#1632
Click released a new version 8.2.0
It doesnt have the _check_multicommand function as it has been renamed
Ref https://github.com/pallets/click/blob/8.2.0/src/click/core.py
pip install frappe-bench
fails because of thisCaution
This PR drops support for python3.9.