py2app doesn't support egg metadata

py2app currently doesn't look at egg metadata at all, and therefore doesn't copy that metadata into the resulting application/plugin bundles.

This means that applications or libraries that use egg metadata (such as entry-points) won't work in an bundle created by py2app

Thank you for looking into this. I think this was one of my main problems trying to use PyOpenGL with Pastels (http://code.google.com/p/pastels/ ).

Later, Blake.

For what it's worth, this bug caused us hours of headaches today on Mimic when our mac app build started failing due to testtools introducing a runtime dependency on egg metadata.

For now we will likely stick with old versions of testtools or abandon it, but it was a bit sad that a 5-year-old bug triggered this headache.

It is a 5 year old feature request, not a bug.

@Ronald Oussoren - I just ran into the issue that py2app doesn't support entry points, which I am using to implement plugin support for http://www.glueviz.org. I was wondering whether you have any ideas for how to proceed with the implementation to support this (in py2app), or whether you have suggestions for working around this?

My current plan is to add two features:

1) Provide a switch to include entire PyPI packages

2) Add a mapping from module names to PyPI packages (using egg metadata)

With this information py2app can then copy the metadata for all PyPI packages that are (partially) used to the right location inside the app bundle.