py2app picking up .git subdir of a package during build
We use py2app extensively at our facility to produce self contained .app packages for easy internal deployment without dependency issues. Something I noticed recently, and have no idea how it began, is that when building an .app, py2app started including the .git directory of our main library.

commonLib, for instance, is our root python library package, which is a git repo. Under this package are the various subpackages such as database, utility, etc.

    commonLib/
        |- .git/ # because commonLib is a git repo
        |- __init__.py
        |- database/
            |- __init__.py
        |- utility/
            |- __init__.py
        # ... etc

In a given project, say Foo, we will do imports like `from commonLib import xyz` to use our common packages. Building via py2app looks something like: `python setup.py py2app`

So the recent issue I am seeing is that when building an app for project Foo, I will see it include everything in commonLib/.git/ into the app, which is extra bloat. py2app has an excludes option but that only seems to be for python modules. I cant quite figure out what it would take to exclude the .git subdir, or in fact, what is causing it to be included in the first place.

Has anyone experienced this when using a python package import that is a git repo?
Nothing has changed in our setup.py files for each project, and commonLib has always been a git repo. So the only thing I can think of being a variable is the version of py2app and its deps which have obviously been  upgraded over time.
py2app picking up .git subdir of a package during build
===

We use py2app extensively at our facility to produce self contained .app packages for easy internal deployment without dependency issues. Something I noticed recently, and have no idea how it began, is that when building an .app, py2app started including the .git directory of our main library.

commonLib, for instance, is our root python library package, which is a git repo. Under this package are the various subpackages such as database, utility, etc.

    commonLib/
        |- .git/ # because commonLib is a git repo
        |- __init__.py
        |- database/
            |- __init__.py
        |- utility/
            |- __init__.py
        # ... etc

In a given project, say Foo, we will do imports like `from commonLib import xyz` to use our common packages. Building via py2app looks something like: `python setup.py py2app`

So the recent issue I am seeing is that when building an app for project Foo, I will see it include everything in commonLib/.git/ into the app, which is extra bloat. py2app has an excludes option but that only seems to be for python modules. I cant quite figure out what it would take to exclude the .git subdir, or in fact, what is causing it to be included in the first place.

Has anyone experienced this when using a python package import that is a git repo?
Nothing has changed in our setup.py files for each project, and commonLib has always been a git repo. So the only thing I can think of being a variable is the version of py2app and its deps which have obviously been  upgraded over time.