Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2017-01-17 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"ed251246cc6a22561217f38f7cf96598b22ff0fe" ed251246]:
 {{{
 #!CommitTicketReference repository=""
 revision="ed251246cc6a22561217f38f7cf96598b22ff0fe"
 Refs #25550 -- Removed support for direct assignment to the reverse side
 of a related set.
 }}}

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


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2016-12-17 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"e1f93e2b1e0da8cdacbb63167bab8732ffbab872" e1f93e2b]:
 {{{
 #!CommitTicketReference repository=""
 revision="e1f93e2b1e0da8cdacbb63167bab8732ffbab872"
 [1.10.x] Refs #25550 -- Removed a deprecated reverse assignment example in
 docs.

 Backport of 8dac9890a5941e7b59ea0ebebed400965941fe09 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/067.cbf7b0457fcd23dab88d1a8aa9c2bf41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2016-12-17 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"8dac9890a5941e7b59ea0ebebed400965941fe09" 8dac9890]:
 {{{
 #!CommitTicketReference repository=""
 revision="8dac9890a5941e7b59ea0ebebed400965941fe09"
 Refs #25550 -- Removed a deprecated reverse assignment example in docs.
 }}}

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


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2016-07-30 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"83b950e9ffd4904500bb9dcc9c7526f4d7899853" 83b950e9]:
 {{{
 #!CommitTicketReference repository=""
 revision="83b950e9ffd4904500bb9dcc9c7526f4d7899853"
 [1.10.x] Refs #25550 -- Corrected deprecation message for assigning M2M
 relations.

 Backport of 5fa4370543658aedd79dc554d8c52684d6c7cbca 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/067.c335e6e12be6b17a2c76d02528e4899f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2016-07-30 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 GitHub ):

 In [changeset:"5fa4370543658aedd79dc554d8c52684d6c7cbca" 5fa43705]:
 {{{
 #!CommitTicketReference repository=""
 revision="5fa4370543658aedd79dc554d8c52684d6c7cbca"
 Refs #25550 -- Corrected deprecation message for assigning M2M relations.
 }}}

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


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2015-10-30 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"c7b8d5d135980b267b089b7367e1796304415417" c7b8d5d]:
 {{{
 #!CommitTicketReference repository=""
 revision="c7b8d5d135980b267b089b7367e1796304415417"
 Refs #25550 -- Removed reverse related set assignment in selenium tests.
 }}}

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


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2015-10-27 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"9c5e272860c076736237d4b280c7c922c46ba273" 9c5e2728]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c5e272860c076736237d4b280c7c922c46ba273"
 Fixed #25550 -- Deprecated direct assignment to the reverse side of a
 related set.
 }}}

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


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2015-10-21 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

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


Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

2015-10-13 Thread Django
#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5413 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 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/067.28bb546176a3ff4e6cb5e192e13243f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.