Re: [Django] #34219: Collation is not preserved when field is altered on PostgreSQL and MySQL.

[Django]

#34219: Collation is not preserved when field is altered on PostgreSQL and 
MySQL.
-+-
 Reporter:  David Foster |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 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:"ae0899be0d787fbfc5f5ab2b18c5a8219d822d2b" ae0899b]:
 {{{
 #!CommitTicketReference repository=""
 revision="ae0899be0d787fbfc5f5ab2b18c5a8219d822d2b"
 Fixed #34219 -- Preserved Char/TextField.db_collation when altering column
 type.

 This moves setting a database collation to the column type alteration
 as both must be set at the same time.

 This should also avoid another layer of the column type alteration when
 adding database comments support (#18468).
 }}}

-- 
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/010701853876b652-f3fe4af8-88af-40d5-b71f-6fc153e8d39e-00%40eu-central-1.amazonses.com.

Re: [Django] #34208: Confirm/Add support for GDAL 3.6.

[Django]

#34208: Confirm/Add support for GDAL 3.6.
--+
 Reporter:  Mariusz Felisiak  |Owner:  Leo Tom
 Type:  New feature   |   Status:  assigned
Component:  GIS   |  Version:  4.1
 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 Leo Tom):

 * owner:  nobody => Leo Tom
 * status:  new => assigned


-- 
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/010701853786146d-2cb64cc6-62fd-4291-843a-ab1b7ae1c882-00%40eu-central-1.amazonses.com.

Re: [Django] #34221: Plural-Forms in .po files break Django's translation precedence.

[Django]

#34221: Plural-Forms in .po files break Django's translation precedence.
--+
 Reporter:  Stefano Parmesan  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  4.1
 Severity:  Normal|   Resolution:
 Keywords:  i18n  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the detailed report and test project!

 To solve #30439 and allow for different plural forms for a same language,
 we had to refrain from merging all translations in a unique catalog, as
 was done before. However, your setup demonstrates that the algorithm to
 decide between merge or separating catalogs is flawed (the third catalog
 from LOCALE_PATH having the same plural forms as the Django one, it is
 merge with it, hence loosing it's priority over the intermediary django-
 extension catalog).

 The following patch should fix the issue:
 {{{
 diff --git a/django/utils/translation/trans_real.py
 b/django/utils/translation/trans_real.py
 index c1e64d4ebd..f4d05b8f76 100644
 --- a/django/utils/translation/trans_real.py
 +++ b/django/utils/translation/trans_real.py
 @@ -96,11 +96,9 @@ class TranslationCatalog:
  yield from cat.keys()

  def update(self, trans):
 -# Merge if plural function is the same, else prepend.
 -for cat, plural in zip(self._catalogs, self._plurals):
 -if trans.plural.__code__ == plural.__code__:
 -cat.update(trans._catalog)
 -break
 +# Merge if plural function is the same as the top catalog, else
 prepend.
 +if trans.plural.__code__ == self._plurals[0]:
 +self._catalogs[0].update(trans._catalog)
  else:
  self._catalogs.insert(0, trans._catalog.copy())
  self._plurals.insert(0, trans.plural)
 }}}

-- 
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/01070185363fabc7-2312c96f-b0a6-4726-b325-42819db5af9b-00%40eu-central-1.amazonses.com.

Re: [Django] #33735: Add asynchronous responses for use with an ASGI server

[Django]

#33735: Add asynchronous responses for use with an ASGI server
+--
 Reporter:  florianvazelle  |Owner:  Carlton Gibson
 Type:  New feature |   Status:  assigned
Component:  HTTP handling   |  Version:  4.0
 Severity:  Normal  |   Resolution:
 Keywords:  ASGI async  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Carlton Gibson):

 * needs_better_patch:  1 => 0


Comment:

 PR should now be ready for review.

-- 
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/01070185363cfbc4-9c4e2e74-caa2-4ce2-bc94-7413f5d45c48-00%40eu-central-1.amazonses.com.

Re: [Django] #34180: Document that setting language in tests affects other tests

[Django]

#34180: Document that setting language in tests affects other tests
-+-
 Reporter:  Václav Řehák |Owner:  Faris
 |  Naimi
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  documentation i18n   | Triage Stage:  Accepted
  tests  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Václav Řehák):

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


Comment:

 How can you close ticket just because there is a commit in a Github fork?
 The issue is not closed until is it merged into Django source code (or
 wontfixed).

-- 
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/01070185363b4372-8290996f-e325-42d7-9f83-856ac78156a6-00%40eu-central-1.amazonses.com.

Re: [Django] #34180: Document that setting language in tests affects other tests

[Django]

#34180: Document that setting language in tests affects other tests
-+-
 Reporter:  Václav Řehák |Owner:  Faris
 |  Naimi
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  4.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  documentation i18n   | Triage Stage:  Accepted
  tests  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Faris Naimi):

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


-- 
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/010701853632add8-0c98a25c-59d0-40a4-a84b-1c5232d343fb-00%40eu-central-1.amazonses.com.

Re: [Django] #34180: Document that setting language in tests affects other tests

[Django]

#34180: Document that setting language in tests affects other tests
-+-
 Reporter:  Václav Řehák |Owner:  Faris
 |  Naimi
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  documentation i18n   | Triage Stage:  Accepted
  tests  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Faris Naimi):

 The documentation was modified to explain the issue and the possibility of
 activating the default language in the tearDown method.

 This is now available from the branch "ticket_34180" on the repo:

 https://github.com/fnaimi66/django.git

-- 
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/0107018536307cfb-c6252770-e2cc-481a-b1e6-48ea2dde827b-00%40eu-central-1.amazonses.com.

Re: [Django] #34223: I am Faceing tis type of error when i run the command py manage.py runserver Error=usage: manage.py [-h] [-c] manage.py: error: unrecognized arguments: runserver

[Django]

#34223: I am Faceing tis type of error when i run the command py manage.py
runserver  Error=usage: manage.py [-h] [-c] manage.py: error: unrecognized
arguments: runserver
---+--
 Reporter:  Umer Farooq|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  4.1
 Severity:  Normal |   Resolution:  invalid
 Keywords:  django | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Mariusz Felisiak):

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


Comment:

 Please don't use Trac as a support channel. Closing per
 TicketClosingReasons/UseSupportChannels.

-- 
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/0107018535ed584c-8604da3c-79ce-40bf-9b37-53ff64ccfd99-00%40eu-central-1.amazonses.com.

Re: [Django] #34223: I am Faceing tis type of error when i run the command py manage.py runserver Error=usage: manage.py [-h] [-c] manage.py: error: unrecognized arguments: runserver (was: I am Facein

[Django]

#34223: I am Faceing tis type of error when i run the command py manage.py
runserver  Error=usage: manage.py [-h] [-c] manage.py: error: unrecognized
arguments: runserver
-+--
 Reporter:  umer-farooq-dev  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  django   | 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/0107018535e7398f-df733938-35e4-43a6-8cff-5c7b9b381e49-00%40eu-central-1.amazonses.com.

[Django] #34223: I am Faceing tis type of error when i run the command py manage.py runserver

[Django]

#34223: I am Faceing tis type of error when i run the command py manage.py
runserver
---+
   Reporter:  umer-farooq-dev  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Uncategorized|Version:  4.1
   Severity:  Normal   |   Keywords:  django
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 PS F:\Git\ClintProjects\Bait-Souq\bait_souq> py manage.py runserver
 Performing system checks...

 usage: manage.py [-h] [-c]
 manage.py: error: unrecognized arguments: runserver


 Please help

-- 
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/0107018535e632e4-b8af0eb6-34a6-4906-be86-68cfd8e2a09a-00%40eu-central-1.amazonses.com.

Re: [Django] #16055: Filtering over generic relations with TextField/CharField object_id breaks in postgres

[Django]

#16055: Filtering over generic relations with TextField/CharField object_id 
breaks
in postgres
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  3.2
 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 Sage Abdullah):

 * cc: Sage Abdullah (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/0107018535ddf612-ad7b5c73-26ea-4ec1-aae3-bcf8182e99a8-00%40eu-central-1.amazonses.com.

Re: [Django] #34222: Django unit tests hang when running against a Postgres database

[Django]

#34222: Django unit tests hang when running against a Postgres database
---+--
 Reporter:  Adrian Garcia  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  4.1
 Severity:  Normal |   Resolution:  invalid
 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 Egor R):

 I'm not that deeply involved with the project, so can't answer that. You
 might want to start a discussion on the [https://forum.djangoproject.com/
 Django forum] to gauge interest for that.

-- 
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/010701853591c384-9ec3247d-6f04-4912-98fe-60145c823c90-00%40eu-central-1.amazonses.com.

Re: [Django] #34222: Django unit tests hang when running against a Postgres database

[Django]

#34222: Django unit tests hang when running against a Postgres database
---+--
 Reporter:  Adrian Garcia  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  4.1
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Adrian Garcia):

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


Comment:

 Replying to [comment:1 Egor R]:
 > You have the same name for "default" and "other" databases, and they
 should be different. Try changing that and see if that helps.
 That solved it, knew it would probably be something incredibly dumb. Now
 that I've done a little more Googling it looks like I should have just
 copied the Django Docker Box config instead of writing my own.

 It's interesting that there are no checks to see if there are two DB
 configs for the same database, is there a use case for that?

-- 
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/01070185358230c5-54b30379-ccbe-4ca8-94ce-fc16eb6161c4-00%40eu-central-1.amazonses.com.

Re: [Django] #34222: Django unit tests hang when running against a Postgres database

[Django]

#34222: Django unit tests hang when running against a Postgres database
---+--
 Reporter:  Adrian Garcia  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  4.1
 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
---+--
Changes (by Egor R):

 * cc: Egor R (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/01070185356f35ac-f7cab72f-a6ad-4346-87ae-1f53364ef1a3-00%40eu-central-1.amazonses.com.

Re: [Django] #34222: Django unit tests hang when running against a Postgres database

[Django]

#34222: Django unit tests hang when running against a Postgres database
---+--
 Reporter:  Adrian Garcia  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  4.1
 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 Egor R):

 You have the same name for "default" and "other" databases, and they
 should be different. Try changing that and see if that helps.

-- 
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/01070185356edce3-bc0bc539-726a-439f-aa8b-ac4d909b6d4a-00%40eu-central-1.amazonses.com.

[Django] #34222: Django unit tests hang when running against a Postgres database

[Django]

#34222: Django unit tests hang when running against a Postgres database
-+
   Reporter:  Adrian Garcia  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  4.1
   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 am trying to get the
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /unit-tests/ Django library tests] running so I can develop a custom
 backend and everything works fine with the default SQLite settings file,
 but when I provide one for Postgres random tests will hang with no error.
 To debug, I am running the test suite with {{{runtests.py --noinput
 --parallel=1 -v 2 --settings test_postgres}}}

 test_postgres.py:
 {{{
 DATABASES = {
 "default": {
 "ENGINE": "django.db.backends.postgresql",
 "NAME": "postgres",
 "USER": "user",
 "PASSWORD": "password",
 "HOST": "127.0.0.1",
 "PORT": "5432",
 },
 "other": {
 "ENGINE": "django.db.backends.postgresql",
 "NAME": "postgres",
 "USER": "user",
 "PASSWORD": "password",
 "HOST": "127.0.0.1",
 "PORT": "5432",
 },
 }

 SECRET_KEY = "django_tests_secret_key"

 # Use a fast hasher to speed up tests.
 PASSWORD_HASHERS = [
 "django.contrib.auth.hashers.MD5PasswordHasher",
 ]

 DEFAULT_AUTO_FIELD = "django.db.models.AutoField"

 USE_TZ = False

 }}}

 Am I doing something wrong, or do these test cases hang for others? I
 cloned the 4.1.x repo and reset it to 2ff479f to specifically test against
 Django 4.1.4 and it consistently crashes *after*
 `multiple_database.tests.AuthTestCase` runs. If I get it working, I'll
 compile a list of test classes I have to skip to get the tests to run
 through without hanging.

-- 
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/01070185356bdd53-3d20903b-5623-474c-950e-f615b12cf9b8-00%40eu-central-1.amazonses.com.

Re: [Django] #34219: Collation is not preserved when field is altered on PostgreSQL and MySQL.

[Django]

#34219: Collation is not preserved when field is altered on PostgreSQL and 
MySQL.
-+-
 Reporter:  David Foster |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (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 Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16396 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/01070185349ec7b2-d3fc1445-8165-4b78-a78e-cfbda0866310-00%40eu-central-1.amazonses.com.

Re: [Django] #33961: Update admin's jQuery to 3.6.X.

[Django]

#33961: Update admin's jQuery to 3.6.X.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   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 Carlton Gibson):

 * 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/010701853475867a-cad49ebf-a8d2-4011-98cd-ce7acd4a82a6-00%40eu-central-1.amazonses.com.

Re: [Django] #26029: Provide an API to configure arbitrary file storage backends

[Django]

#26029: Provide an API to configure arbitrary file storage backends
-+-
 Reporter:  Aymeric Augustin |Owner:  Jarosław
 |  Wygoda
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  dev
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 PR looks promising, but have comments outstanding ref adding the new
 `STORAGES` defaults.

-- 
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/010701853460d7d6-2be8a853-ba87-4ff6-8db9-570723837f01-00%40eu-central-1.amazonses.com.

Re: [Django] #34219: Collation is not preserved when field is altered on PostgreSQL and MySQL.

[Django]

#34219: Collation is not preserved when field is altered on PostgreSQL and 
MySQL.
-+-
 Reporter:  David Foster |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 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):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned


Comment:

 I decided to work on this as we will have a similar issue with database
 comments.

-- 
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/010701853452cf94-01423fff-8850-4f2d-8dea-a41aa05f2616-00%40eu-central-1.amazonses.com.

Re: [Django] #29510: QueryDict.copy() returns closed files when the type of file is TemporaryUploadedFile

[Django]

#29510: QueryDict.copy() returns closed files when the type of file is
TemporaryUploadedFile
-+-
 Reporter:  Liquid Scorpio   |Owner:  Dan
 |  Madere
 Type:  Bug  |   Status:  assigned
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  QueryDict, upload,   | Triage Stage:  Accepted
  file   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anton-kazlouski):

 This is exactly what happened in my case. I have a code that modifies some
 attributes of `request.data` and then passes it to a serializer. At some
 point we started to notice `This QueryDict instance is immutable`
 exceptions in our logs. Thus, decided to use built-in method which you are
 referenced to. Once, replaced direct modifications  `request.data` with
 `request.data.copy()`,  `TypeError: cannot pickle '_io.BufferedRandom'
 object on...` started to araise.

 Replying to [comment:12 Dan Madere]:
 >
 > After trying it, I don't think either of these suggestions is workable,
 considering the nature of `TemporaryUploadedFile`. It has logic where the
 file is deleted as soon as it's closed. When copying/streaming the old
 file's content to the new one, we have a problem where the new file
 deletes itself immediately.
 >
 > I stepped back, and pondered why are people copying a `QueryDict`
 anyway, and what do they expect to happen to a `TemporaryUploadedFile`
 inside? [[https://docs.djangoproject.com/en/dev/ref/request-response
 /#querydict-objects]]:
 >
 > {{{
 > class QueryDict¶
 >
 > In an HttpRequest object, the GET and POST attributes are instances of
 django.http.QueryDict, a dictionary-like class customized to deal with
 multiple values for the same key. This is necessary because some HTML form
 elements, notably , pass multiple values for the same
 key.
 >
 > The QueryDicts at request.POST and request.GET will be immutable when
 accessed in a normal request/response cycle. To get a mutable version you
 need to use QueryDict.copy().
 > }}}
 >
 > That leads me to think that people are copying a `QueryDict` because
 it's a nice starting point to have all the query params organized, but
 they want to modify it, and pass to the template. Doing so would result in
 a `This QueryDict instance is immutable` exception, and the advice above,
 so they try to copy the `QueryDict` before modifying it.
 >
 > I propose we omit `TemporaryUploadedFile` values on deep copy of a
 `QueryDict`, and will open a PR for feedback.

-- 
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/01070185340151cb-c0673a4f-428b-43c4-83e5-48f42cc974da-00%40eu-central-1.amazonses.com.

Re: [Django] #34221: Plural-Forms in .po files break Django's translation precedence.

[Django]

#34221: Plural-Forms in .po files break Django's translation precedence.
-+-
 Reporter:  Stefano Parmesan |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  4.1
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  i18n | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Claude Paroz (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/0107018533d5e580-8c7ed340-e353-42fc-b598-be9502889267-00%40eu-central-1.amazonses.com.

[Django] #34221: Plural-Forms in .po files break Django's translation precedence.

[Django]

#34221: Plural-Forms in .po files break Django's translation precedence.
+
   Reporter:  Stefano Parmesan  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  4.1
   Severity:  Normal|   Keywords:  i18n
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 According to the
 [https://docs.djangoproject.com/en/4.1/topics/i18n/translation/#how-
 django-discovers-translations| documentation], Django reads translations
 from `LOCALE_PATHS` first, then from apps in `INSTALLED_APPS`, and then
 from its own folders.

 This behaviour breaks if the files in `LOCALE_PATHS` contain `Plural-
 Forms` while those found in `INSTALLED_APPS` don't.

 To test this behaviour I created a test project on github here:

 https://github.com/armisael/test-django-i18n-preference

 The project contains a .po file with `Plural-Forms` and a single
 translation that is also included in one of the dependencies. A single
 test checks which translation is picked.

 With the current configuration, the test fails by using the dependency
 translation. It passes if:
 1) the dependency is removed from `INSTALLED_APPS`; or if
 2) `Plural-Forms` is removed from the .po file.

 1) proves that i18n is correctly configured, and that the dependency
 translation is picked over the project one; 2) proves that `Plural-Forms`
 is involved in the bug.

-- 
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/0107018533cafaed-9a3640f5-8781-46f0-8c78-ad6232a94561-00%40eu-central-1.amazonses.com.

Re: [Django] #34220: Cannot import csrf_input_lazy from partially initialized module.

[Django]

#34220: Cannot import csrf_input_lazy from partially initialized module.
-+-
 Reporter:  thommy   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  Jinja2 TemplateView  | Triage Stage:  Accepted
  ImportError csrf_input_lazy|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by thommy):

 Hi Mariusz,

 thanks for the quick response. I'll give it a try.

 However it might take a couple of days to be sure because the problem
 happens so rarely.

 Best regards
 Thommy

-- 
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/0107018533b39787-07e1374e-87f3-4f39-8fad-1b4d1c7c6cd6-00%40eu-central-1.amazonses.com.