-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
pip effectively deprecated use of setuptools (in read-only directories) #21612
Comments
This was referenced Jul 9, 2023
We can use remove setup.py and stick to Existing apps will have to upgrade on their own. |
ankush
added a commit
to ankush/frappe
that referenced
this issue
Jul 17, 2023
ankush
added a commit
that referenced
this issue
Jul 17, 2023
* chore: remove setup.py requirements.txt boilerplate * feat(DX): PEP517 compatible builds on new apps closes #21612
pateljannat
pushed a commit
to pateljannat/frappe
that referenced
this issue
Jul 31, 2023
* chore: remove setup.py requirements.txt boilerplate * feat(DX): PEP517 compatible builds on new apps closes frappe#21612
ankush
added a commit
that referenced
this issue
Dec 13, 2023
* feat(DX): PEP517 compatible build in new apps (#21704) * chore: remove setup.py requirements.txt boilerplate * feat(DX): PEP517 compatible builds on new apps closes #21612 (cherry picked from commit 8436f77) # Conflicts: # frappe/utils/boilerplate.py * chore: resolve conflicts --------- Co-authored-by: Ankush Menat <ankush@frappe.io> Co-authored-by: barredterra <14891507+barredterra@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
frappe/frappe/utils/boilerplate.py
Lines 135 to 136 in cb156b6
Since the workarround has been removed there is no more work around.
Solution: move to
flit
(as infrappe
proper)Impact:
Community modules can't be built from read-only sources, throwing the following error:
The text was updated successfully, but these errors were encountered: