This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author msopacua
Recipients barry, dbzhang800, eric.snow, msopacua, ncoghlan, palm.kevin, pitrou, srid, steve.dower, tarek, vstinner
Date 2016-09-12.14:09:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The cause for this error is any cause for not being able to load a module. This includes version conflicts, so when trying to load a virtualenv with python 3.3 interpreter by a uWSGI embedded python3.4 interpreter the action fails.

This is - bluntly overstated - a design flaw or overly confident claim with respect to virtualenv support in uWSGI. This configuration can never work and becomes a configuration error.

It really deserves a less generic error message, indicating the version conflict and possibly the path to the encoding module it tried to load. This helps in debugging the cause and possibly abandon the idea before wading through the list of reports generated by this error message (only one of which I found to hint at the version conflict and most don't have a clear solution or different root cause).
Date User Action Args
2016-09-12 14:09:01msopacuasetrecipients: + msopacua, barry, ncoghlan, pitrou, vstinner, tarek, srid, palm.kevin, eric.snow, dbzhang800, steve.dower
2016-09-12 14:09:01msopacuasetmessageid: <>
2016-09-12 14:09:01msopacualinkissue11320 messages
2016-09-12 14:09:00msopacuacreate