Allow Django to be packaged as a Python egg

[sil@…]

This patch allows Django to be packaged as a ​Python egg file. This means that you can download the Django source and build an egg file with "python setup.py bdist_egg", and that egg contains all of Django and can be dropped onto sys.path and used like other eggs. In particular, this makes it easier to use Django when you don't want to install it into your Python directory (either with "setup.py install" or with a symlink).

This patch incorporates some code from ticket #582.

[sil@…]

Better patch: ignore previous one

[sil@…]

Changed the patch so that it doesn't break every existing Django project. :-) Using an egg-based Django will require editing of settings/admin.py to make ADMIN_TEMPLATE_PATH be a path that includes the .egg file. Create a new project with an egg-based Django and examine settings/admin.py to see what is meant here.

This patch could do with some testing.

[Adrian Holovaty]

Stuart (or somebody else) -- When you use Django as an egg, how do you access django-admin.py?

[sil@…]

You have to copy django-admin.py out of the egg. I haven't come up with a good solution to this yet :( The TurboGears people have setuptools *create* their tg-admin.py, which might be an acceptable solution.

[danlipsitt@…]

Can this be done with ​setuptools automatic script creation?

[Adrian Holovaty]

(In [1010]) Improved autoreloader to ignore files that might be in eggs. Refs #596

[Adrian Holovaty]

At this point, all we need to do is apply the patches to django/core/servers/basehttp.py and django/core/management.py.

[hugo]

What still would be open (after the i18n merge) would be handling of the .po/.mo files. Currently they are expected only in the filesystem (either application, project or django-wide), not in eggs. Since I don't have an egged environment for python running, it would be better if somebody who knows eggs could look into that. The problem is that gettext.find() searches for translations and I don't think that it will take eggs into consideration (and the behaviour of gettext.find itself isn't driven by something subclasseable, at least not IIRC).

Maybe the egg patching could wait until after the i18n merge, so that we have some time to check into this and provide a patch?

[Gary Wilson <gary.wilson@…>]

0.91 has come and gone.

[(none)]

Milestone Version 1.0 deleted

[James Bennett]

Django dropped setuptools support (for Django itself) some time ago due to maintenance headaches; marking wontfix because of that.

[anonymous]

could you specify what caused the maintenance headaches?

[Jannis Leidel]

sorry, the question came from me :)

[Malcolm Tredinnick]

Please ask support questions on the mailing list, rather than in Trac. Thanks.

[bhuztez]

add support for PEP 302 importers should fix this.
some related tickets #294 #8238 #8280 #12206 #13334 #13587 #14087 #16718 #17331

I will move zip_egg_fixed patch here from #14087 and add PEP 302 importers support to the following components

• templates
• fixtures
• static files
• translations
• django.db.utils.load_backend

[bhuztez]

zip_egg_fixed.5.diff from #14087

[bhuztez]

add pep-302 importers support for template

[bhuztez]

django.db.utils.load_backend

[bhuztez]

translation files

[bhuztez]

update for revision 17868

[bhuztez]

I am going to separate patch into three, because they are three different problems.

• Django will try not to import any app when finding management commands, thus we have to make assumption on (pseudo-)filesystem layout on app modules.
• Django will import app before finding templates, fixtures, static files and locale files, and will skip some of the apps if a specific directory under app path does not exist.

django.db.utils.load_backend will be maintained under #8238. management commands from PEP-302 importers will be under #8280. Others will be remained here.

[bhuztez]

only templates and translation files

[bhuztez]

the resource-pep-302 patch focus on loading resources from apps imported by PEP-302 importers

[Jannis Leidel]

Please don't reopen tickets that have been closed for years by core developers. Adding support for PEP 302 import hooks is only slightly related to egg files which to be honest are a no go for me too. Feel free to open a discussion about that on the developer mailing list if you haven't already.

[bhuztez]

Replying to jezdez:

Please don't reopen tickets that have been closed for years by core developers.

I will leaved it closed.

Feel free to open a discussion about that on the developer mailing list if you haven't already.

I did. But got no response unfortunately.