Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

version 4.3.3 breaks py2app #67

Closed
glyph opened this issue Dec 14, 2016 · 7 comments
Closed

version 4.3.3 breaks py2app #67

glyph opened this issue Dec 14, 2016 · 7 comments

Comments

@glyph
Copy link

glyph commented Dec 14, 2016

We began seeing this in Mimic in this PR: rackerlabs/mimic#700.

@glyph
Copy link
Author

glyph commented Dec 14, 2016

@tseaver
Copy link
Member

tseaver commented Dec 14, 2016

@glyph Thanks for the report. If the issue is to do with namespace packages, there is a currently-in-work setuptools issue which may be the source of the problem.

@glyph
Copy link
Author

glyph commented Dec 14, 2016

@tseaver Thanks for the reply. I suspect that is the issue, although I don't know why it would have changed between 4.3.2 and 4.3.3. Any chance we can drop the 'zope' and just make this 'interface' or 'interfaces'? :) In addition to avoiding the perpetual complexity annoyances of dealing with NS packages (this is not the first time it's broken our mac app build) it would also be a PR coup :).

@tseaver
Copy link
Member

tseaver commented Dec 16, 2016

@glyph All renaming aside, did the setuptools 31.0.1 release fix your py2app build?

@glyph
Copy link
Author

glyph commented Dec 16, 2016

We landed a workaround immediately afterwards, and we haven't removed it yet. However, we have upgraded setuptools, so we could try a PR that removes it...

@jamadden
Copy link
Member

jamadden commented Feb 6, 2020

Closing because the upstream issue seems solved and there have been no updates on this for a few years.

@jamadden jamadden closed this as completed Feb 6, 2020
@glyph
Copy link
Author

glyph commented Feb 7, 2020

Thanks @jamadden ! Ronald's fix did indeed resolve the issue, sorry I didn't follow up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants