Skip to content

live_server: fix in-memory DB detection, dj 2.2 compat #793

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

Closed

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented Jan 5, 2020

Fixes #783.

TODO:

  • dec_thread_sharing() ? (also for dj < 2.2 then likely)

blueyed added a commit to blueyed/pytest-django that referenced this pull request Jan 7, 2020
blueyed added a commit to blueyed/pytest-django that referenced this pull request Jan 13, 2020
@blueyed blueyed mentioned this pull request Jan 14, 2020
blueyed added a commit to blueyed/pytest-django that referenced this pull request Jan 21, 2020
blueyed added a commit to blueyed/pytest-django that referenced this pull request Jan 22, 2020
blueyed added a commit to blueyed/pytest-django that referenced this pull request Mar 31, 2020
@blueyed blueyed force-pushed the live_server-inc_thread_sharing branch from ec6f271 to b29b1b5 Compare March 31, 2020 09:53
@githubdd7
Copy link

Are there any plans to merge this change ? We think this can fix our pytest errors. Thank You.

@asfaltboy
Copy link
Contributor

I'd love to pick it up, @blueyed could you provide some background on this PR, i.e with the changes that remove the thread logic, how will this still work?

@boxed
Copy link
Contributor

boxed commented Feb 19, 2021

I hit this exact problem today! Would love it if this was merged and released!

@bluetech
Copy link
Member

bluetech commented Dec 1, 2021

Fixed in #973 (didn't see this one before...)

@bluetech bluetech closed this Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Live server error with sqlite3
5 participants