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

ModuleNotFoundError: No module named 'zope.deferredimport' #856

Closed
zopyx opened this issue Jun 29, 2020 · 5 comments
Closed

ModuleNotFoundError: No module named 'zope.deferredimport' #856

zopyx opened this issue Jun 29, 2020 · 5 comments

Comments

@zopyx
Copy link
Member

zopyx commented Jun 29, 2020

In some Plone 5.2 installation I am stuck with this error:

https://community.plone.org/t/modulenotfounderror-no-module-named-zope-deferredimport/12032

In particular, the second import in Zope2 causes the problem

https://community.plone.org/t/modulenotfounderror-no-module-named-zope-deferredimport/12032/4

@dataflake
Copy link
Member

Since there's no information how to recreate your specific setup I have done a quick check with a very simple buildout configuration and cannot reproduce the error, so it appears this is not a Zope issue.

[buildout]
extends =
    https://zopefoundation.github.io/Zope/releases/4.4.4/versions-prod.cfg
parts =
    zopeinstance

[zopeinstance]
recipe = plone.recipe.zope2instance
user = admin:admon
http-address = 127.0.0.1:8088
zodb-temporary-storage = off
eggs =
    Zope

bin/zopeinstance adduser works fine, as does bin/zopeinstance debug etc.

@zopyx
Copy link
Member Author

zopyx commented Jun 29, 2020

It seems to be related (and reproducible) on Debian 9 with its system Python. Seems to work with Debian 9.12...doing further checks.

@dataflake
Copy link
Member

You're really using a system Python for a production system? Wow, living on the edge.

@zopyx
Copy link
Member Author

zopyx commented Jun 29, 2020

You're really using a system Python for a production system? Wow, living on the edge.

For years on all production systems...no longer a problem on Debian or Ubuntu

@zopyx
Copy link
Member Author

zopyx commented Jun 29, 2020

ok, problem solved. This is a side-effect of

zopefoundation/persistent#114

persistent was installed locally in the virtual environment because buildout could not properly build persistent with having TMPDIR set (/tmp is on a mount point). bin/pip install persistent installed zope.interface ...this is where the clash occured.

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

2 participants