Differences

This shows you the differences between two versions of the page.

--- python:portspolicy [2023/01/13 03:52] – remove confusing leftover before clarifying PyPI or not CharlieLi
+++ python:portspolicy [2023/03/02 02:17] (current) – emphasise case-sensitivity CharlieLi
@@ Line 42: / Line 42: @@
   * If the package is registered on %%PyPI%%
-    * ''%%PORTNAME%%'' MUST **exactly** match the registered %%PyPI%% package name
+    * ''%%PORTNAME%%'' MUST **exactly** match the registered %%PyPI%% package name, **including casing**.
     * The %%PyPI%% package name is that which is displayed in the URL at [[https://pypi.org/]]%%<%%package-name>
     * Note: The displayed %%PyPI%% package name can be different than the package name specified in ''%%setup.py:name%%''
@@ Line 103: / Line 103: @@
 **Guideline**: Use all standard Python ecosystem infrastructure whenever possible.
+==== pep517 ====
+  * Packages following PEP-517 (have a pyproject.toml specifying a build backend that builds an installable wheel) SHALL use pep517, unless there is a compelling reason not to.
+==== distutils ====
+  * Packages that use distutils (directly executes a setup.py, import distutils/setuptools), SHOULD use distutils, unless there is a compelling reason not to.
 ==== autoplist ====
+  * Packages following PEP-517 (have a pyproject.toml specifying a build backend that builds an installable wheel) and built as such SHALL use autoplist.
   * Packages that use distutils (have a setup.py, import distutils/setuptools), SHOULD use autoplist, unless there is a compelling reason not to.
@@ Line 117: / Line 126: @@
 See Also: https://reviews.freebsd.org/D20927#454268
-==== distutils ====
-  * Packages that use distutils (have a setup.py, import distutils/setuptools), SHOULD use distutils, unless there is a compelling reason not to.
 ===== Dependencies =====