manage.py makemessages anlalyses lib/python in virtualenv

[g1234@…]

When working with virtualenv to develop django application there is the lib subdirectory under the project root with the whole django installation.

python manage.py makemessages --all

will recurse into all subdirectories under the project root and also into the lib subdirectory. Because of this it will try to generate .po files for all messages in the whole django installation, not only in the project or app developed.

It takes very long to generate all those messages, even worse it breaks the run because of errormesseges from makemessages. Also it makes very big .po files with alot of messages to translate.

It at least should be optional to scan apps outside the project.

Workaround: Move the lib and the local subdirectories out of the way before running ./manage.py makemessages. For example mv lib ..; mv local ..; But then the hole django installation is not working any more. This workaround is working only if the developing computer has also a python and django installation in the /usr path which than can do the makemessages. Probably that is a different version of python and/or django than the one in the virtualenv.

[Simon Charette]

There's an --ignore ​option just for that.

Please use ​support channels prior to report a bug next time.

By the way you should maybe consider moving re-thinking project layout, you can probably get insights on ​#django.

[Aymeric Augustin]

Yes, you shouldn't be running makemessages for within your virtualenv; it isn't an appropriate location for your application code.