Changes between Version 11 and Version 12 of Python

Timestamp:

Dec 16, 2022, 10:30:41 AM (16 months ago)

Author:

jmroot (Joshua Root)

Comment:

clarify

Python

@@ -44 +44 @@
 
 == Version Policy ==
-Ports should attempt to support the latest stable version of Python, and should generally avoid using Python versions that are no longer receiving upstream updates (a.k.a. "end-of-life"), unless it is impossible to use a newer version for some reason. As always, no port should be removed without first ensuring it has no remaining dependents (remember that this applies recursively), and the permission of relevant maintainers should be obtained. Port maintainers may extend support for older Python versions at their discretion.
+Module ports should attempt to support the latest stable version of Python, and should generally avoid using Python versions that are no longer receiving upstream updates (a.k.a. "end-of-life"), unless it is impossible to use a newer version for some reason. As always, no port should be removed without first ensuring it has no remaining dependents (remember that this applies recursively), and the permission of relevant maintainers should be obtained. Port maintainers may extend support for older Python versions at their discretion.
 
-Ports that support multiple versions of Python should use the same version by default as the python portgroup. This version is updated to the latest stable release of Python as of the 1st of January each year.
+Ports that support multiple versions of Python should use the same version by default as the python portgroup. This version is updated to the latest stable release of Python as of the 1st of January each year. Ports that use a single Python version should use this version if possible.
 
 End-of-life Python versions should include the deprecated portgroup so that users know they are EOL and can make an informed decision whether to continue using them.