-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Importing plone.app.testing forces Zope (partly) into production mode due to regression in plone.testing #64
Comments
oh. then the move of the import statement should be reverted with a comment to leave it there. what do you think @datakurre ? |
@thet Yes, I also assume that is the easiest solution. |
@datakurre this is an interesting side effect and makes me rethink doing any import restructures in tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I was wondering, why my pip installed Plone was showing "production mode" even when it was started in foreground mode (
fg
). This was within add-on development setup where the environment also had test packages (so this should never happen in production unless you accidentally include test packages).I traced the issue to this change in plone.testing by @thet where an inline import
from Testing.ZopeTestCase.ZopeLite import _patched as ZOPETESTCASEALERT
was moved with the other imports in file:499e369
Because of that change, importing plone.app.testing has side effect of injecting ZopeLite test configuration into global Zope configuration.
As we see below, plone.app.testing gets imported by z3c.autoinclude when it is looking for includable plugins:
The text was updated successfully, but these errors were encountered: