Replies: 2 comments 1 reply
-
|
This appears to also affect |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Which version of setuptools are you using? After upgrading to setuptools 82 I needed to reinstall ckan and its extensions so that the pkgutil path in Lines 7 to 9 in c7effcf I don't know why having a namespace declaration in a submodule would seem to fix the issue, that's really odd. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We're encountering some perplexing behaviour regarding Python namespaces when moving to CKAN 2.11.5, and I'm hoping that someone else will have insights.
We run two sites, with different plugin sets that both include
ckanext-s3filestore, and one works fine on CKAN 2.11.5, while the other crashes when attempting to run any CLI command on 2.11.5, with a stack trace similar to:Investigation showed various workarounds that would resolve it, but we're still scratching our heads about exactly what is happening here.
ckanext/stats/__init__.py, then the error goes away.ckanext/__init__.pydoes not suffice. This appears to be why one of our two sites is working, as it installs ckanext-ytp-comments, ckanext-archiver, ckanext-harvest, and ckanext-datarequests, all of which have that declaration.pysolrto version 3.9.0 (as was used in CKAN 2.11.4), then the error goes away.Removing
__init__.pyfrom ckanext-s3filestore, however, to comply withimportlibstyle, does not help.Does anyone have more insight on what is happening and what is the proper solution to this?
Beta Was this translation helpful? Give feedback.
All reactions