zope.configuration failure to find dependency
See original GitHub issueWhile trying to upgrade zope.configuration for Nixos, I found this problem, which sounds similar to:
https://github.com/pypa/setuptools/issues/870
I tried already with Setuptools 32.3.1, but the result is the same. This is not Nix specific, but happens also in a normal Python3.6 virtualenv
======================================================================
ERROR: test_wo_parents (zope.configuration.tests.test_docutils.Test_makeDocStructures)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/zope.configuration/src/zope/configuration/tests/test_docutils.py", line 61, in test_wo_parents
from zope.interface import Interface
ModuleNotFoundError: No module named 'zope.interface'
----------------------------------------------------------------------
Ran 252 tests in 0.195s
FAILED (errors=229)
Test failed: <unittest.runner.TextTestResult run=252 errors=229 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=252 errors=229 failures=0>
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:20 (14 by maintainers)
Top Results From Across the Web
Python Dependency satisfied but pip still complains for zope ...
It appears that zope.interface<5.0.0 relies on a deprecated API from setuptools , so pip throws away the matching distribution once it ...
Read more >Configuring and Running Zope — Zope 5.7.3 documentation
Once you've installed Zope, you will need to create an “instance home”. This is a directory that contains configuration and data for a...
Read more >zope.configuration - PyPI
Fix the domain of MessageID fields to be a native string. Previously on Python 3 they were bytes, which meant that they couldn't...
Read more >Working Installation Documentation - Plone Community
7 for Zope/Plone requirements.... Failed: We need to be able to use Python.h, which is missing. You may be able to resolve this...
Read more >Zope - Python Package Health Analysis | Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages. License: ZPL-2.1. Security Policy: No.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So I encountered this too and my impression as to why this is failing is that it’s because the namespace package’s
__path__
ends up being aimportlib._bootstrap_external._NamespacePath
object with Python 3.5 and 3.6 and there is anisinstance(path, list)
in pkg_resources at https://github.com/pypa/setuptools/blob/master/pkg_resources/__init__.py#L2128 that prevents the__path__
being modified in some way that seems to be important (my guess is that it means theif _normalize_cached(item)==normalized:
condition in file_ns_handler never fires, but I’m waaaaay past the point where I understand what’s going on now).In Nixpkgs we recently changed the way we install
setuptools
from egg to wheel. All packages, includingsetuptools
are explicitly onPYTHONPATH
during installation. Importing namespace packages such as zope however fails in case of Python 2.