Unverified Commit 1060b3dc authored by Filipe Laíns's avatar Filipe Laíns 🌈
Browse files

rfc0010: clarify scope of the proposed changes



Signed-off-by: Filipe Laíns's avatarFilipe Laíns <lains@riseup.net>
parent c2cccf6e
Pipeline #19486 passed with stage
in 11 seconds
============================================= =========================================
Adopt PEP 517 tooling for all Python packages Adopt PEP 517 tooling for Python packages
============================================= =========================================
- Date proposed: 2022-02-19 - Date proposed: 2022-02-19
- RFC MR: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/0010 - RFC MR: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/0010
...@@ -9,7 +9,7 @@ Summary ...@@ -9,7 +9,7 @@ Summary
------- -------
Replace setup.py with PEP 517 tooling (python-build/python-installer) for all Replace setup.py with PEP 517 tooling (python-build/python-installer) for all
Python packages. Python packages where this approach is viable.
Motivation Motivation
---------- ----------
...@@ -52,6 +52,10 @@ with ...@@ -52,6 +52,10 @@ with
You can find more information in the `Python packaging guidelines`_. You can find more information in the `Python packaging guidelines`_.
This would naturally only serve as a general guideline, packages that need an
alternative approach can still do so, but are recommended to stay as close as the
guidelines as reasonably possible.
Drawbacks Drawbacks
--------- ---------
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment