Re: [Django] #34250: Duplicate model names in M2M relationship causes RenameModel migration failure

[Django]

#34250: Duplicate model names in M2M relationship causes RenameModel migration
failure
-+
 Reporter:  Zac Miller   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  RenameModel  | 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):

 * component:  Database layer (models, ORM) => Migrations
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report.

-- 
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/010701859fb733c1-9be6a398-71df-4ed6-a9b9-3545bb95445d-00%40eu-central-1.amazonses.com.

Re: [Django] #34249: Custom RelatedManager documentation should have side tip on prefetch_related

[Django]

#34249: Custom RelatedManager documentation should have side tip on
prefetch_related
-+-
 Reporter:  Vaughn Koch  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  documentation| Triage Stage:
  relatedmanager custom  |  Unreviewed
  prefetch_related   |
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:   => duplicate
 * easy:  1 => 0


Comment:

 Duplicate of #30355.

-- 
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/010701859f299be4-78a330df-3453-4c14-9137-5a475bfa3aa2-00%40eu-central-1.amazonses.com.

Re: [Django] #31546: Replace Command.requires_system_checks = True by something like Command.required_system_checks = '__all__'

[Django]

#31546: Replace Command.requires_system_checks = True by something like
Command.required_system_checks = '__all__'
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  Core (Management |  Version:  dev
  commands)  |
 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:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"829f4d1448f7b40238b47592fc17061bf77b0f23" 829f4d1]:
 {{{
 #!CommitTicketReference repository=""
 revision="829f4d1448f7b40238b47592fc17061bf77b0f23"
 Refs #31546, Refs #34118 -- Corrected
 CommandTests.test_requires_system_checks_specific().

 System checks are never called without skip_checks=False. Moreover,
 called_once_with() is not a proper assertion and raise AttributeError
 on Python 3.12.
 }}}

-- 
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/010701859f1e5bdc-8ff9802c-e1c8-4c9c-99e5-65ed13b50a73-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

[Django]

#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"829f4d1448f7b40238b47592fc17061bf77b0f23" 829f4d1]:
 {{{
 #!CommitTicketReference repository=""
 revision="829f4d1448f7b40238b47592fc17061bf77b0f23"
 Refs #31546, Refs #34118 -- Corrected
 CommandTests.test_requires_system_checks_specific().

 System checks are never called without skip_checks=False. Moreover,
 called_once_with() is not a proper assertion and raise AttributeError
 on Python 3.12.
 }}}

-- 
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/010701859f1e5c0c-ef25f5bd-568e-408e-ab10-743630d20d03-00%40eu-central-1.amazonses.com.

Re: [Django] #33573: Add native async support to redis cache backend

[Django]

#33573: Add native async support to redis cache backend
-+-
 Reporter:  Christopher Bailey   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Cache system)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andrew Chen Wang):

 Makes sense. Thanks for the comment!

 You can take a look at a practically broken but conceptual implementation
 here: https://github.com/Andrew-Chen-Wang/django-async-redis/pull/6

 The repository itself is designed to be a django-redis replacement that I
 recently migrated from aioredis to redis-py; in regards to this convo, the
 places to look are `django_async_redis.client.core.py` and the test file
 `tests/test_core.py`

-- 
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/010701859d8ce4d6-e06757bf-771e-43ef-b01b-d109a1f5bd2a-00%40eu-central-1.amazonses.com.

[Django] #34250: Duplicate model names in M2M relationship causes RenameModel migration failure

[Django]

#34250: Duplicate model names in M2M relationship causes RenameModel migration
failure
-+-
   Reporter:  Zac|  Owner:  nobody
  Miller |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  RenameModel
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Example code is here: https://github.com/jzmiller1/edemo

 I have a django project with two apps, incidents and vault, that both have
 a model named Incident.  The vault Incident model has an M2M involving the
 incidents Incident model.  When the table is created for this M2M
 relationship the automatic field names are "from_incident_id" and
 "to_incident_id" since models have the same names.

 If I then try to use a RenameModel in a migration...


 {{{
 operations = [
 migrations.RenameModel(
 old_name='Incident',
 new_name='Folder',
 ),
 ]
 }}}


 it fails with this traceback:


 {{{
 Tracking file by folder pattern:  migrations
 Operations to perform:
   Apply all migrations: admin, auth, contenttypes, incidents, sessions,
 vault
 Running migrations:
   Applying vault.0002_rename_incident_folder...Traceback (most recent call
 last):
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/db/models/options.py", line 668, in get_field
 return self.fields_map[field_name]
 KeyError: 'incident'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/Users/zacmiller/Library/Application
 
Support/JetBrains/Toolbox/apps/PyCharm-P/ch-0/222.4345.23/PyCharm.app/Contents/plugins/python/helpers/pycharm/django_manage.py",
 line 52, in 
 run_command()
   File "/Users/zacmiller/Library/Application
 
Support/JetBrains/Toolbox/apps/PyCharm-P/ch-0/222.4345.23/PyCharm.app/Contents/plugins/python/helpers/pycharm/django_manage.py",
 line 46, in run_command
 run_module(manage_file, None, '__main__', True)
   File
 "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py",
 line 209, in run_module
 return _run_module_code(code, init_globals, run_name, mod_spec)
   File
 "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py",
 line 96, in _run_module_code
 _run_code(code, mod_globals, init_globals,
   File
 "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py",
 line 86, in _run_code
 exec(code, run_globals)
   File "/Users/zacmiller/PycharmProjects/edemo/manage.py", line 22, in
 
 main()
   File "/Users/zacmiller/PycharmProjects/edemo/manage.py", line 18, in
 main
 execute_from_command_line(sys.argv)
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/core/management/__init__.py", line 446, in
 execute_from_command_line
 utility.execute()
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/core/management/__init__.py", line 440, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/core/management/base.py", line 402, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/core/management/base.py", line 448, in execute
 output = self.handle(*args, **options)
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/core/management/base.py", line 96, in wrapped
 res = handle_func(*args, **kwargs)
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/core/management/commands/migrate.py", line 349, in
 handle
 post_migrate_state = executor.migrate(
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/db/migrations/executor.py", line 135, in migrate
 state = self._migrate_all_forwards(
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/db/migrations/executor.py", line 167, in
 _migrate_all_forwards
 state = self.apply_migration(
   File "/Users/zacmiller/PycharmProjects/virtualenvs/edemo/lib/python3.10
 /site-packages/django/db/migrations/executor.py", line 252, in
 apply_migration
 state = migration.apply(state, schema_editor)
   File 

Re: [Django] #34247: Cannot resolve operation dependencies

[Django]

#34247: Cannot resolve operation dependencies
+--
 Reporter:  Mike Schem  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  4.1
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham):

 We can't add code for a problem we don't fully understand, or else Django
 would quickly become a mess. Without a test, we can't be sure the problem
 is fixed and that the behavior won't regress in the future.

-- 
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/010701859d273048-ad7d7ab5-d77d-4240-bc8e-1265c06da258-00%40eu-central-1.amazonses.com.

[Django] #34249: Custom RelatedManager documentation should have side tip on prefetch_related

[Django]

#34249: Custom RelatedManager documentation should have side tip on
prefetch_related
-+-
   Reporter:  Vaughn |  Owner:  nobody
  Koch   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  4.1
  Documentation  |   Keywords:  documentation
   Severity:  Normal |  relatedmanager custom
   Triage Stage: |  prefetch_related
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 This Django documentation shows how to use a custom manager for reverse
 relations.

 https://docs.djangoproject.com/en/4.1/topics/db/queries/#using-custom-
 reverse-manager

 In the given example, this works well as-is, but if you prefetch_related
 the entries when you're querying Blog, Django will use the
 prefetch_related cache and ignore the custom manager.

 This behavior may/may not be desired, but the documentation could use a
 side tip about this condition, maybe in a 'Good to know' infobox.

 Also, separately: one flaw in the documented approach is that you have to
 explicitly use the custom manager when making a query - there doesn't seem
 to be a way to make the custom manager the default, which can cause issues
 if you forget to add it to all your calls.

-- 
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/010701859cda23a1-c334b1a6-730f-4187-a7c6-8832721b984b-00%40eu-central-1.amazonses.com.

Re: [Django] #34247: Cannot resolve operation dependencies

[Django]

#34247: Cannot resolve operation dependencies
+--
 Reporter:  Mike Schem  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  4.1
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Mike Schem):

 Replying to [comment:1 Tim Graham]:
 > You'll need to provide a minimal example to reproduce the issue so we
 can better understand it. The patch also requires a regression test based
 on that.

 Yea, I've tried to come up with something, but no luck so far.  I've only
 been able to get this to fail on my project, and like I said, it has
 hundreds of objects with complex relations.  The code does fix the problem
 and I see no downside to ordering proxy model and model creates at the top
 before the sort, any reason not to just accept the PR?

 Not sure if I'll be able to come up with something 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/010701859cce83fb-c68c44e1-5848-44bc-b6a8-a79ecda397c5-00%40eu-central-1.amazonses.com.

Re: [Django] #34234: Drop support for PROJ < 5.

[Django]

#34234: Drop support for PROJ < 5.
--+
 Reporter:  Mariusz Felisiak  |Owner:  Leo Tom
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  GIS   |  Version:  dev
 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/010701859c8bc3b5-d6483beb-b626-4eaf-9990-92e744bcc880-00%40eu-central-1.amazonses.com.

Re: [Django] #34248: sdist is missing tox.ini

[Django]

#34248: sdist is missing tox.ini
--+
 Reporter:  Marcel Telka  |Owner:  Leo Tom
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Packaging |  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:  1 |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/010701859c8b0f0b-92bc19b6-59ad-4077-a9cb-bba44070fadc-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

[Django]

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wkt, wkb | 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):

 * has_patch:  1 => 0
 * stage:  Ready for checkin => Accepted


Comment:

 Support for `srid` is missing.

-- 
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/010701859b4f0962-cc5ccb4a-8c58-414e-925a-00ef5640e0d0-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

[Django]

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wkt, wkb | 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 GitHub ):

 In [changeset:"552384fa977901dcbc33cc999cd38dddcdc0eef1" 552384fa]:
 {{{
 #!CommitTicketReference repository=""
 revision="552384fa977901dcbc33cc999cd38dddcdc0eef1"
 Refs #31014 -- Added FromWKB and FromWKT GIS database functions.

 Co-authored-by: Ondřej Böhm 
 Co-authored-by: Mariusz Felisiak 
 Co-authored-by: Sergey Fedoseev 
 }}}

-- 
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/010701859b4e6d3d-f5a8842c-8d5f-4750-adac-215182965dfc-00%40eu-central-1.amazonses.com.

Re: [Django] #34110: Add InMemoryStorage

[Django]

#34110: Add InMemoryStorage
-+-
 Reporter:  Josh |Owner:  Francesco
 |  Panico
 Type:  New feature  |   Status:  closed
Component:  File |  Version:  dev
  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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"72efd840a8cb6ee35a3732d8bb434e7361970b3c" 72efd840]:
 {{{
 #!CommitTicketReference repository=""
 revision="72efd840a8cb6ee35a3732d8bb434e7361970b3c"
 Fixed #34110 -- Added in-memory file storage.

 Thanks Paolo Melchiorre, Carlton Gibson, and Mariusz Felisiak for
 reviews.
 }}}

-- 
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/010701859b37c49e-54aee92a-2e28-4399-8bbb-a7aef4d06a89-00%40eu-central-1.amazonses.com.

Re: [Django] #27029: Make EmailValidator accept non-ASCII characters

[Django]

#27029: Make EmailValidator accept non-ASCII characters
-+-
 Reporter:  Ramin Farajpour  |Owner:  j-bernard
  Cami   |
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Other) |  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
-+-

Comment (by Carlton Gibson):

 The new PR seems ''OK™'' — for
 [https://docs.python.org/3.11/library/re.html#index-34 strings `\w`] is
 equivalent  to `[a-zA-Z0-9_]` with ASCII, and the unicode examples then
 pass.

 I worry slightly about bringing in a host of lookalike address
 vulnerabilities. 樂

 I think this needs a discussion to decide the way forward.

 1. I'm not convinced this is really a distinct issue to #26423.
 2. [The https://groups.google.com/d/topic/django-
 developers/ASBJ0ge2KYo/discussion mailing list discussion] was essentially
 unanimous to radically simplify here (rather than continue to tweak).

 Florian's comment:21 more or less sums it up:

 > ...propose to change the current email validator to just check if "@" is
 in the address and be done with it.

 We've said similar with URLValidator a number of times.

 I'm not sure we shouldn't (again) mark this as a duplicate of #26423, re-
 purpose that to simplify the validation, make sure ''How to customise
 validation'' shows the way forward clearly, and then close everything else
 in this area as `wontfix`. 樂

-- 
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/010701859b164686-31ff4c07-99ac-45f5-97eb-889bc6651743-00%40eu-central-1.amazonses.com.

Re: [Django] #34110: Add InMemoryStorage

[Django]

#34110: Add InMemoryStorage
-+-
 Reporter:  Josh |Owner:  Francesco
 |  Panico
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  dev
  uploads/storage|
 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 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/010701859b06e5d7-2068ca5a-954b-4c45-bbc5-7b574a2a4065-00%40eu-central-1.amazonses.com.

Re: [Django] #32409: TestCase async tests are not transaction-aware

[Django]

#32409: TestCase async tests are not transaction-aware
-+-
 Reporter:  David|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  TestCase, async, | Triage Stage:  Accepted
  transaction|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * owner:  KangDo96 => (none)
 * status:  assigned => new


-- 
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/010701859aec35ea-7851cd5d-7b57-4b9f-a7b4-83afbbed5332-00%40eu-central-1.amazonses.com.

Re: [Django] #32173: Autoreloader doesn't work with asyncio.

[Django]

#32173: Autoreloader doesn't work with asyncio.
+
 Reporter:  Carlton Gibson  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Utilities   |  Version:  3.1
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  async   | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Carlton Gibson):

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


Comment:

 Over time this has faded away — I think dropping Python 3.6 support when
 that went EOL was the key. (As `asyncio` moved from `get_event_loop` to
 `get_running_loop` the tendency to get a reference to an event loop from a
 different thread faded.)

 Auto-reloading works with the latest Daphne versions (>4). There may be
 lingering issues, but I think they can be resolved there.

-- 
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/010701859ae55b07-6a1db521-5b1e-45c1-9f3a-b26a0f03d647-00%40eu-central-1.amazonses.com.