Re: [Django] #13394: django.contrib.auth.tests fail with custom Authentication Backends

1 view
Skip to first unread message

Django

unread,
Nov 17, 2011, 8:06:10 PM11/17/11
to django-...@googlegroups.com
#13394: django.contrib.auth.tests fail with custom Authentication Backends
-------------------------------------+-------------------------------------
Reporter: timc3 | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: SVN
Severity: Normal | Resolution:
Keywords: Auth, contrib, | Triage Stage: Accepted
testing | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by julien):

* ui_ux: => 0
* easy: => 0


Comment:

See also #17194.

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

Django

unread,
Dec 31, 2011, 6:38:38 AM12/31/11
to django-...@googlegroups.com
#13394: django.contrib.auth.tests fail with custom Authentication Backends
-------------------------------------+-------------------------------------
Reporter: timc3 | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: SVN
Severity: Normal | Resolution:
Keywords: Auth, contrib, | Triage Stage: Accepted
testing | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by claudep):

* has_patch: 0 => 1


Comment:

I'm resubmitting the (refreshed) patch that I proposed for #17194, with
the idea of a DefaultSettingsTestCase to isolate the app tests from any
current project settings.

--
Ticket URL: <https://code.djangoproject.com/ticket/13394#comment:6>

Django

unread,
Aug 1, 2013, 1:08:46 PM8/1/13
to django-...@googlegroups.com
#13394: django.contrib.auth.tests fail with custom Authentication Backends
-------------------------------------+-------------------------------------
Reporter: timc3 | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: master

Severity: Normal | Resolution:
Keywords: Auth, contrib, | Triage Stage: Accepted
testing | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1

Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timo):

* needs_better_patch: 0 => 1


Comment:

This seems like a good idea to me; patch needs to be updated to apply
cleanly though.

#20796 was a recent a duplicate.

--
Ticket URL: <https://code.djangoproject.com/ticket/13394#comment:7>

Django

unread,
Aug 1, 2013, 7:18:36 PM8/1/13
to django-...@googlegroups.com
#13394: django.contrib.auth.tests fail with custom Authentication Backends
-------------------------------------+-------------------------------------
Reporter: timc3 | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: Auth, contrib, | Triage Stage: Accepted
testing | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Comment (by russellm):

Isn't this a moot point once 1.6 lands? Django's new unittest discovery
mechanism means that auth tests won't be run as part of an end-developer's
test suite, so the we don't have to be quite as concerned about adapting
to every possible environmental configuration.

--
Ticket URL: <https://code.djangoproject.com/ticket/13394#comment:8>

Django

unread,
Aug 1, 2013, 7:48:28 PM8/1/13
to django-...@googlegroups.com
#13394: django.contrib.auth.tests fail with custom Authentication Backends
-------------------------------------+-------------------------------------
Reporter: timc3 | Owner: nobody
Type: Bug | Status: closed
Component: contrib.auth | Version: master
Severity: Normal | Resolution: wontfix

Keywords: Auth, contrib, | Triage Stage: Accepted
testing | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timo):

* status: new => closed
* resolution: => wontfix


Comment:

Ah, didn't realize that Russ, thanks!

--
Ticket URL: <https://code.djangoproject.com/ticket/13394#comment:9>

Reply all
Reply to author
Forward
0 new messages