Re: [Django] #32416: LiveServerTestCase's ThreadedWSGIServer doesn't close database connections after each thread (was: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServer

#32416: LiveServerTestCase's ThreadedWSGIServer doesn't close database connections after each thread ---+ Reporter: Chris Jerdonek |Owner: nobody Type: Bug|

Re: [Django] #32417: LiveServerTestCase._tearDownClassInternal() has unneeded hasattr check

#32417: LiveServerTestCase._tearDownClassInternal() has unneeded hasattr check --+ Reporter: Chris Jerdonek|Owner: nobody Type: Cleanup/optimization | Status:

Re: [Django] #32417: LiveServerTestCase._tearDownClassInternal() has unneeded hasattr check (was: LiveServerTestCase._tearDownClassInternal has unneeded hasattr check)

#32417: LiveServerTestCase._tearDownClassInternal() has unneeded hasattr check --+ Reporter: Chris Jerdonek|Owner: nobody Type: Cleanup/optimization | Status:

Re: [Django] #32417: LiveServerTestCase._tearDownClassInternal has unneeded hasattr check (was: LiveServerTestCase's tearDownClass() not symmetric with setUpClass())

#32417: LiveServerTestCase._tearDownClassInternal has unneeded hasattr check -+- Reporter: Chris Jerdonek |Owner: nobody Type: | Status: new

Re: [Django] #32417: LiveServerTestCase's tearDownClass() not symmetric with setUpClass()

#32417: LiveServerTestCase's tearDownClass() not symmetric with setUpClass() +-- Reporter: Chris Jerdonek |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #32424: in-memory test database does not work with multiprocessing.apply_async

#32424: in-memory test database does not work with multiprocessing.apply_async -+- Reporter: Tata Krushna |Owner: Chaitanya | ArkaprabhaChakraborty Type:

Re: [Django] #29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase

#29062: "database table locked errors" when using sqlite in-memory database with LiveServerTestCase -+- Reporter: Juozas Masiulis |Owner: nobody Type: Bug |

Re: [Django] #32416: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServerTestCase (#20238)

#32416: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServerTestCase (#20238) ---+ Reporter: Chris Jerdonek |Owner: nobody Type: Bug|

Re: [Django] #32423: Support for extra related lookup definitions of a field.

#32423: Support for extra related lookup definitions of a field. -+- Reporter: Bálint Balina|Owner: nobody Type: New feature | Status: closed

Re: [Django] #32411: Case-insensitive lookups on JSONField doesn't work on MySQL.

#32411: Case-insensitive lookups on JSONField doesn't work on MySQL. -+- Reporter: elonzh |Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #32424: in-memory test database does not work with multiprocessing.apply_async

#32424: in-memory test database does not work with multiprocessing.apply_async -+- Reporter: Tata Krushna |Owner: nobody Chaitanya | Type: Uncategorized

[Django] #32424: in-memory test database does not work with multiprocessing.apply_async

#32424: in-memory test database does not work with multiprocessing.apply_async -+- Reporter: Tata | Owner: nobody Krushna Chaitanya | Type: |

Re: [Django] #32416: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServerTestCase (#20238)

#32416: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServerTestCase (#20238) ---+ Reporter: Chris Jerdonek |Owner: nobody Type: Bug|

Re: [Django] #32419: "Serving files uploaded by a user during development" example unclear about "urls.py"

#32419: "Serving files uploaded by a user during development" example unclear about "urls.py" -+- Reporter: Josef Richter|Owner: Amankumar Type: | Singh

Re: [Django] #32419: "Serving files uploaded by a user during development" example unclear about "urls.py"

#32419: "Serving files uploaded by a user during development" example unclear about "urls.py" -+- Reporter: Josef Richter|Owner: Amankumar Type: | Singh

Re: [Django] #32419: "Serving files uploaded by a user during development" example unclear about "urls.py"

#32419: "Serving files uploaded by a user during development" example unclear about "urls.py" -+- Reporter: Josef Richter|Owner: Amankumar Type: | Singh

[Django] #32423: Support for extra related lookup definitions of a field.

#32423: Support for extra related lookup definitions of a field. -+- Reporter: CloudCode | Owner: nobody Hungary| Type: New| Status:

Re: [Django] #32411: Case-insensitive lookups on JSONField doesn't work on MySQL.

#32411: Case-insensitive lookups on JSONField doesn't work on MySQL. -+- Reporter: elonzh |Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #32420: build_instance in (de)serializers uses model's primary key field name instead of attname to detect if data contains a primary key

#32420: build_instance in (de)serializers uses model's primary key field name instead of attname to detect if data contains a primary key --+ Reporter: trybik|Owner: trybik

Re: [Django] #32420: build_instance in (de)serializers uses model's primary key field name instead of attname to detect if data contains a primary key

#32420: build_instance in (de)serializers uses model's primary key field name instead of attname to detect if data contains a primary key --+ Reporter: trybik|Owner: trybik

Re: [Django] #32411: Case-insensitive lookups on JSONField doesn't work on MySQL.

#32411: Case-insensitive lookups on JSONField doesn't work on MySQL. -+- Reporter: elonzh |Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #32416: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServerTestCase (#20238)

#32416: Apparent regression of #22414 from switching to ThreadedWSGIServer in LiveServerTestCase (#20238) +-- Reporter: Chris Jerdonek |Owner: nobody Type: Uncategorized |