Re: 1.9 release planning

On Tuesday, April 7, 2015 at 2:31:08 PM UTC-4, Asif Saifuddin wrote: > > How about > > a 8 month release cycle and having a LTS in every two years and supporting > the old LTS atleast 3 years from the release date? there will be 3 version > between two LTS. > Interesting. I like the idea of havi

Re: 1.9 release planning

How about a 8 month release cycle and having a LTS in every two years and supporting the old LTS atleast 3 years from the release date? there will be 3 version between two LTS. On Thursday, March 12, 2015 at 6:13:11 AM UTC+6, Tim Graham wrote: > > With the release of 1.8 coming up, it's time to

Re: Django Admin New Look

2015-04-07 17:25 GMT+02:00 Marc Tamlyn : > The primary questions to establish answers to before a possible merge in > my opinion are: > - Do we ship both, or just the new one and release the old one as a third > party package? > I'd like to make the new theme the default unless the developer opts

Re: Django Admin New Look

We would modify our base admin template when we merge it. There are a number of third party applications which provide modified versions of their admin pages (FeinCMS is a good example of a moderately complex one). They would normally support two versions of Django (maybe also an LTS now), and so w

Re: Django Admin New Look

On Tuesday, 7 April 2015 20:23:28 UTC+5, Collin Anderson wrote: > > There's a ticket about icons here: > https://code.djangoproject.com/ticket/20597 > Thanks Collin. On Tuesday, 7 April 2015 20:25:57 UTC+5, Marc Tamlyn wrote: > > The primary questions to establish answers to before a possible

Re: Django Admin New Look

Django's master is the correct branch for 1.9 development now. Flat icons would be good, and I agree personally with your earlier suggestion to use font awesome icons. I do think this is a separate issue we could add later. The primary questions to establish answers to before a possible merge in

Re: Django Admin New Look

There's a ticket about icons here: https://code.djangoproject.com/ticket/20597 On Tuesday, April 7, 2015 at 11:16:42 AM UTC-4, elky wrote: > > Hi everyone. As you can see there is less activity now in this thread. > With the latest 0.9.3 release I just think CSS work is over until anyone > repo

Re: Django Admin New Look

Hi everyone. As you can see there is less activity now in this thread. With the latest 0.9.3 release I just think CSS work is over until anyone report a bug or suggestion to improvement. There is big interest from the community: - 1736 downloads in the last month from PyPi

Re: render_to_response in Django 1.8 missing a request parameter?

Hi Stephen, The only difference between render_to_response and render is that render_to_response doesn't know about the current request while render does. If you were using: response = render_to_response('some_template.html', {'foo': 'bar'}, RequestContext(request)) Now you should use: respons

Re: render_to_response in Django 1.8 missing a request parameter?

The purpose of render_to_response is "render without a request context" now as far as I can tell. There are reasons why you would do this, whether they justify the existence of the shortcut is another question. On 7 April 2015 at 11:37, Stephen Brooks wrote: > In that case the render_to_response

Re: render_to_response in Django 1.8 missing a request parameter?

In that case the render_to_response shortcut has little value and should probably be removed in Django 2.0 ?? On Tuesday, 7 April 2015 11:31:24 UTC+1, Marc Tamlyn wrote: > > This is probably a slight error in the documentation, however what you > really want to use is the `render()` function whe

Re: 1.9 release planning

On Tuesday, April 7, 2015 at 1:21:20 AM UTC+2, Tim Graham wrote: > > With a 9 month schedule, here is what the future might look like: > > 1.8 - April 2015 > 1.9 - January 2016 > 2.0 - October 2016 > 2.1 - July 2017 (LTS, and might be the last version to support Python 2.7 > since 3 years of LTS

Re: render_to_response in Django 1.8 missing a request parameter?

This is probably a slight error in the documentation, however what you really want to use is the `render()` function when you want a request context. See https://docs.djangoproject.com/en/1.8/topics/http/shortcuts/#render On 7 April 2015 at 11:28, Stephen Brooks wrote: > I note from the release

render_to_response in Django 1.8 missing a request parameter?

I note from the release notes for Django 1.8 https://docs.djangoproject.com/en/1.8/releases/1.8/ the remark under the section: "dictionary and context_instance arguments of rendering functions" (which includes django.shortcuts.render_to_response()) "If you’re passing a Context

Re: 1.9 release planning

This looks like a good plan to me. The main reason for shortening it before as far as I could tell was the lengthy alpha to final process, which hasn't happened this time and hopefully will be rather less frequent in future. Marc On 7 April 2015 at 00:21, Tim Graham wrote: > With a 9 month sche