Re: [Django] #35030: Make django.contrib.auth decorators work with async functions.

[Django]

#35030: Make django.contrib.auth decorators work with async functions.
--+
 Reporter:  Mike Lissner  |Owner:  Dingning
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  async, decorator  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Dingning):

 * needs_better_patch:  0 => 1


Comment:

 Here is my PR.
 https://github.com/django/django/pull/17621

-- 
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/0107018c7b52a61b-e4bd81cb-6d56-4177-b955-8d1f8237d380-00%40eu-central-1.amazonses.com.

Re: [Django] #35030: Make django.contrib.auth decorators work with async functions.

[Django]

#35030: Make django.contrib.auth decorators work with async functions.
--+
 Reporter:  Mike Lissner  |Owner:  Dingning
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  async, decorator  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Dingning):

 * needs_docs:  0 => 1
 * has_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/0107018c7b5080ea-ae0398f4-180a-421e-804d-0f11184c4322-00%40eu-central-1.amazonses.com.

Re: [Django] #35046: BlankChoiceIterator causes AttributeError for some existing packages and projects

[Django]

#35046: BlankChoiceIterator causes AttributeError for some existing packages and
projects
-+--
 Reporter:  Hazho Human  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  5.0
 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 Mariusz Felisiak):

 * cc: Nick Pope (added)
 * status:  new => closed
 * resolution:   => invalid
 * easy:  1 => 0


Comment:

 Replying to [ticket:35046 Hazho Human]:
 > The iterators should have method __len__ ...!

 That's not true, and there is no need to shout. According to
 [https://docs.python.org/3/glossary.html#term-iterator the Python's
 documentation]: ''"Iterators are required to have an `__iter__()`
 method...".'' and that's it so the `BlankChoiceIterator` implementation is
 correct. Also, `django-countries` doesn't support Django 4.2+, but there
 are efforts to change this, check out [https://github.com/SmileyChris
 /django-countries/pull/424 PR424] and [https://github.com/SmileyChris
 /django-countries/pull/438 PR 438].

-- 
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/0107018c7b400ad1-86debc9f-3243-4b37-9d8d-9098cd4476c6-00%40eu-central-1.amazonses.com.

Re: [Django] #35043: LogoutView.as_view() no longer works in 5.0

[Django]

#35043: LogoutView.as_view() no longer works in 5.0
-+--
 Reporter:  otonoton |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Tim Graham):

 If you would like to continue supporting logout via GET, you could copy
 `LogoutView` from Django 4.2 and use that in your project.

-- 
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/0107018c7adf96f5-43d06705-3e8e-4d78-badf-3a95d54b7d03-00%40eu-central-1.amazonses.com.

Re: [Django] #35046: BlankChoiceIterator causes AttributeError for some existing packages and projects

[Django]

#35046: BlankChoiceIterator causes AttributeError for some existing packages and
projects
---+--
 Reporter:  hazho  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by hazho):

 * cc: hazho (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/0107018c7a320e50-fd1d28f2-1268-4327-a6ee-736d641dacdf-00%40eu-central-1.amazonses.com.

[Django] #35046: BlankChoiceIterator causes AttributeError for some existing packages and projects

[Django]

#35046: BlankChoiceIterator causes AttributeError for some existing packages and
projects
--+
   Reporter:  hazho   |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Utilities   |Version:  5.0
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
 The iterators should have method __len__ ...!
 while this is not the case for (BlankChoiceIterator) in the current
 version of Django (5.0), this is why the following error raised:
 AttributeError: 'BlankChoiceIterator' object has no attribute '__len__'.
 Did you mean: '__le__'?


 to solve this, simply the BlankChoiceIterator class should have the method
 __len__ returning 0 as indication for emptiness.

 this is important because the package maintainer or project author may not
 find the way to update their code accordingly, for example the projects
 depend on django-countries would have the following trace raised (note
 there is no obvious indication where in the project code is the main
 causer that calls __len__ of BlankChoiceIterator objects:


 {{{

 Traceback (most recent call last):
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\core\handlers\exception.py", line 55, in inner
 response = get_response(request)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\core\handlers\base.py", line 197, in _get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
 
   File "C:\django_simple_payment_system\wallets\views.py", line 38, in
 index
 return render(request, template_path, context)
^^^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\shortcuts.py", line 24, in render
 content = loader.render_to_string(template_name, context, request,
 using=using)
 ^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\loader.py", line 62, in render_to_string
 return template.render(context, request)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\backends\django.py", line 61, in render
 return self.template.render(context)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 171, in render
 return self._render(context)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 163, in _render
 return self.nodelist.render(context)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 1000, in render
 return SafeString("".join([node.render_annotated(context) for node in
 self]))
^^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 961, in render_annotated
 return self.render(context)

   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\loader_tags.py", line 210, in render
 return template.render(context)

   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 173, in render
 return self._render(context)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 163, in _render
 return self.nodelist.render(context)
^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 1000, in render
 return SafeString("".join([node.render_annotated(context) for node in
 self]))
^^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 961, in render_annotated
 return self.render(context)

   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\defaulttags.py", line 241, in render
 nodelist.append(node.render_annotated(context))
 ^^
   File "C:\env_django_simple_payment_system\Lib\site-
 packages\django\template\base.py", line 961, in render_annotated
 return 

Re: [Django] #35043: LogoutView.as_view() no longer works in 5.0

[Django]

#35043: LogoutView.as_view() no longer works in 5.0
-+--
 Reporter:  otonoton |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  duplicate
 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 otonoton):

 How am I supposed to use LogoutView in urls.py now? i.e. without any other
 explicit view or template being defined (just like how it used to work)

-- 
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/0107018c7a02ab9f-fbdf73bd-398c-434d-9387-08bfaa0db8f8-00%40eu-central-1.amazonses.com.

Re: [Django] #35043: LogoutView.as_view() no longer works in 5.0

[Django]

#35043: LogoutView.as_view() no longer works in 5.0
-+--
 Reporter:  otonoton |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  duplicate
 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 Mariusz Felisiak):

 > Please don't just immediately close my ticket without at least
 attempting to communicate with me first.

 Then provide any details and follow our
 [https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
 features/#reporting-bugs bug reporting guidelines]. I don't think you've
 explained the issue in enough detail to confirm a bug in Django.

 > I don't consider it a duplicate because URL path entries do not specify
 a request method.

 What do you mean? How could we understand what you're trying to report?
 The ticket description shows that it's a duplicate. `LogoutView`
 implements `post()` and release notes describe precisely that you should
 use `POST` requests.

-- 
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/0107018c79993f04-77860ce9-0902-42be-8bf0-7dfc10afb64b-00%40eu-central-1.amazonses.com.

Re: [Django] #35043: LogoutView.as_view() no longer works in 5.0

[Django]

#35043: LogoutView.as_view() no longer works in 5.0
-+--
 Reporter:  otonoton |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  duplicate
 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 otonoton):

 I don't consider it a duplicate because URL path entries do not specify a
 request method. Please don't just immediately close my ticket without at
 least attempting to communicate with me first.

-- 
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/0107018c7938327b-c09a09ed-ac5b-44d6-ad55-7e4ce51b0fed-00%40eu-central-1.amazonses.com.

Re: [Django] #34411: Update obsolete GDAL API for DataSource handling

[Django]

#34411: Update obsolete GDAL API for DataSource handling
--+
 Reporter:  Claude Paroz  |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  GIS   |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz):

 * needs_better_patch:  1 => 0


Comment:

 Patch should be reviewable now, thanks to David Smith!

-- 
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/0107018c791ed31d-c96deb57-31f6-42cd-8e88-8f0b5abf3d3f-00%40eu-central-1.amazonses.com.

Re: [Django] #27055: Model form with geometry widgets has invalid html

[Django]

#27055: Model form with geometry widgets has invalid html
--+
 Reporter:  Antonis Christofides  |Owner:  (none)
 Type:  Bug   |   Status:  closed
Component:  GIS   |  Version:  dev
 Severity:  Normal|   Resolution:  fixed
 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 Claude Paroz):

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


Comment:

 The 

Re: [Django] #35041: DATA_UPLOAD_MAX_MEMORY_SIZE causes a confusing error when not an integer

[Django]

#35041: DATA_UPLOAD_MAX_MEMORY_SIZE causes a confusing error when not an integer
-+-
 Reporter:  Dimitar Tasev|Owner:  (none)
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  File |  Version:  4.2
  uploads/storage|
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * type:  Bug => Cleanup/optimization
 * has_patch:  1 => 0
 * resolution:   => wontfix


Comment:

 Thanks for the report, however we cannot add type checks for all settings.
 It's documented as integer and Django crashes when you use it incorrectly,
 so it's hard to miss.

 You can start a discussion on DevelopersMailingList if you don't agree.

-- 
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/0107018c788417be-3a39ba73-c970-42d7-8fcd-f87d2945ca26-00%40eu-central-1.amazonses.com.

Re: [Django] #35042: Queryset count does not work after union when annotations on aggregation are unused.

[Django]

#35042: Queryset count does not work after union when annotations on aggregation
are unused.
-+-
 Reporter:  Marcin   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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:"77278929c86168f075600d9d8c8e76a4792e672b" 7727892]:
 {{{
 #!CommitTicketReference repository=""
 revision="77278929c86168f075600d9d8c8e76a4792e672b"
 Fixed #35042 -- Fixed a count() crash on combined queries.

 Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.

 Thanks Marcin 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/0107018c78665ad9-e6085f79-a530-48ea-90b1-0bb1bdadc91b-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

[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:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Johnson):

 * cc: Adam Johnson (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/0107018c780557fc-4c442358-f882-4c29-abde-127b51453ca1-00%40eu-central-1.amazonses.com.

Re: [Django] #35033: EmailMessage repeats header if provided via the headers kwargs

[Django]

#35033: EmailMessage repeats header if provided via the headers kwargs
+
 Reporter:  Aalekh Patel|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Core (Mail) |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  email, headers  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by Adam Johnson):

 I agree that an exception sounds more correct, probably a ValueError, for
 any keys in headers that correspond to the explicit arguments like “to”.

 Natalia - no worries, I just saw this message after a number of other
 spammy ones 

-- 
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/0107018c77fe2de5-0d42edce-41a1-4e50-ac33-dedeb04fbe84-00%40eu-central-1.amazonses.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+
 Reporter:  Alex Rothberg  |Owner:  Bhuvnesh
 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:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Bhuvnesh):

 Hi Maarten!
 I don't think moving the model code to the new django app and setting the
 app_label to point to the old django app will work. The auto detector will
 see it as the deletion of model in the old app and creation of that model
 in the new app. This will also lead to losing all the data associated with
 that model.
 There is a [https://github.com/django/django/pull/16905 PR] open for
 addressing this issue which was working pretty good when the last time I
 tested it. I would suggest switching to that branch and try the same you
 suggested above (if possible) and it should work fine without any data
 loss. You can also have a look at the working of this new feature
 [https://github.com/DevilsAutumn/moving-model-demo#10-moving-model-by-
 just-changing-app_label-in-models-meta here.] Let me know if you face any
 problem.

-- 
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/0107018c77c7be82-04e81164-0b46-48e9-9f1e-ed451a0bd079-00%40eu-central-1.amazonses.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+
 Reporter:  Alex Rothberg  |Owner:  Bhuvnesh
 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:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Maarten Nieber):

 I've been struggling with this issue for a while, and came upon an
 extremely simple (though not perfect) solution. Things seem to keep
 working fine if I move the model code to a new django app, and set the
 "app_label" field in the Meta class to point to the old django app.

 I have two questions:

 - is this totally fine to do, and expected to work?
 - should we explain in the Docs that this is a simple and effective way to
 move a model?

-- 
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/0107018c77382296-82247ae5-e260-4cb3-96ca-e30da5c5eeb7-00%40eu-central-1.amazonses.com.