There's not much to this, really, except what's in the subject line of this
message.

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.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAL13Cg-Y8OXrJvF%2BeXof9v0uBKCJ76owqH4dMzrShVKwVoLxUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to