Re: [Django] #31700: Highlight destructive operations in makemigrations output

2024-01-04 Thread Django 
#31700: Highlight destructive operations in makemigrations output
-+---
 Reporter:  Tom Forbes   |Owner:  Amir Karimi
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  dev
 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 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/0107018cd8a11a84-e8a0c6e0-92fe-488a-bc55-cf831c132bef-00%40eu-central-1.amazonses.com.

Re: [Django] #35086: Add BoundedCircle support with SpatiaLite 5.1+

2024-01-04 Thread Django 
#35086: Add BoundedCircle support with SpatiaLite 5.1+
-+---
 Reporter:  David Smith  |Owner:  David Smith
 Type:  New feature  |   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 David Smith):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/17691 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/0107018cd88bd05f-f47fae56-5d92-43a3-9064-d513977bce74-00%40eu-central-1.amazonses.com.

Re: [Django] #35086: Add BoundedCircle support with SpatiaLite 5.1+

2024-01-04 Thread Django 
#35086: Add BoundedCircle support with SpatiaLite 5.1+
-+---
 Reporter:  David Smith  |Owner:  David Smith
 Type:  New feature  |   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 Mariusz Felisiak):

 * owner:  nobody => David Smith
 * status:  new => assigned
 * version:  5.0 => dev
 * type:  Uncategorized => New feature
 * 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/0107018cd88877ea-83ea1b44-e686-4392-b480-2f715a281cc2-00%40eu-central-1.amazonses.com.

[Django] #35086: Add BoundedCircle support with SpatiaLite 5.1+

2024-01-04 Thread Django 
#35086: Add BoundedCircle support with SpatiaLite 5.1+
-+
   Reporter:  David Smith|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  GIS|Version:  5.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  |
-+
 SpatiaLite added support for BoundedCircle (GEOSMinimumBoundingCircle)
 https://groups.google.com/g/spatialite-users/c/hAJ2SgitN4M

 GeoDjango already supports this on Oracle / PostGIS backends, we should
 allow support on SpatiaLite too.

-- 
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/0107018cd884b6de-7ce2be3b-14ea-494f-babe-8843d6262599-00%40eu-central-1.amazonses.com.

Re: [Django] #28404: Django admin empty_value/empty_value_display doesn't check for empty strings

2024-01-04 Thread Django 
#28404: Django admin empty_value/empty_value_display doesn't check for empty
strings
-+-
 Reporter:  Mark Koh |Owner:  Alexander
 |  Lazarević
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  empty value display  | Triage Stage:  Accepted
  admin charfield|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Sarah Boyce):

 Yes that's completely fine - enjoy!

-- 
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/0107018cd87fb2d7-22cb7382-e793-40f5-a3ed-70c95b7d6f14-00%40eu-central-1.amazonses.com.

Re: [Django] #28404: Django admin empty_value/empty_value_display doesn't check for empty strings

2024-01-04 Thread Django 
#28404: Django admin empty_value/empty_value_display doesn't check for empty
strings
-+-
 Reporter:  Mark Koh |Owner:  Alexander
 |  Lazarević
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  empty value display  | Triage Stage:  Accepted
  admin charfield|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Alexander Lazarević):

 * owner:  Nazarov Georgiy => Alexander Lazarević


Comment:

 After watching how to perform the "vulture method" in (1) I found this
 ticket.

 According to “Claiming” tickets'  I reassign this ticket to myself,
 because "... If a ticket has been assigned for weeks or months without any
 activity, it’s probably safe to reassign it to yourself." I hope that's
 ok.

 (1) https://fosstodon.org/@djangonaut@indieweb.social/111697455678403023

-- 
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/0107018cd68e7516-ac650256-1688-4a45-9d87-eb6d07060ea0-00%40eu-central-1.amazonses.com.

Re: [Django] #23321: Remove .mo files from the Django Git repository

2024-01-04 Thread Django 
#23321: Remove .mo files from the Django Git repository
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  dev
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 > Claude, question: in your PR, why are you favoring using msgfmt directly
 instead of using the Django compilemessages command (perhaps its internal
 compile_messages helper)?

 Probably because I estimated at the time we didn't need all bells and
 whistles from `compilemessages`. May be re-tested.

-- 
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/0107018cd6525e23-b504747e-ea07-450e-a8a4-a08effcd06da-00%40eu-central-1.amazonses.com.

Re: [Django] #35085: Import of PyATS breaks runserver reloader

2024-01-04 Thread Django 
#35085: Import of PyATS breaks runserver reloader
--+--
 Reporter:  Andy Norwood  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Utilities |  Version:  4.2
 Severity:  Normal|   Resolution:  needsinfo
 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 Andy Norwood):

 Thank you both for looking at this.

 I have contacted pyats support and pointed them to this ticket in the hope
 that they can share some insight that might help find a way forward.

-- 
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/0107018cd64aeb26-634abfff-17cf-4f16-a227-14ac013f5b5e-00%40eu-central-1.amazonses.com.

Re: [Django] #23321: Remove .mo files from the Django Git repository

2024-01-04 Thread Django 
#23321: Remove .mo files from the Django Git repository
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  dev
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Natalia Bidart):

 Hello everyone!

 As a Django release manager, and as someone who went thru the super
 painful process of incorporating translations from Transifex into Django
 5.0, I'd like to express a big +1 to remove the .mo files from the Django
 source. I agree with Ningú's counterpoints to Jannis Leidel's comment:7,
 and also I'd like to add:

 * Automatic compiling .po files when running tests would not add
 noticeable overhead since we could add a flag to use the existing ones if
 available (like `keep-db`, perhaps `on` by default)
 * Manually compiling .po files when developing Django and/or a from-repo
 version of Django *and* working on i18n related issues, feels natural to
 me (as long as we properly document this)
 * I haven't used Babel before but even assuming that this is a superior
 lib, I think that that migration should be treated and pushed forward as
 an orthogonal issue and not block improvements to our current (sometimes
 painful) translations machinery.

 Claude, question: in your PR, why are you favoring using `msgfmt` directly
 instead of using the Django `compilemessages` command (perhaps its
 internal `compile_messages` helper)?

-- 
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/0107018cd63d5bd0-b8fec5f1-2340-48fb-887a-bb151bb691e6-00%40eu-central-1.amazonses.com.

Re: [Django] #35085: Import of PyATS breaks runserver reloader

2024-01-04 Thread Django 
#35085: Import of PyATS breaks runserver reloader
--+--
 Reporter:  Andy Norwood  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Utilities |  Version:  4.2
 Severity:  Normal|   Resolution:  needsinfo
 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 Natalia Bidart):

 Thank you Tim, I double checked and while I did install `pyats` and added
 an adequate import to my `views.py`, due to a previous ticket triaging I
 had temporarily removed the corresponding `urls.py` from my Django project
 config :facepalm:.

 Andy, I agree with Tim's comment in that we would need to understand why
 `pyats` is providing modules that are not hashable. I searched a bit and I
 couldn't find concrete Python docs regarding modules and their
 hashability, though I did find
 [https://bytes.com/topic/python/answers/35503-modules-hashable this post].
 I'm inclined to suggest that `pyats` may need to ensure their modules are
 hashable, or explain why they are not/can not be so we can evaluate how
 niche vs common that reason is.

-- 
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/0107018cd62e2d72-e5d9a69f-d084-4226-b5b8-54d3cbf2c8a9-00%40eu-central-1.amazonses.com.

Re: [Django] #35085: Import of PyATS breaks runserver reloader (was: Import of PyATS breaks built-in server)

2024-01-04 Thread Django 
#35085: Import of PyATS breaks runserver reloader
--+--
 Reporter:  Andy Norwood  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Utilities |  Version:  4.2
 Severity:  Normal|   Resolution:  needsinfo
 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 Tim Graham):

 * resolution:  worksforme => needsinfo
 * type:  Uncategorized => Bug
 * component:  Uncategorized => Utilities


Comment:

 I had no trouble reproducing with `pip install pyats` and adding `from
 pyats.topology import Testbed` to the tutorial's `polls/views.py`.

 The question for me is why does pyats's `Configuration({})` class appear
 in `sys.modules`. Is this a proper behavior that could reasonably be
 expected in other packages. Since pyats is closed-source, we may need some
 details from pyats developers on this.

-- 
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/0107018cd6189d14-dbb78302-6216-4ce5-9854-ec37b94aef14-00%40eu-central-1.amazonses.com.

Re: [Django] #35085: Import of PyATS breaks built-in server

2024-01-04 Thread Django 
#35085: Import of PyATS breaks built-in server
---+--
 Reporter:  Andy Norwood   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:  worksforme
 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 Natalia Bidart):

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


Comment:

 Hello Andy, thanks for your report, though I'm having a hard time
 reproducing and thus understanding where Django is at fault.

 I have read the linked GH report and while I understand the change (adding
 `and isinstance(m, Hashable)` to `iter_modules_and_files`), I'm not being
 able to reproduce with a minimal Django app (and less so with a test
 case). I have tried installing the `pyats` dependency and adding the
 imports to `views.py` modules without being able to trigger any error.

 I'll be closing as `worksforme`, but please reopen if you can provide
 either a test case for the Django source (ideal), or a minimal pure Django
 project to reproduce otherwise.

 Thanks, Natalia.

-- 
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/0107018cd5f6c026-f6e6d530-4fb8-4fde-920f-7692ce03bffb-00%40eu-central-1.amazonses.com.

Re: [Django] #34981: Promote `--pair` and `--bisect` from `runtest.py` to be available as flags for the Django `test` command

2024-01-04 Thread Django 
#34981: Promote `--pair` and `--bisect` from `runtest.py` to be available as 
flags
for the Django `test` command
-+-
 Reporter:  Natalia Bidart   |Owner:  Sulabh
 |  Katila
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Hi Sulabh, tests and documentation are also required. Ideally, we wouldn't
 duplicate all the similar code in `runtests.py` as well.

-- 
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/0107018cd5d29e05-cf7f7c06-d921-4422-9237-6ea3a08f64d6-00%40eu-central-1.amazonses.com.

Re: [Django] #16281: ContentType.get_object_for_this_type using wrong database for creating object

2024-01-04 Thread Django 
#16281: ContentType.get_object_for_this_type using wrong database for creating
object
-+-
 Reporter:  tfrydrychewicz@… |Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  dev
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  contenttype, object  | Triage Stage:  Accepted
  get_object_for_this_type,  |
  database, multiple |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bcail):

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


Comment:

 Thanks, Mariusz - I updated docs and commented on the 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/0107018cd52e0869-5d87f6ab-b0bc-4d85-9ae3-e1083c192a3f-00%40eu-central-1.amazonses.com.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations

2024-01-04 Thread Django 
#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  Markus Holtermann  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Documentation  |  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
---+

Comment (by Natalia Bidart):

 Replying to [comment:5 HAMA Barhamou]:
 > I think that this tiket should cover a broader need.
 [https://forum.djangoproject.com/t/internal-organization-of-the-django-
 project/18490]

 Hey HAMA Barhamou, thank you for your interest in making Django better,
 but please note that as mentioned in the first comment from Tim, this
 ticket is intentionally scoped to only documenting the database migrations
 machinery.

-- 
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/0107018cd4bb14c8-57657106-cad0-4488-ad69-cf453a596b30-00%40eu-central-1.amazonses.com.

[Django] #35085: Import of PyATS breaks built-in server

2024-01-04 Thread Django 
#35085: Import of PyATS breaks built-in server
-+
   Reporter:  bonzo81|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  4.2
   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  |
-+
 When importing from the pyats library the development server fails to
 start with the following error. A more complete description of the issue
 in listed here
 https://github.com/CiscoTestAutomation/pyats/issues/120#issuecomment-892857620

 {{{
 Django version 4.2.8, using settings 'config.settings.local'
 Development server is running at http://0.0.0.0:8000/
 Using the Werkzeug debugger (https://werkzeug.palletsprojects.com/)
 Quit the server with CONTROL-C.
 Traceback (most recent call last):
   File "/app/manage.py", line 31, in 
 execute_from_command_line(sys.argv)
   File "/usr/local/lib/python3.11/site-
 packages/django/core/management/__init__.py", line 442, in
 execute_from_command_line
 utility.execute()
   File "/usr/local/lib/python3.11/site-
 packages/django/core/management/__init__.py", line 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/local/lib/python3.11/site-
 packages/django/core/management/base.py", line 412, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/usr/local/lib/python3.11/site-
 packages/django/core/management/base.py", line 458, in execute
 output = self.handle(*args, **options)
  ^
   File "/usr/local/lib/python3.11/site-
 packages/django_extensions/management/utils.py", line 62, in inner
 ret = func(self, *args, **kwargs)
   ^^^
   File "/usr/local/lib/python3.11/site-
 packages/django_extensions/management/commands/runserver_plus.py", line
 338, in handle
 self.inner_run(options)
   File "/usr/local/lib/python3.11/site-
 packages/django_extensions/management/commands/runserver_plus.py", line
 438, in inner_run
 self.extra_files |= set(filter(lambda filename:
 str(filename).endswith('.mo'), gen_filenames()))
 
   File "/usr/local/lib/python3.11/site-
 packages/django/utils/autoreload.py", line 304, in watched_files
 yield from iter_all_python_module_files()
^^
   File "/usr/local/lib/python3.11/site-
 packages/django/utils/autoreload.py", line 120, in
 iter_all_python_module_files
 return iter_modules_and_files(modules, frozenset(_error_files))

 TypeError: unhashable type: 'Configuration'
 }}}

 I have used the python manage.py shell to test the import and do not get
 an error after import
 {{{
 Python 3.11.7 (main, Dec 19 2023, 03:30:20) [GCC 12.2.0]
 Type 'copyright', 'credits' or 'license' for more information
 IPython 8.19.0 -- An enhanced Interactive Python. Type '?' for help.

 In [1]: from pyats.topology import Testbed, Device

 In [2]:

 }}}

 As an aside, I found a similar issue reported but with the Netmiko library
 instead https://github.com/ktbyers/netmiko/issues/1955

 I don't think this has been reported previously. I have limited Python
 skills but happy to assist where I can.

-- 
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/0107018cd4af28e6-13a7f2de-9270-456e-8a2f-e6286ab58762-00%40eu-central-1.amazonses.com.

Re: [Django] #35083: Make django.utils.decorators.method_decorator work with async functions.

2024-01-04 Thread Django 
#35083: Make django.utils.decorators.method_decorator work with async functions.
--+
 Reporter:  Drew Winstel  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Utilities |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:  async | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Drew Winstel):

 > Out of interest though, View standardly has a sync dispatch, which
 you've overridden here:

 Right, that's because strawberry's `dispatch()` is overridden as well:
 https://github.com/strawberry-
 graphql/strawberry/blob/main/strawberry/django/views.py#L266-L277

 > Likely off-topic but just for future context, Drew could you maybe
 briefly say how it comes up — I guess the Strawberry base class is async
 def all the way... or ... 樂?

 It does inherit from `django.views.generic.View`, but `dispatch()` is a
 clean break from the generic view's version.

 Strawberry's view includes the `@csrf_exempt()` decorator,  but we (at my
 day job) need `@ensure_csrf_cookie()` applied to that view because of
 weird node.js things that I don't even pretend to understand. :D

-- 
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/0107018cd4a5c693-409cc47c-a37d-4b4b-b17c-93ae112ff513-00%40eu-central-1.amazonses.com.

Re: [Django] #35084: Recommend reusable app module names use a `django_` prefix

2024-01-04 Thread Django 
#35084: Recommend reusable app module names use a `django_` prefix
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 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 Mariusz Felisiak ):

 In [changeset:"4818a139f74744b3e628bd097caf7f030108c23d" 4818a13]:
 {{{
 #!CommitTicketReference repository=""
 revision="4818a139f74744b3e628bd097caf7f030108c23d"
 [5.0.x] Fixed #35084 -- Recommended 'django_' prefix for reusable app
 modules.

 Backport of 05f124348e72c1dcf1f6e5de72ffc1f67ad9aa77 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/0107018cd4203915-06674275-8685-4b5d-a3a3-3ed9104b6e11-00%40eu-central-1.amazonses.com.

Re: [Django] #35084: Recommend reusable app module names use a `django_` prefix

2024-01-04 Thread Django 
#35084: Recommend reusable app module names use a `django_` prefix
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 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:"05f124348e72c1dcf1f6e5de72ffc1f67ad9aa77" 05f1243]:
 {{{
 #!CommitTicketReference repository=""
 revision="05f124348e72c1dcf1f6e5de72ffc1f67ad9aa77"
 Fixed #35084 -- Recommended 'django_' prefix for reusable app modules.
 }}}

-- 
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/0107018cd41fdce1-45eebeed-2e33-4aa0-87fd-9bebaa7452cb-00%40eu-central-1.amazonses.com.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations

2024-01-04 Thread Django 
#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  Markus Holtermann  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Documentation  |  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
---+

Comment (by HAMA Barhamou):

 I think that this tiket should cover a broader need.
 [https://forum.djangoproject.com/t/internal-organization-of-the-django-
 project/18490]

-- 
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/0107018cd40fc7e8-06f30e85-8436-4fd3-bfe3-a8d91e7b9ccc-00%40eu-central-1.amazonses.com.

Re: [Django] #35084: Recommend reusable app module names use a `django_` prefix

2024-01-04 Thread Django 
#35084: Recommend reusable app module names use a `django_` prefix
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  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 Mariusz Felisiak):

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


Comment:

 [https://github.com/django/django/pull/17677 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/0107018cd3b07297-9b22c36a-1fad-4613-922b-b5315141ad22-00%40eu-central-1.amazonses.com.

Re: [Django] #35083: Make django.utils.decorators.method_decorator work with async functions.

2024-01-04 Thread Django 
#35083: Make django.utils.decorators.method_decorator work with async functions.
--+
 Reporter:  Drew Winstel  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Utilities |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:  async | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Carlton Gibson):

 This ticket seems correct (`method_decorator` should work with `async def`
 methods).

 Out of interest though, `View` standardly has a sync `dispatch`, which
 you've overridden here:

 {{{
 class View1(View):
 @method_decorator(ensure_csrf_cookie)
 async def dispatch(
 self, request: HttpRequest, *args: Any, **kwargs: Any
 ) -> HttpResponse:
 return await super().dispatch(request, *args, **kwargs)

 }}}

 ... so would `method_decorator` work already for the ''usual cases'',
 decorating `dispatch`? 樂

 Likely off-topic but just for future context, Drew could you maybe briefly
 say how it comes up — I guess the Strawberry base class is `async def` all
 the way... or ... 樂?
 Thanks.

-- 
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/0107018cd395f5c6-30524fee-3327-4186-b9f6-fa5424842d18-00%40eu-central-1.amazonses.com.