I too realise I don't have a(n obvious) break key but have been happily
hitting CTRL-C.
On Monday, 21 June 2021 at 23:53:15 UTC+2 Adam Johnson wrote:
> Would it be bad to have Django respond to both shortcuts?
>
I think as a matter of fact it does. At least using PowerShell/Win10/Etc —
Would it be bad to have Django respond to both shortcuts?
On Mon, 21 Jun 2021 at 21:40, Matthew Pava wrote:
> Ctrl + Break and Ctrl + C are treated slightly differently by Windows.
> Ctrl + Break is always a signal, but an application can override the
> functionality of Ctrl + C.
>
>
>
> Please
So am I right that the example model with deleted_at will not be validated
by ModelForm as deleted_at will never be included in it?
I tried implementing ExclusionConstraint.validate
(https://github.com/Gagaro/django/commit/558f33f574838b21cc9bf58a825ef337e7b1d0b2)
but I had to use RawSQL as I
Ctrl + Break and Ctrl + C are treated slightly differently by Windows. Ctrl +
Break is always a signal, but an application can override the functionality of
Ctrl + C.
Please see
https://docs.microsoft.com/en-us/windows/console/ctrl-c-and-ctrl-break-signals
I’ve dealt with this issue many
Hi all,
Is the Pause/Break key still a thing on Windows keyboards? My new Surface 4
doesn't even have such a key and I think this applies to many new Windows
keyboards as well.
I ask because the runserver.py command
Week ending June 20, 2021
*Holidays ☀️*
Best,
Mariusz
--
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
Week ending June 13, 2021
*Triaged: *
https://code.djangoproject.com/ticket/32820 - Fields’ errors should be
programmatically associated with fields. (accepted)
https://code.djangoproject.com/ticket/32819 - Fields’ help text and
errors should be associated with input. (accepted)
That's looking great :)
1. Yes and that's expected. If a form/serializer doesn't provide some
fields included in the constraint the database client side of the
validation can't do much about it. It might result in an integrity error
but that's a misuse of the API. I guess a check/runtime
I tried my hand at implementing Q.check()
(https://github.com/Gagaro/django/tree/ticket-30581).
A few things:
1/ Is the exclude parameter there because of Model.validate_unique
signature? Conditional UniqueConstraint might not work in those cases if a
field use in a the condition is not in
