Today marks one month until the scheduled alpha/feature freeze for 1.8. As
far as I can tell, we are making good progress on the remaining major
features that we hope to land for 1.8 (model meta refactor, multiple
template engines, contrib.postgres).
I wanted to highlight the patch from Thoma
I haven't used external authentication backends for any projects, but I
still think the concept of dynamically changing how the password change
form/views work based on which backend you authenticated with is too much
complexity. This scheme feels very brittle and I'm not sure that making
this
Thanks! It's open: https://code.djangoproject.com/ticket/23985
On Fri, Dec 12, 2014 at 12:12 PM, Michael Manfre wrote:
> Please open a ticket for this.
>
> On Fri, Dec 12, 2014 at 9:11 AM, Bruno Ribeiro da Silva <
> bruno.dev...@gmail.com> wrote:
>
>> Hey everyone,
>>
>> I just found out that th
Please open a ticket for this.
On Fri, Dec 12, 2014 at 9:11 AM, Bruno Ribeiro da Silva <
bruno.dev...@gmail.com> wrote:
> Hey everyone,
>
> I just found out that the new schemes option of URLValidator causes
> incompatible changes for people who were using custom regex to restrict
> schemes. Coul
Hey everyone,
I just found out that the new schemes option of URLValidator causes
incompatible changes for people who were using custom regex to restrict
schemes. Could somebody put a note in Django 1.7 backward incompatible
changes documentation? Should I open a ticket for this?
Thanks!
--
Bru
