Re: [Django] #21004: Deprecation Timeline: is_managed(): more info needed

[Django]

#21004: Deprecation Timeline: is_managed(): more info needed
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  wontfix
 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 aaugustin):

 Indeed you can keep using private APIs if you like pain.

 Or you can take advantage of the new public APIs like I said above:

 > You'll probably end up replacing it by not
 `transaction.get_autocommit()`.

--
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 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.d391771a6e4c96d940606b57b4ee5d31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21004: Deprecation Timeline: is_managed(): more info needed

[Django]

#21004: Deprecation Timeline: is_managed(): more info needed
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  wontfix
 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 guettli):

 You can use this, instead of `is_managed()`




 {{{
 transaction.get_connection().in_atomic_block
 }}}

--
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 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.385bc46fe54a8c8b5077467083b5f275%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21004: Deprecation Timeline: is_managed(): more info needed

[Django]

#21004: Deprecation Timeline: is_managed(): more info needed
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  wontfix
 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 guettli):

 Related: http://stackoverflow.com/questions/28338490/django-atom-force-
 transaction-raise-assertionerror-if-already-inside-a-tran

--
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 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.c3b3cff03855d4a9d6edbb2b0a215faf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21004: Deprecation Timeline: is_managed(): more info needed

[Django]

#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
-+-

Comment (by aaugustin):

 > The django users should know how to use is_managed() with future
 versions.

 The answer is very simple: don't, it's going to be removed.

-- 
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 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.93e6dde0a2ceded72211ea274825befe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21004: Deprecation Timeline: is_managed(): more info needed

[Django]

#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: 
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 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.