Tests failing on postgres 9.6

Hi, I'm having troubles with a couple of tests on postgres 9.6. I've created a ticket here: https://code.djangoproject.com/ticket/28234 Because Jenkins is still on 9.5 I would appreciate if someone could try to reproduce it on their setup with 9.6. Thanks. André Ericson -- You received

Re: [JOB POST] Django backend developer per Centre Comune di Ricerca - JRC

(Django-users is a better place for job postings: https://groups.google.com/d/forum/django-users ) On Tue, May 23, 2017 at 5:17 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hello Jorge, > > Job postings are inappropriate on this mailing list. > > Thanks for your

Re: [JOB POST] Django backend developer per Centre Comune di Ricerca - JRC

Hello Jorge, Job postings are inappropriate on this mailing list. Thanks for your understanding, -- Aymeric. > On 23 May 2017, at 14:54, Jorge Lopez wrote: > > We are looking for an experienced Python-Django developer, for a consulting > activity at the

Re: Review of DEP 201 - simplified routing syntax

Huzzah! Looking forward to the new syntax landing. On Sunday, May 21, 2017 at 2:56:13 AM UTC-5, Aymeric Augustin wrote: > > Hello, > > The technical board accepted DEP 201: > https://github.com/django/deps/blob/master/accepted/0201-simplified-routing-syntax.rst > > Sjoerd has taken the lead on

Re: Pre-DEP: Meta.without_primary_key (related to CompositeFields)

Hi Shai, Thanks for your feedback. Our 'real' use case, is we have an opaque legacy application that we are rewriting in Django. Adding columns to the tables before we have migrated it away from the old application is too risky to do. I'm at the PyCon2017 sprins now, and as JKM said it --

[JOB POST] Django backend developer per Centre Comune di Ricerca - JRC

We are looking for an experienced Python-Django developer, for a consulting activity at the Joint Research Centre, Ispra site, in the area of Forest management. If you are interested, please contact Mr. Matteo Villa - matteo.vi...@finconsgroup.com -- You received this message because you

Re: Pre-DEP: Meta.without_primary_key (related to CompositeFields)

Hi, Thank you for making this suggestion. It is my guess that allowing pk-less models will place quite a burden on many parts of Django, which assume a PK exists. There may also be other solutions to the problem you raise -- e.g. changing the legacy table to add a PK, perhaps while providing