Re: Psycopg2 version support

2015-02-15 Thread Collin Anderson
Right, I think the situation would be if you don't have admin/sudo and the -dev / -devel header files are not present. Seems to me 2.4.5 would be a safe minimum today, but supporting it until 2018 seems a bit excessive. On Sun, Feb 15, 2015 at 7:18 PM, Christophe Pettus wrote: > > On Feb 15, 20

Re: Psycopg2 version support

2015-02-15 Thread Christophe Pettus
On Feb 15, 2015, at 4:14 PM, Tim Graham wrote: > Is there a scenario where you could pip install Django but not pip install > psycopg2? Installing psycopg2 does require development tools, while Django does not. I'm not offering this as a compelling argument for anything, just an observation.

Re: Psycopg2 version support

2015-02-15 Thread Tim Graham
Unless any counter arguments are presented, I suggest let's require psycopg 2.5 for now. Is there a scenario where you could pip install Django but not pip install psycopg2? On Saturday, February 14, 2015 at 5:43:32 PM UTC-5, Shai Berger wrote: > > Hi all, > > On Saturday 14 February 2015 22:53

Re: Drop the TEMPLATE_DEBUG setting

2015-02-15 Thread Enrique Paredes
+1 Last year I do an app to develop templates on the fly granting template_debug dump to some users (designers) and even in that escenario is looking good. Go for it. On Sun, Feb 15, 2015 at 4:42 PM, Marc Tamlyn wrote: > +1 to removing it > On 15 Feb 2015 14:16, "Aymeric Augustin" > wrote: >

Re: Drop the TEMPLATE_DEBUG setting

2015-02-15 Thread Tino de Bruijn
+1, sounds logical to me. On Sun, Feb 15, 2015 at 4:42 PM, Marc Tamlyn wrote: > +1 to removing it > On 15 Feb 2015 14:16, "Aymeric Augustin" < > aymeric.augus...@polytechnique.org> wrote: > >> Hello, >> >> During the multiple template engines refactor, I didn’t touch >> TEMPLATE_DEBUG. >> The on

Re: Drop the TEMPLATE_DEBUG setting

2015-02-15 Thread Marc Tamlyn
+1 to removing it On 15 Feb 2015 14:16, "Aymeric Augustin" wrote: > Hello, > > During the multiple template engines refactor, I didn’t touch > TEMPLATE_DEBUG. > The only purpose of this setting is to control whether Django stores the > information required to display stack traces for exceptions t

Drop the TEMPLATE_DEBUG setting

2015-02-15 Thread Aymeric Augustin
Hello, During the multiple template engines refactor, I didn’t touch TEMPLATE_DEBUG. The only purpose of this setting is to control whether Django stores the information required to display stack traces for exceptions that occur while rendering Django templatse. I think I should have deprecated it