Re: [Django] #20207: `ManyToManyField` with an unicode name fails to create an intermediary model.

2013-04-05 Thread Django 
#20207: `ManyToManyField` with an unicode name fails to create an intermediary
model.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"d04e8f8c7869b79a6f848a94bd51ce71223c2df2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d04e8f8c7869b79a6f848a94bd51ce71223c2df2"
 [1.5.x] Fixed #20207 -- Handle ManyToManyField with a unicode name
 correctly.

 Backport of 216580e034.
 }}}

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

Re: [Django] #20207: `ManyToManyField` with an unicode name fails to create an intermediary model.

2013-04-05 Thread Django 
#20207: `ManyToManyField` with an unicode name fails to create an intermediary
model.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"216580e03499e035b93283df00fcc03b346fef7b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="216580e03499e035b93283df00fcc03b346fef7b"
 Fixed #20207 -- Handle ManyToManyField with a unicode name correctly.
 }}}

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

Re: [Django] #20207: `ManyToManyField` with an unicode name fails to create an intermediary model.

2013-04-05 Thread Django 
#20207: `ManyToManyField` with an unicode name fails to create an intermediary
model.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 It'd be nice to backport the fix to 1.5.

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

Re: [Django] #20207: `ManyToManyField` with an unicode name fails to create an intermediary model.

2013-04-05 Thread Django 
#20207: `ManyToManyField` with an unicode name fails to create an intermediary
model.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Unreviewed => Ready for checkin


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

Re: [Django] #20207: `ManyToManyField` with an unicode name fails to create an intermediary model.

2013-04-05 Thread Django 
#20207: `ManyToManyField` with an unicode name fails to create an intermediary
model.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * has_patch:  0 => 1


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

[Django] #20207: `ManyToManyField` with an unicode name fails to create an intermediary model.

2013-04-05 Thread Django 
#20207: `ManyToManyField` with an unicode name fails to create an intermediary
model.
-+-
   Reporter:  charettes  |  Owner:  charettes
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:
   Severity:  Normal |  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 I encountered the following error when porting an app codebase to support
 both python 2 and 3.

 {{{
 #!python
 from __future__ import unicode_literals


 class Teacher(models.Model):
 students_ = models.ManyToManyField(Student, name='students')  # Here
 the name is a unicode string because of the future import.
 }}}

 Raises:

 {{{
 TypeError: Error when calling the metaclass bases
 type() argument 1 must be string, not unicode
 }}}

 The culprit is this
 
[https://github.com/django/django/blob/8d05e6c0c7fe35df86799fa2fdcdb6499a4f6312/django/db/models/fields/related.py#L1312
 line]. It should always be a `str`.

 This was not introduced by the codebase port to Python 3 and thus it's not
 a release blocker.

 Attaching a simple patch with tests in a few moments.

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