Talk:Python package policies

From Alpine Linux
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This page duplicates quite a bit of details which are already present:

Instead of creating a new page the existing information should be updated.


`_py2_depends` and `_py3_depends` are more consistent with the other variable names and preferable to '_py2_deps' and '_py3_deps' in my opinion.

Agreed, but I've removed all of the Python 2 details entirely pending the coming EoL. --Ddevault (talk) 15:10, 24 January 2020 (UTC)



_pyname is much less common than _pkgname although _pkgname is used for many things; would be good to have a clear recommended name

_pyname was per ncopa's suggestion, I don't have a problem with it. --Ddevault (talk) 15:10, 24 January 2020 (UTC)

my only issue with _pyname is that it is less common; I agree _pkgname is more common and longer term consistency would be good, we had a discussion about it today on IRC; the consensus there is that it is a private variable and the name doesn't matter. --Keith.maxwell (talk) 09:25, 12 April 2020 (UTC)

a good argument for _pyname from IRC is that "More descriptive names are preferable, _pkgname doesn't really tell much" Keith.maxwell (talk) 09:38, 12 April 2020 (UTC)