Re: Order of INSTALLED_APPS

Aymeric, Ramiro, Florian, thanks a lot for your answers! Indeed there is some (slightly hidden :D ) documentation! And it has improved since 1.5, I now see! - I remembered reading something before, but I couldn't find them anymore when I wrote yesterday's message. My proposal would then be to

Re: Order of INSTALLED_APPS

2013/8/13 Stefano Crosta > My proposal would then be to simply add another box to the > https://docs.djangoproject.com/en/dev/ref/settings/#installed-apps to say > "order matters" once more and link the other two pages for translations and > templates. > *if you think this would* help I could do

Re: Deprecation a little harsh?

On Tue, Aug 13, 2013 at 1:37 AM, Chris Wilson wrote: > I would love to see support extended for a bit longer after deprecation. This is a matter of resources; we struggle to maintain security releases against 3 simultaneous releases (e.g. right now 1.4.x, 1.5.x, and the up-coming 1.6). Adding a

Re: Deprecation a little harsh?

On Tue, Aug 13, 2013 at 9:22 AM, Jacob Kaplan-Moss wrote: > > >> We have apps in production running Django 1.3. There won't be any >> security fixes. If there's a critical vulnerability, we may have to do a >> lot of unpaid work to either backport the fix, > > > I have to say I find this kinda hil

Re: Deprecation a little harsh?

I'm sorry; I was snarkier and nastier than I should have been (and than I intended to be). Thanks for calling me on it; I'll try to do better next time. Jacob On Tue, Aug 13, 2013 at 10:03 AM, Andre Terra wrote: > On Tue, Aug 13, 2013 at 9:22 AM, Jacob Kaplan-Moss wrote: > >> >> >>> We have ap

Re: Deprecation a little harsh?

If there is interest in the community to backport security fixes to no longer supported versions of Django, what is the likelihood that a core dev would merge them in to the appropriate stable branch? This would not include packaging an official release, but would provide a way for those stuck on o

Re: Deprecation a little harsh?

On Aug 13, 2013, at 11:34 AM, Michael Manfre wrote: > If there is interest in the community to backport security fixes to no longer > supported versions of Django, what is the likelihood that a core dev would > merge them in to the appropriate stable branch? This would not include > packaging

Re: Deprecation a little harsh?

Hi Not sure if this is useful, but I thought it might be helpful to throw my perspective as someone who has built four sites with Django (two of which are public, and one of those has to be HIPAA compliant). I will update to dot releases after the main release to give the main release time to s

Re: Deprecation a little harsh?

Hi François, On Tuesday, August 13, 2013 5:46:10 PM UTC+2, François Schiettecatte wrote: > > I have done 1.3.x -> 1.4.x -> 1.5.x and they have all been painless, each > migration taking less than 1/2 day. Point being that back-porting is not > something I would ever need. > It's good to hear t

[ANNOUNCE] Security releases issued (1.4.6, 1.5.2, 1.6b2)

Hi folks -- Today the Django team is issuing multiple releases -- Django 1.4.6, Django 1.5.2, and Django 1.6 beta 2 -- as part of our security process. These releases address two cross-site scripting (XSS) vulnerabilities: one in a widget used by Django's admin interface, and one in a utility func

Re: Deprecation a little harsh?

Florian Here are wc -l line counts: Project 1 .py 28574 .html 16967 (this is a little misleading because we don't use model.py but a separate REST API to handle all the storage) Project 2 .py 43199 .html 91804 Project 3 .py 32441 .html 86684 Cheers François On Aug 13, 2013, at 12:31 PM,

Usage and documentation of F()

I noticed while looking for material for that mentions that: product.number_sold = F('number_sold') + 1 is faster than: product.num

Re: #20739 - Making LiveServerTestCase not depend on staticfiles?

On Mon, Jul 15, 2013 at 1:16 PM, Ramiro Morales wrote: > [...] > > I will be working further on the PR keeping all this design advice in > mind. Guys, I've updated the PR with further work on this: https://github.com/django/django/pull/1354 Any feedback is welcome. Thanks, -- Ramiro Morale

Re: Deprecation a little harsh?

Hi, We've been able to do quite painless upgrades to our software as well. Considering that we started with Django 1.1, stuck quite while at 1.3 and recently we did upgrade to 1.5 Most notable change was {% url %} tag, but nothing really major. Though we don't use many external libs - we've b