Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add testcase to show erroneous multiple runs of django.setup() #538

Closed
wants to merge 1 commit into from

Conversation

pakal
Copy link

@pakal pakal commented Oct 30, 2017

Testcase to advance on #531

@blueyed
Copy link
Contributor

blueyed commented Jan 18, 2018

Rebased against master.
I think it could be fixed for Django 2.0 at least given https://code.djangoproject.com/ticket/27176 (django/django#7682).

@blueyed
Copy link
Contributor

blueyed commented Jul 26, 2018

Will include this into #629.

@blueyed blueyed closed this Jul 26, 2018
blueyed added a commit to blueyed/pytest-django that referenced this pull request Jul 26, 2018
@blueyed
Copy link
Contributor

blueyed commented Jul 26, 2018

I think the test added to https://github.com/pytest-dev/pytest-django/pull/629/files#diff-b8f370066f4a8dcc417f6e09e1689a84 is enough to test this, do you agree?

blueyed added a commit to blueyed/pytest-django that referenced this pull request Jul 26, 2018
@blueyed
Copy link
Contributor

blueyed commented Jul 26, 2018

Backed out the changes in #629, basically only fixing this issue now.

@pakal
Copy link
Author

pakal commented Aug 5, 2018

Yes the test added above seems to make the same as mine, ensuring django.setup() is only called once

@blueyed
Copy link
Contributor

blueyed commented Aug 5, 2018

Cool, merged #629.

@pakal
Copy link
Author

pakal commented Sep 7, 2018

Thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants