Re: [Django] #23296: Invalid parameter to create() in RunPython example

2014-08-15 Thread Django 
#23296: Invalid parameter to create() in RunPython example
-+-
 Reporter:  areski   |Owner:  areski
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"28d97533246fa1051e416ff772a40190b1f30e4d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="28d97533246fa1051e416ff772a40190b1f30e4d"
 [1.7.x] Fixed #23296 -- Fixed RunPython code sample in Migration
 Operations.

 Backport of 7ca665c5f5 from master
 }}}

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

Re: [Django] #23296: Invalid parameter to create() in RunPython example

2014-08-15 Thread Django 
#23296: Invalid parameter to create() in RunPython example
-+-
 Reporter:  areski   |Owner:  areski
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7ca665c5f593953cba2cfeebd4f82acd38231031"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7ca665c5f593953cba2cfeebd4f82acd38231031"
 Fixed #23296 -- Fixed RunPython code sample in Migration Operations.
 }}}

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

Re: [Django] #23296: Invalid parameter to create() in RunPython example

2014-08-15 Thread Django 
#23296: Invalid parameter to create() in RunPython example
-+-
 Reporter:  areski   |Owner:  areski
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by collinanderson):

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


Comment:

 lgtm

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

Re: [Django] #23296: Invalid parameter to create() in RunPython example

2014-08-15 Thread Django 
#23296: Invalid parameter to create() in RunPython example
---+
 Reporter:  areski |Owner:  areski
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.7-rc-2
 Severity:  Normal |   Resolution:
 Keywords:  migrations | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by areski):

 * owner:  nobody => areski
 * status:  new => assigned


Comment:

 +1 for best practices!

 Here a [https://github.com/django/django/pull/3073 PR] if we are happy
 with this change

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

Re: [Django] #23296: Invalid parameter to create() in RunPython example (was: RunPython)

2014-08-15 Thread Django 
#23296: Invalid parameter to create() in RunPython example
---+
 Reporter:  areski |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-rc-2
 Severity:  Normal |   Resolution:
 Keywords:  migrations | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 If we are showing best practices, how about using
 `.using(db_alias).bulk_create(...)`?

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