#24352: Coercing ManyRelatedManager to string raises StopIteration exception
-------------------------------------+-------------------------------------
     Reporter:  rasca                |                    Owner:  gmunumel
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:  1.7
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by charettes):

 > For instance, if I have a change for 1.4 branch I need to go against
 master branch?

 Yes, but per our [https://docs.djangoproject.com/en/1.7/internals/release-
 process/#backwards-compatibility-policy backport policy] the
 `stable/1.4.x` would only receive security fixes and bug fixes for data
 loss issues.

 > I saw this documentation:
 ​https://docs.djangoproject.com/en/1.7/internals/contributing/committing-
 code/#committing-guidelines . If I want to backport my PR I need to change
 its title? The revision hash code is the code of the commit?

 The commit message will be changed by the committer through an automated
 script.

 You just have a to open a new pull request against master with your
 changes and a commit message following
 [https://docs.djangoproject.com/en/1.7/internals/contributing/committing-
 code/#committing-guidelines the guidelines].

 e.g `Fixed #24352 -- Prevented ManyRelatedManager from raising an
 exception when converted to string.`

--
Ticket URL: <https://code.djangoproject.com/ticket/24352#comment:7>
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/063.4ca45203df5940e852e0a03430692182%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to