#26480: Allow sensitive_variables() to preserve the signature of its decorated
function
-------------------------------------+-------------------------------------
     Reporter:  tpazderka            |                    Owner:  Baptiste
         Type:                       |  Mispelon
  Cleanup/optimization               |                   Status:  closed
    Component:  Error reporting      |                  Version:  master
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"3df3c5e67070949887e08282a332cc34c1f05184" 3df3c5e6]:
 {{{
 #!CommitTicketReference repository=""
 revision="3df3c5e67070949887e08282a332cc34c1f05184"
 Fixed #26480 -- Fixed crash of contrib.auth.authenticate() on decorated
 authenticate() methods of authentication backends.

 The Signature API (PEP 362) has better support for decorated functions
 (by default, it follows the __wrapped__ attribute set by
 functools.wraps for example).
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/26480#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1138a68bafd90194f6c9735c3e4a3506%40djangoproject.com.

Reply via email to