#25120 closed Cleanup/optimization (fixed)
Deprecate template.loaders.eggs.Loader
| Reported by: | Tim Graham | Owned by: | nobody |
|---|---|---|---|
| Component: | Template system | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
James: The problem of providing a single-file, no-build-step format for distributing and installing Python packages has been solved by wheels, and wheels also don't cause the pile of weirdness that comes with using eggs.
So Django should really stop encouraging/supporting the use of eggs. At a minimum, this should involve Django 1.9 starting the deprecation process for the egg template loader, and any other parts of Django which contain special-case workarounds to deal with eggs.
Marc & Preston T: +1
Donald: I’m fine with this, but just be warned that it does mean anything that ships a Django app will need a zip_unsafe=True or else they no longer support being installed with easy_install.
See Deprecating a Feature for the checklist of what needs to be done.
PR