Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive
Hello, On 1/5/19 10:56 PM, Nicolas Le Manchet wrote: > As Kye Russell mentioned, email addresses being case-sensitive for the local > part and case-insensitive for the domain part is a whole different problem > that has implications way beyond Django. In my opinion, it is best to leave > it out of the issue and focus the discussion on usernames. There was another Ticket about the email casing #17561 [1]. [1]: https://code.djangoproject.com/ticket/17561 -- Tobias Wiese -- 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 it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ba41335c-a5fe-0368-abce-166e5b7a2ab3%40tobiaswiese.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: Can we make HTTP 308 the default for CommonMiddleware / APPEND_SLASH?
Hello, On 1/11/19 6:42 PM, George-Cristian Bîrzan wrote: > the only thing that I can think of is whether HSTS preload will > support anything except 301. All my pages redirect via a 308 from the http to the https version. And most of them are HSTS preloaded. So no problem here. -- Tobias Wiese -- 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 it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4fe097e2-0f41-e4f7-8075-1c7acac8933c%40tobiaswiese.com. For more options, visit https://groups.google.com/d/optout.
Re: Proposal to re-open #27017 (updating only dirty fields in save())
On 3/14/19 10:52 AM, Adam Johnson wrote: > Assuming the application is not using either a transaction or > select_for_update(), current Django does still guarantee that either the > complete state after Process 1 or 2 is in the database, by always writing > back all the fields. That is, no Photo instance can have its total set to > anything but likes * multiplier , since Django's save() sends all fields in > a single UPDATE statement, which is always atomic. Sure there's a race > condition and the results of either process 1 or 2 can be lost, but still > there's a guarantee on the relationship between the values, which > downstream logic might rely on. > > Moving to dirty field tracking would break this guarantee. This would > probably cause untold low-level breakage in applications where atomicity > has not been considered. Therefore it seems like it would be a breaking > change which is hard to communicate to users, a complicated situation. This case already has the bug, that data gets lost. (Beside that one shouldn't have fields that rely on other fields that much anyway). This change would only move the bug somewere else, were it is also easier to detect (the existance of the bug, not exactly where it happens) Beside that I don't see a vaild use case where something like this would actually happen. -- Tobias Wiese -- 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 it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1d8a4070-f34d-6b0f-c83f-5a2316b4bc63%40tobiaswiese.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: cannot use a string pattern on a bytes-like object
Hello, This mailing list is for development. You are probably searching for the list for users to ask questions: django-us...@googlegroups.com Alternatively you might ask your question on freenode irc in the channel #django -- Tobias Wiese PGP KEY: https://tobiaswiese.com/pgp.asc PGP FPR: E1A7A8879BAD75B42D63F3310F067C2DD70E89A0 -- 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 it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20190602205908.GA13849%40origin.wieto.net. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
