On 21/11/2010, at 10:52 AM, Carl Meyer wrote:
> Hi all,
>
> The special-cased handling of contrib.admin static assets in Django
> core is a long-time wart. Fortunately, the new static assets standard
> introduced by contrib.staticfiles and the STATIC_URL and STATIC_ROOT
Hi all,
I've recently been exploring simple multitenancy options in Django
using contrib.sites, and have some thoughts on how core could make it
easier.
First, let me make a quick distinction between static and dynamic
multitenancy. In the static case, you have a limited set of sites
running on
Hi all,
The special-cased handling of contrib.admin static assets in Django
core is a long-time wart. Fortunately, the new static assets standard
introduced by contrib.staticfiles and the STATIC_URL and STATIC_ROOT
settings finally allows us to begin a migration path to remove this
wart.
On Sun, Nov 21, 2010 at 8:55 AM, hutch_burgopak wrote:
> This is probably a dumb question, but what is the policy on this?
We don't have a specific plan or timeline in mind. Like everything
else in open source, it'll get done when enough people are willing to
devote enough time
This is probably a dumb question, but what is the policy on this? RHEL
for instance is just now releasing version 6, still running python2
from what I read. It will be for about 5 years from what I understand.
I'm sure the Ubuntu LTS version that's supported right now will be the
same. Is it