[Checkins] [zopefoundation/z3c.autoinclude] 4d4820: Adding support for pip.

[GitHub]

  Branch: refs/heads/pip
  Home:   https://github.com/zopefoundation/z3c.autoinclude
  Commit: 4d4820eadf6c973e9fece3ec3e9259dc278d498b
      https://github.com/zopefoundation/z3c.autoinclude/commit/4d4820eadf6c973e9fece3ec3e9259dc278d498b
  Author: Patrick Gerken <patrick.gerken at zumtobelgroup.com>
  Date:   2016-03-25 (Fri, 25 Mar 2016)

  Changed paths:
    M CHANGES.rst
    M src/z3c/autoinclude/dependency.txt
    M src/z3c/autoinclude/plugin.txt
    A src/z3c/autoinclude/tests/A/a/__init__.py
    A src/z3c/autoinclude/tests/A/a/configure.zcml
    A src/z3c/autoinclude/tests/A/setup.py
    R src/z3c/autoinclude/tests/APackage/a/__init__.py
    R src/z3c/autoinclude/tests/APackage/a/configure.zcml
    R src/z3c/autoinclude/tests/APackage/setup.py
    R src/z3c/autoinclude/tests/BCPackage/b/__init__.py
    R src/z3c/autoinclude/tests/BCPackage/b/c/__init__.py
    R src/z3c/autoinclude/tests/BCPackage/b/c/configure.zcml
    R src/z3c/autoinclude/tests/BCPackage/setup.py
    R src/z3c/autoinclude/tests/FooPackage/foo/__init__.py
    R src/z3c/autoinclude/tests/FooPackage/foo/configure.zcml
    R src/z3c/autoinclude/tests/FooPackage/setup.py
    R src/z3c/autoinclude/tests/SiblingPackage/F/G/__init__.py
    R src/z3c/autoinclude/tests/SiblingPackage/F/G/meta.zcml
    R src/z3c/autoinclude/tests/SiblingPackage/F/H/__init__.py
    R src/z3c/autoinclude/tests/SiblingPackage/F/H/configure.zcml
    R src/z3c/autoinclude/tests/SiblingPackage/F/H/meta.zcml
    R src/z3c/autoinclude/tests/SiblingPackage/F/__init__.py
    R src/z3c/autoinclude/tests/SiblingPackage/setup.py
    R src/z3c/autoinclude/tests/XYZPackage/setup.py
    R src/z3c/autoinclude/tests/XYZPackage/x/__init__.py
    R src/z3c/autoinclude/tests/XYZPackage/x/y/__init__.py
    R src/z3c/autoinclude/tests/XYZPackage/x/y/z/__init__.py
    A src/z3c/autoinclude/tests/b.c/b/__init__.py
    A src/z3c/autoinclude/tests/b.c/b/c/__init__.py
    A src/z3c/autoinclude/tests/b.c/b/c/configure.zcml
    A src/z3c/autoinclude/tests/b.c/setup.py
    A src/z3c/autoinclude/tests/base2.plug/base2/__init__.py
    A src/z3c/autoinclude/tests/base2.plug/base2/plug/__init__.py
    A src/z3c/autoinclude/tests/base2.plug/base2/plug/configure.zcml
    A src/z3c/autoinclude/tests/base2.plug/setup.py
    R src/z3c/autoinclude/tests/base2_plug/base2/__init__.py
    R src/z3c/autoinclude/tests/base2_plug/base2/plug/__init__.py
    R src/z3c/autoinclude/tests/base2_plug/base2/plug/configure.zcml
    R src/z3c/autoinclude/tests/base2_plug/setup.py
    A src/z3c/autoinclude/tests/f.g/F/G/__init__.py
    A src/z3c/autoinclude/tests/f.g/F/G/meta.zcml
    A src/z3c/autoinclude/tests/f.g/F/H/__init__.py
    A src/z3c/autoinclude/tests/f.g/F/H/configure.zcml
    A src/z3c/autoinclude/tests/f.g/F/H/meta.zcml
    A src/z3c/autoinclude/tests/f.g/F/__init__.py
    A src/z3c/autoinclude/tests/f.g/setup.py
    A src/z3c/autoinclude/tests/foo/foo/__init__.py
    A src/z3c/autoinclude/tests/foo/foo/configure.zcml
    A src/z3c/autoinclude/tests/foo/setup.py
    M src/z3c/autoinclude/tests/tests.py
    A src/z3c/autoinclude/tests/x.y.z/setup.py
    A src/z3c/autoinclude/tests/x.y.z/x/__init__.py
    A src/z3c/autoinclude/tests/x.y.z/x/y/__init__.py
    A src/z3c/autoinclude/tests/x.y.z/x/y/z/__init__.py
    M src/z3c/autoinclude/utils.py
    M src/z3c/autoinclude/utils.txt

  Log Message:
  -----------
  Adding support for pip.

This unfortunately removes support for having package names totally different
from the modules they provide.
This is not an issue with current Plone packages.
There are packages providing modules with different names, ZODB3 comes to mind,
but these packages did not trigger any problems with auto include.

Also, unfortunately, there is no way around it if one wants to support
pip, because pip installs everything in such a way, that all eggs
can share the same sys.path entry. When I see the physical location
of a python module, I cannot see, from which egg this was coming.
This is a breaking change, but it does not affect the consumer Plone
in a negative way. I can't speak for other frameworks using this.