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

Fix zope_interface and add python3 compatibility #1677

Merged
merged 1 commit into from
Feb 5, 2019

Conversation

opacam
Copy link
Member

@opacam opacam commented Feb 5, 2019

The zope.interface module lacks of the __init__.py file in one of his folders, that leads into:

ImportError: No module named zope.interface

@KeyWeeUsr
Copy link
Contributor

Perhaps a better idea would be to just create an empty patch for that file, so that we don't do more tricky stuff within the recipe. If/after they fix it, we will get a conflict for applying patch and will know that everything is ok on their side.

@opacam
Copy link
Member Author

opacam commented Feb 5, 2019

Oh yes, @KeyWeeUsr, a lot better with a patch, thanks!!
😄

@opacam opacam changed the title Fix zope_interface and add python3 compatibility [WIP] Fix zope_interface and add python3 compatibility Feb 5, 2019
The `zope.interface` module lacks of the __init__.py file in one of his folders, that leads into an ImportError: No module named zope.interface
@36Boxes
Copy link

36Boxes commented Feb 5, 2019

Tried this patch with python2 and it worked for me!

@opacam opacam changed the title [WIP] Fix zope_interface and add python3 compatibility Fix zope_interface and add python3 compatibility Feb 5, 2019
# Here we intentionally apply a patch to solve that, so, in case that
# this is solved in the future an error will be triggered
zope_install = join(self.ctx.get_site_packages_dir(arch.arch), 'zope')
self.apply_patch('fix-init.patch', arch.arch, build_dir=zope_install)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor: I'm not sure I understand why we're applying the patch that way rather than adding it to the patches list?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because the patch is apllied into the site-packages directory after the installation is made.
The patches are applied before the installation...and if you check the source code of zope.interface, you will se that the __init__.py file is in there, but when we install the package the file isn't installed...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ahah fun, thanks for the explanation!
Then is it not the manifest file or something like that we want to fix with a patch?
I mean the way you did seems fine, I'm just challenging to see if there're no better ways

Copy link
Member

@AndreMiras AndreMiras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@AndreMiras AndreMiras merged commit 9efee20 into kivy:master Feb 5, 2019
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

Successfully merging this pull request may close these issues.

4 participants