Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

Hi, It looks to me like this has introduced a slight behaviour difference with 1.11 on python 2.7 than on 3.x: https://github.com/django/django/commit/f4cff43bf921fcea6a29b726eb66767f67753fa2#diff-e840e362abe9e625eee52d91897400bdR36 The release notes don't indicate what the difference in

Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

I've been looking in more detail into this issue, as some other Django packages are affected also by this issue. Now, when I run the tests that are provided with this fix using SQLite, the issue does not occur, whereas it does happen for PostgreSQL (I haven't tested for MySQL). Is it correct

Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

Django developers, We use Django 2.1 and anyway I saw that Django expects each user to have one email address, where on Speedy Net each user can have multiple email addresses. So I had to override *def save* in *class PasswordResetForm* on Speedy Net:

Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

Thanks for checking and asking! On Python 2, the email address with "i without dot" isn't a valid email address according to the EmailValidator and thus shouldn't be in your database in the first place. Cheers, /Markus On Wed, Dec 18, 2019, at 11:23 AM, Sam Willis wrote: > Hi, > > It looks

Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

HI Dirk. You're correct, the issue doesn't appear to arise on SQLite. Pass on exactly why right now. Maybe there's some PostgreSQL setting that might avoid it but, in general, it's not dependent on specific PostgreSQL settings. Kind Regards, Carlton On Wednesday, 18 December 2019

Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

SQLite's only does an exact match, so it's not affected by Unicode Case Mapping Collisions. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from

Re: Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

This depends on the collation that is used . On a system sorting everything as if it was Turkish, "ı" and "i" would be considered two different letters, but I guess everywhere else they would be merged into "i". On Wed, 18 Dec 2019 at

Automatic admins registration

Hello to everyone, # This non-trivial patch improve Django functionality # by providing automatic registration in main admin.py # of all admin files of the project admin.py module code # admin.py import importlib from django.contrib import admin from django.apps import apps #

Re: Automatic admins registration

Hi Vladimir Posting code to this mailing list is the wrong way to try make contributions. Thanks for offering though. Please read the guides at https://docs.djangoproject.com/en/dev/internals/contributing/ for how to post tickets and code. However from a quick skim I'm not sure your code is

Django security releases issued: 3.0.1, 2.2.9, and 1.11.27

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and

Re: Automatic admins registration

среда, 18 декабря 2019 г., 19:46:18 UTC+3 пользователь Adam Johnson написал: > > Hi Vladimir > > Posting code to this mailing list is the wrong way to try make > contributions. Thanks for offering though. > > Please read the guides at >

Re: Sounding out for GSoC 2020.

> > This year was interesting. Sage in particular did well putting together a > cross-db JSONField, but he was probably under-mentored, > since Mariusz has spent quite a bit of time reworking the PR, and still > has a bit to go, before we can pull it in, hopefully for 3.1 > > So, one consideration

Re: Sounding out for GSoC 2020.

Thank you for the kind comments! I see some very interesting ideas here. I haven't been able to come up with a good idea, but I can give a hand as a mentor next year, so I thought I'd join on this conversation :) Andrew, I think the Django Case Studies will be a great idea for Season of Docs