#21004: Deprecation Timeline: is_managed(): more info needed
-------------------------------------+-------------------------------------
Reporter: guettli | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: 1.5
Component: Documentation | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
It's a private API. If you've been using it, you're on your own; that's
the deal.
In Django 1.6 you cannot put a connection in managed mode, so
`is_managed()` always returns `False`. You'll probably end up replacing it
by `not transaction.get_autocommit()`. But more generally you need to
account for the new transaction management, which means you need to
understand what your code is trying to achieve and what functionality the
new transaction management API provides rather than just replace
`is_managed()` by something else.
I can suggest two resources:
- my talk at !DjangoCon in Warsaw gives lots of background on the design
of transaction management in Django (both the old one and the new one) —
see http://myks.org/en/talks/
- the transaction management docs contain fairly extensive information
about upgrading.
FYI I didn't remove the API outright because I knew it was used into the
wild. I made an extra effort to provide a deprecation path. However,
that's the extent of what I'm willing to do. Since it's a private API, its
purpose and use case weren't documented, and therefore I cannot provide
adequate advice in general.
--
Ticket URL: <https://code.djangoproject.com/ticket/21004#comment:1>
Django <https://code.djangoproject.com/>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.29ddbcb112778b5993870b97c9b2ede6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
