[Python-Dev] Keyword meanings [was: Accept just PEP-0426] (original) (raw)

PJ Eby pje at telecommunity.com
Mon Dec 10 17🔞59 CET 2012

On Sun, Dec 9, 2012 at 10:38 PM, Andrew McNabb <amcnabb at mcnabbs.org> wrote:

On Fri, Dec 07, 2012 at 05:02:26PM -0500, PJ Eby wrote:

If the packages have files in conflict, they won't be both installed. If they don't have files in conflict, there's nothing important to be informed of. If one is installing pexpect-u, then one does not need to discover that it is a successor of pexpect. In the specific case of pexpect and pexpect-u, the files don't actually conflict. The pexpect package includes a "pexpect.py" file, while pexpect-u includes a "pexpect/" directory. These conflict, but not in the easily detectable sense.

Excellent! A concrete non-file use case. Setuptools handles this particular scenario by including a list of top-level module or package names, but newer tools ought to look out for this scenario, too.

More information about the Python-Dev mailing list