Re: [Django] #33449: Migration autodetector crashes on models with field named _order, but not using order_with_respect_to.

[Django]

#33449: Migration autodetector crashes on models with field named _order, but 
not
using order_with_respect_to.
-+-
 Reporter:  Fabian Büchler   |Owner:  Fabian
 |  Büchler
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  4.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b32080219ebaacbee73f8abd8a9ddc85387f95ed" b320802]:
 {{{
 #!CommitTicketReference repository=""
 revision="b32080219ebaacbee73f8abd8a9ddc85387f95ed"
 [4.0.x] Fixed #33449 -- Fixed makemigrations crash on models without
 Meta.order_with_respect_to but with _order field.

 Regression in aa4acc164d1247c0de515c959f7b09648b57dc42.

 Backport of eeff1787b0aa23016e4844c0f537d5093a95a356 from main
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.497310e4846d31d025ae3235df5de1e5%40djangoproject.com.

Re: [Django] #33449: Migration autodetector crashes on models with field named _order, but not using order_with_respect_to.

[Django]

#33449: Migration autodetector crashes on models with field named _order, but 
not
using order_with_respect_to.
-+-
 Reporter:  Fabian Büchler   |Owner:  Fabian
 |  Büchler
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  4.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"eeff1787b0aa23016e4844c0f537d5093a95a356" eeff1787]:
 {{{
 #!CommitTicketReference repository=""
 revision="eeff1787b0aa23016e4844c0f537d5093a95a356"
 Fixed #33449 -- Fixed makemigrations crash on models without
 Meta.order_with_respect_to but with _order field.

 Regression in aa4acc164d1247c0de515c959f7b09648b57dc42.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.c9566cf37d5f18ebdfec00f42c25c423%40djangoproject.com.

Re: [Django] #33449: Migration autodetector crashes on models with field named _order, but not using order_with_respect_to.

[Django]

#33449: Migration autodetector crashes on models with field named _order, but 
not
using order_with_respect_to.
-+-
 Reporter:  Fabian Büchler   |Owner:  Fabian
 |  Büchler
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.271531172e98bf55d5e2879fe4ee13a8%40djangoproject.com.

Re: [Django] #29984: Support prefetch_related() with Queryset.iterator()

[Django]

#29984: Support prefetch_related() with Queryset.iterator()
-+-
 Reporter:  Taylor H |Owner:  Jacob
 |  Walls
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 Jacob Walls):

 * needs_better_patch:  1 => 0


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.568a457fb1c04f53377fb29373f8f733%40djangoproject.com.

Re: [Django] #33449: Migration autodetector crashes on models with field named _order, but not using order_with_respect_to.

[Django]

#33449: Migration autodetector crashes on models with field named _order, but 
not
using order_with_respect_to.
-+-
 Reporter:  Fabian Büchler   |Owner:  Fabian
 |  Büchler
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Patch LGTM once a release note is added.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.3757e37d7f4fa38d1a0bd65d51cd5095%40djangoproject.com.

Re: [Django] #26142: Provide a way for model formsets to disallow new object creation

[Django]

#26142: Provide a way for model formsets to disallow new object creation
-+
 Reporter:  Tim Graham   |Owner:  Vlad
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Jacob Walls):

 * needs_docs:  0 => 1


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.d6755c9c1925e27856cae7b335bbacaa%40djangoproject.com.

Re: [Django] #33449: Migration autodetector crashes on models with field named _order, but not using order_with_respect_to.

[Django]

#33449: Migration autodetector crashes on models with field named _order, but 
not
using order_with_respect_to.
-+-
 Reporter:  Fabian Büchler   |Owner:  Fabian
 |  Büchler
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 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 Fabian Büchler):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15339 PR] submitted. CCLA pending.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.84d07a3fe1e3f8bbcd99438ddb3e43c7%40djangoproject.com.

Re: [Django] #33455: Missleading error message when running selenium tests without selenium.

[Django]

#33455: Missleading error message when running selenium tests without selenium.
-+-
 Reporter:  David Smith  |Owner:  Mohamed
 Type:   |  Nabil Rady
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mohamed Nabil Rady):

 * owner:  nobody => Mohamed Nabil Rady
 * status:  new => assigned
 * has_patch:  0 => 1
 * easy:  0 => 1


Comment:

 https://github.com/django/django/pull/15338

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.919620be2ec09dd26a6fdf8d82e07efe%40djangoproject.com.

Re: [Django] #33455: Missleading error message when running selenium tests without selenium. (was: Potentially missleading error message when running selenium tests)

[Django]

#33455: Missleading error message when running selenium tests without selenium.
--+
 Reporter:  David Smith   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Testing framework
 * stage:  Unreviewed => Accepted


Comment:

 We could try to import `selenium` before calling `import_webdriver()`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.308dc890ed53d4e7afb009cee8b583ce%40djangoproject.com.

Re: [Django] #26142: Provide a way for model formsets to disallow new object creation

[Django]

#26142: Provide a way for model formsets to disallow new object creation
-+
 Reporter:  Tim Graham   |Owner:  Vlad
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Vlad):

 * needs_docs:  1 => 0


Comment:

 Added topic about `edit_only` mode in Formsets and fixed other remarks.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1ca05961a3280fe2aecbea8ddcbf8dc1%40djangoproject.com.

Re: [Django] #33453: Drop support for GDAL 2.1.

[Django]

#33453: Drop support for GDAL 2.1.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  dev
 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 GitHub ):

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


Comment:

 In [changeset:"f605e85af9763a3940369bb79462f2cb466288f6" f605e85]:
 {{{
 #!CommitTicketReference repository=""
 revision="f605e85af9763a3940369bb79462f2cb466288f6"
 Fixed #33453 -- Dropped support for GDAL 2.1.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ca29a8e77508907f583b0e244eaa1c90%40djangoproject.com.

[Django] #33455: Potentially missleading error message when running selenium tests

[Django]

#33455: Potentially missleading error message when running selenium tests
-+
   Reporter:  David Smith|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  4.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I got tripped up by the error message generated by this line

 
https://github.com/django/django/blob/2c76c27a951ee76c6f763a05c7e119305a21c78d/tests/runtests.py#L329

 The issue was that I didn't have selenium installed. However, the error
 message I received was


 {{{
 runtests.py: error: argument --selenium: Selenium browser specification
 'chrome' is not valid.

 }}}

 Therefore much head scratching trying to think about what was wrong with
 chrome/webdriver rather than not having selenium installed. Maybe there is
 something better we could do here?

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.274d37956ceef09de46e2720a0319f7d%40djangoproject.com.

Re: [Django] #26760: Delete nonexistent migrations from django_migrations table

[Django]

#26760: Delete nonexistent migrations from django_migrations table
-+-
 Reporter:  Jarek Glowacki   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  django_migrations| Triage Stage:  Accepted
  squash migrations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * needs_better_patch:  1 => 0


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4b0a40cd65c4c43f91b739fadd4df9cc%40djangoproject.com.

Re: [Django] #33454: Django4 does not pick up tests according to market value

[Django]

#33454: Django4 does not pick up tests according to market value
---+--
 Reporter:  Thorben Luepkes|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  4.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham):

 You need to debug the issue and explain where Django is at fault. See if
 you can [https://docs.djangoproject.com/en/dev/internals/contributing
 /triaging-tickets/#bisecting-a-regression bisect] to find the commit where
 the behavior changed.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a7b560d407e3d69a04c06d64ac1570c5%40djangoproject.com.

Re: [Django] #33453: Drop support for GDAL 2.1.

[Django]

#33453: Drop support for GDAL 2.1.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 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 Nick Pope):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6541933fc6b33f0eb117cf23d7567f2f%40djangoproject.com.

Re: [Django] #33453: Drop support for GDAL 2.1.

[Django]

#33453: Drop support for GDAL 2.1.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15337 PR]

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e6175f852d6e25dc7512635b30dcea85%40djangoproject.com.

Re: [Django] #33454: Django4 does not pick up tests according to market value (was: Django 4 TestRunner does not pick up tests correctly.)

[Django]

#33454: Django4 does not pick up tests according to market value
---+--
 Reporter:  Thorbenl   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  4.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.e4c06c44b96ceb64a67077024f669a5a%40djangoproject.com.

[Django] #33454: Django 4 TestRunner does not pick up tests correctly.

[Django]

#33454: Django 4 TestRunner does not pick up tests correctly.
-+
   Reporter:  Thorbenl   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  4.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Hey!
 We use Django for an online webshop, and want to upgrade to Django 4.
 However, since upgrading on a test branch, we have encountered a problem,
 that did not appear before upgrading:

 We serve two different markets, lets call them Market A and B. Since these
 two markets can have different functionalities, our INSTALLED_APPS gets
 populated like so:
 Here is more information, and the error traces:



 {{{
 INSTALLED_APPS = [
...
'payments', # THIS INCLUDES `BasePayment` Model

 ]
 }}}




 {{{
 MARKET_SPECIFIC_APPS = {
 MARKET_B: [
 'market_b.apps.MarketBConfig',
 'market_b_payments.apps.MarketBPaymentsConfig'
 ],
 MARKET_A: [
 'market_a.apps.MarketAConfig',
 'market_a_payments.apps.MarketAPaymentsConfig'
 ],
 }
 }}}



 {{{
 if MARKET in MARKET_SPECIFIC_APPS:
 # If there is a market-specific app, add it to INSTALLED_APPS
 INSTALLED_APPS += MARKET_SPECIFIC_APPS[MARKET]
 }}}



 {{{
 ==
 ERROR [0.004s]: market_a.test_redirects (unittest.loader._FailedTest)
 --
 ImportError: Failed to import test module: market_a.test_redirects
 Traceback (most recent call last):
   File
 
"/usr/local/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/unittest/loader.py",
 line 436, in _find_test_path
 module = self._get_module_from_name(name)
   File
 
"/usr/local/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/unittest/loader.py",
 line 377, in _get_module_from_name
 __import__(name)
   File "/e-commerce/market_a/test_redirects.py", line 5, in 
 from market_a.models import AdvertisementIdMapping
   File "/e-commerce/market_a/models.py", line 14, in 
 class MigratedMissingData(models.Model):
   File "/e-commerce/venv/lib/python3.9/site-
 packages/django/db/models/base.py", line 113, in __new__
 raise RuntimeError(
 RuntimeError: Model class market_a.models.MigratedMissingData doesn't
 declare an explicit app_label and isn't in an application in
 INSTALLED_APPS.


 ==
 ERROR [0.000s]: market_a_payments.models (unittest.loader._FailedTest)
 --
 ImportError: Failed to import test module: market_a_payments.models
 Traceback (most recent call last):
   File
 
"/usr/local/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/unittest/loader.py",
 line 470, in _find_test_path
 package = self._get_module_from_name(name)
   File
 
"/usr/local/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/unittest/loader.py",
 line 377, in _get_module_from_name
 __import__(name)
   File "/e-commerce/market_a_payments/models/__init__.py", line 1, in
 
 from .payment import Payment
   File "/e-commerce/market_a_payments/models/payment.py", line 12, in
 
 class Payment(BasePayment):
   File "/e-commerce/venv/lib/python3.9/site-
 packages/django/db/models/base.py", line 113, in __new__
 raise RuntimeError(
 RuntimeError: Model class market_a_payments.models.payment.Payments
 doesn't declare an explicit app_label and isn't in an application in
 INSTALLED_APPS.


 ==
 ERROR [0.000s]: market_a_payments.tests (unittest.loader._FailedTest)
 --
 ImportError: Failed to import test module: market_a_payments.tests
 Traceback (most recent call last):
   File
 
"/usr/local/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/unittest/loader.py",
 line 436, in _find_test_path
 module = self._get_module_from_name(name)
   File
 
"/usr/local/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/unittest/loader.py",
 line 377, in _get_module_from_name
 __import__(name)
   File "/e-commerce/market_a_payments/tests.py", line 20, in 
 from market_a_payments.models import Payment
   File "/e-commerce/market_a_payments/models/__init__.py", line 1, in
 
 from .paym

[Django] #33453: Drop support for GDAL 2.1.

[Django]

#33453: Drop support for GDAL 2.1.
-+-
   Reporter:  Mariusz|  Owner:  Mariusz Felisiak
  Felisiak   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  GIS|Version:  dev
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 It'll be more than five years old at the release of Django 4.1.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.250e4b6480de5999d0c911aaff1fde55%40djangoproject.com.

Re: [Django] #26760: Delete nonexistent migrations from django_migrations table

[Django]

#26760: Delete nonexistent migrations from django_migrations table
-+-
 Reporter:  Jarek Glowacki   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  django_migrations| Triage Stage:  Accepted
  squash migrations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a3dbe113d022ea1adcc882c80de4fe48%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

[Django]

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8230e7a6098aaafe6d18be968ab44022%40djangoproject.com.

Re: [Django] #33062: File upload crash when a file extension contains null characters.

[Django]

#33062: File upload crash when a file extension contains null characters.
-+-
 Reporter:  Alex Vandiver|Owner:
 |  Hrushikesh Vaidya
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  3.2
  uploads/storage|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"3fadf141e66c8d0baaa66574fa3b63c4d3655482" 3fadf141]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fadf141e66c8d0baaa66574fa3b63c4d3655482"
 Fixed #33062 -- Made MultiPartParser remove non-printable chars from file
 names.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.fb898b9e458e18a39163465f0f76a323%40djangoproject.com.