Re: Please don't kill the ecosystem

Hi Pkl, On Monday, September 1, 2014 10:45:30 PM UTC+2, Pkl wrote: > > In random order, I stumbled upon: > - removal of django.conf.urls.defaults > - removal of markup contrib lib (adios built-in RST support) > - removal of request.raw_post_data (thus breaking about all existing > webservice libs

Re: Please don't kill the ecosystem

Hello, While I generally agree with what other core devs have said regarding the examples you raised, I still find your feedback interesting because it reminds us that we iterate too quickly for at least some parts of the community. It's unavoidable that some people will find the pace of Django's

Re: Please don't kill the ecosystem

With as many new frameworks as there are out there, with the gains in popularity seen in Go and Node, my thinking is, move quickly, break (some very small) things, or die slowly. As was said, if your favorite lib doesn't work with 1.6 or 1.7, either use a prior version, or spend some time contri

Re: Please don't kill the ecosystem

On Mon, Sep 1, 2014 at 9:45 PM, Pkl wrote: > > Hello, > > I once was once lured to an ideal of long-term stability and > retrocompatibility, by nice docs like this one : > https://docs.djangoproject.com/en/dev/misc/api-stability/ > > But for some years, stuffs have actually been getting worse and

Re: Please don't kill the ecosystem

2014-09-02 15:33 GMT+02:00 Tom Evans : > this story was scored > at 8 points, it took a junior developer much longer than 8 points and > wasn't finished in a single sprint - and 1.3->1.4 was *easy* > I don't know how much a point or a sprint is worth in this context :-/ I know that upgrading is

Re: Please don't kill the ecosystem

Pkl, You shouldn't have to upgrade all your old sites to the latest version of Django, unless you want maintain current methods. This is why we like virtual environments, much. The core team has made a nice set of security releases available via pip. Django 1.4.14, Django 1.5.9, Django 1.6.

@load_fixture annotation for test cases.

Hello, I thought it might be pretty helpful if there was a load_fixtures annotation that loads fixture for a specific test method in TransactionTestCase. On some occasions, it might be pretty hard to test a model/view that uses only one or a few fixtures that are always the same. Here are some o

Re: Setting dictionaries (was Re: integrating django-secure)

Hi Shai, On 09/01/2014 01:15 AM, Shai Berger wrote: > This thread has had very little to do with django-secure for some time... Thanks :-) > On Sunday 31 August 2014 18:07:04 Carl Meyer wrote: >> >> In the case of the email settings, I think introducing a deprecation >> that requires people to u

Re: integrating django-secure

On 09/01/2014 11:31 AM, Erik Romijn wrote: [snip] > So, although I encourage anyone to enable HSTS, we should not recommend > people to just "switch it on". They should be well aware of the > consequences as it can affect an unknown set of users beyond their > Django site, long after the change has

Re: integrating django-secure

On 09/01/2014 02:34 PM, Michael Manfre wrote: > On Mon, Sep 1, 2014 at 2:12 PM, Aymeric Augustin > > wrote: > > If we recommend HSTS, we need visible warnings and a small duration > in examples, for people who copy-paste without reading. > > >

Re: [ANN] django-synth, a bridge to Synth's C++ template engines

On Sunday, August 31, 2014 10:43:48 PM UTC+2, Aymeric Augustin wrote: > > If you look at the first email in this thread, you’ll see that > django_synth provides its own template loader. > > Sure it does, but does that mean I can do this? TEMPLATE_LOADERS = ( ('django.template.loaders.cached.

[ANNOUNCE] Django 1.7 released

Django 1.7 is now available: https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/ Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5 release is the final releae in the 1.5 series, as Django 1.5 has now reached end-of-life. -- You received this message because

Re: [ANNOUNCE] Django 1.7 released

congratulations!!! And thank you for a really good job! Best Regards On Tue, Sep 2, 2014 at 4:13 PM, James Bennett wrote: > Django 1.7 is now available: > > https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/ > > Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugf

Re: [ANNOUNCE] Django 1.7 released

Awesome! Thanks! 2014-09-03 0:15 GMT+02:00 Carlos Aguilar : > congratulations!!! > > And thank you for a really good job! > > Best Regards > > > On Tue, Sep 2, 2014 at 4:13 PM, James Bennett > wrote: > >> Django 1.7 is now available: >> >> https://www.djangoproject.com/weblog/2014/sep/02/releas

Re: [ANNOUNCE] Django 1.7 released

That's good news! On Sep 2, 2014 7:13 PM, "James Bennett" wrote: > Django 1.7 is now available: > > https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/ > > Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5 > release is the final releae in the 1.5 series, as Dj

Re: @load_fixture annotation for test cases.

The idea isn't bad, except that the performance of fixture loading is pretty terrible in general. Take a look at ticket https://code.djangoproject.com/ticket/20392 for some performance profiling and discussion. As far as I'm concerned, using fixtures is the wrong way to populate data for tests