So I recently ran into the csrf/upload_handlers conflict as mentioned in
the not https://docs.djangoproject.com/en/1.8/topics/http/file-uploads/#id1
I'd like to propose an additional option to solve this -- a decorator to
mark a view as "ajax-only" ... so the CSRF middleware will _only_
After some testing I have found out that even when using values_list to prevent
massive object creation when fetching data, it is from 2 to 3 times slower tan
using directly a cursor.execute query through the django cursor.
The issue started here
I'm not sure something like this should live inside Django proper. There is
nothing to guarantee that a user model will have an email address even
though the standard builtins do. I'd feel better about having this
functionality provided by a library, maybe even by django-registration
which
I don't think it's documented anywhere.
I found the link by going to https://www.djangoproject.com/~bmispelon/
(replace by your username) and there was a link to it in the right side bar.
Baptiste
On 11/15/2015 02:57 PM, Daniele Procida wrote:
On Sun, Nov 15, 2015, Baptiste Mispelon
On Sun, Nov 15, 2015, Baptiste Mispelon wrote:
>For your djangoproject account, you can change your display name and
>email there: https://www.djangoproject.com/accounts/edit/.
Heh, thanks, not even Florian was aware of that.
Is this documented somewhere?
Daniele
--
For your djangoproject account, you can change your display name and
email there: https://www.djangoproject.com/accounts/edit/.
Baptiste
On 11/15/2015 02:46 PM, Daniele Procida wrote:
I've been discussing with Florian on IRC a suggestion for improved account
security.
On many sites, you
I've been discussing with Florian on IRC a suggestion for improved account
security.
On many sites, you will get a message a message like this:
>Hello evildmp,
>
>We wanted to let you know that your GitHub password was changed.
>
>If you did not perform this action, you can recover access by