date:20160421

Re: [Django] #9976: Generic Foreign Keys should have a nice widget(ala raw_id)

2016-04-21 Thread Django

#9976: Generic Foreign Keys should have a nice widget(ala raw_id)
-+-
 Reporter:  Alex |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  design_ux| Triage Stage:  Accepted
  raw_id_fields  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by auvipy):

 * owner:  auvipy =>
 * status:  assigned => new


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

Re: [Django] #26528: Allow model/form Field validators kwarg to be any iterable

2016-04-21 Thread Django

#26528: Allow model/form Field validators kwarg to be any iterable
-+-
 Reporter:  loic |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Loïc Bistuer ):

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


Comment:

 In [changeset:"a885bca1dfe5905788ebb9f3a6557822ce3d9e9d" a885bca]:
 {{{
 #!CommitTicketReference repository=""
 revision="a885bca1dfe5905788ebb9f3a6557822ce3d9e9d"
 Fixed #26528 -- Allowed any iterable (e.g. tuple) as validators kwarg for
 form/model fields.
 }}}

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

Re: [Django] #26402: Allow relative paths in {% extends %} and {% include %} (was: relative path in {% extends "./../base.html" %})

2016-04-21 Thread Django

#26402: Allow relative paths in {% extends %} and {% include %}
-+-
 Reporter:  vb64 |Owner:  vb64
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  extends,include,template,relative  |
  path   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


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

Re: [Django] #25005: DateField, DateTimeField defaults needed even when auto_now=True

2016-04-21 Thread Django

#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  yakky
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField, TimeField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


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

Re: [Django] #20189: Collectstatic ignore list expansion on a per project basis

2016-04-21 Thread Django

#20189: Collectstatic ignore list expansion on a per project basis
-+-
 Reporter:  mark0978 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.bdcc611dbbb572686de4bbe5cfe7a57a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26528: Allow model/form Field validators kwarg to be any iterable (was: Fields' validators kwarg must be list.)

2016-04-21 Thread Django

#26528: Allow model/form Field validators kwarg to be any iterable
-+-
 Reporter:  loic |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Ready for checkin
 * component:  Uncategorized => Database layer (models, ORM)


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

Re: [Django] #22383: Add the required tag to the input fields which are required for database entry

2016-04-21 Thread Django

#22383: Add the required tag to the input fields which are required for database
entry
-+-
 Reporter:  abhishek.garg@…  |Owner:  Tim
 |  Graham 
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"ec6121693f112ae33b653b4364e812722d2eb567" ec61216]:
 {{{
 #!CommitTicketReference repository=""
 revision="ec6121693f112ae33b653b4364e812722d2eb567"
 Fixed #22383 -- Added support for HTML5 required attribute on required
 form fields.
 }}}

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

Re: [Django] #22383: Add the required tag to the input fields which are required for database entry

2016-04-21 Thread Django

#22383: Add the required tag to the input fields which are required for database
entry
-+-
 Reporter:  abhishek.garg@…  |Owner:
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.2d8970559c94828d37ea2876de09def0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26429: Name clash of merge migrations after squashing

2016-04-21 Thread Django

#26429: Name clash of merge migrations after squashing
-+-
 Reporter:  xgenadam |Owner:  rtpg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations   | Triage Stage:  Accepted
  merge clash|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Tests need to be fixed on the 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/066.f8bec5541ff8ae304ca7e39bd378a1cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26424: Allow URLValidator to skip schemes validation

2016-04-21 Thread Django

#26424: Allow URLValidator to skip schemes validation
--+
 Reporter:  timgraham |Owner:  burhan
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3b601dfc492ab9ef5f6b7dc580c5f32a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26521: CreateModel allows duplicate field names

2016-04-21 Thread Django

#26521: CreateModel allows duplicate field names
--+
 Reporter:  w0rp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MarkusH):

 * needs_better_patch:  0 => 1
 * version:  1.9 => 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/062.a1d6e8832eea15ed124e85a3b77d3e50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26521: CreateModel allows duplicate field names

2016-04-21 Thread Django

#26521: CreateModel allows duplicate field names
--+
 Reporter:  w0rp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.9
 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
--+

Comment (by MarkusH):

 I don't know if we really need this check, but if we do that, the manager
 names need to be unique and so do the base classes.

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

Re: [Django] #25139: ModelFormSet: allow swapping unique values

2016-04-21 Thread Django

#25139: ModelFormSet: allow swapping unique values
-+
 Reporter:  jdufresne|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by karyon):

 * cc: johannes.linke@… (added)


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

Re: [Django] #25139: ModelFormSet: allow swapping unique values

2016-04-21 Thread Django

#25139: ModelFormSet: allow swapping unique values
-+
 Reporter:  jdufresne|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by karyon):

 i hit the same bug, and i wasn't able to come up with a workaround that
 covers all the edge cases and that's not manually fiddling with that data
 dictionary and parsing the strings in there.

 any fix or pointers how to fix would be appreciated, as this is a user-
 facing bug that we have no acceptable workaround for right now.

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

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

2016-04-21 Thread Django

#26524: Change foreign key id list_display reference to display only the id
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin list_display   | Triage Stage:  Accepted
  changelist |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by krisys):

 I don't think this is specific to admin. @cristianocca and @tim, this
 behavior is documented in the following method - `_forward_fields_map` -
 https://github.com/django/django/blob/master/django/db/models/options.py#L469
 which specifically talks about the *_id fields as well.

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

Re: [Django] #26524: Change foreign key id list_display reference to display only the id

2016-04-21 Thread Django

Comment (by cristianocca):

Is there any specific reason that using 'fk_id' and just 'fk' causes both
to actually fetch the object? I'm expecting that if I access fk_id I am
actually accessing the attribute and not the relation.

It is the same case when working with instances:

{{{
b = B.objects.first()
print b.fk_id --> prints the id/value
print b.fk --> fetchs the relation and call the actual object __unicode__
}}}

So for me this working different when using the ModelAdmin and
display_list looks like a bug rather than a cleanup, you have two
properties performing the exact same action.

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

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

2016-04-21 Thread Django

#21379: class AbstractUser: validators should compile re with Unicode
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by tovmeod):

 I think we should allow non latin characters, users should be able to have
 usernames in their native language (hebrew, chinese etc)

 I propose we use unicode
 [https://docs.python.org/2/library/unicodedata.html#unicodedata.normalize
 normalization]

 unicodedata.normalize(input, 'NFKD')

 this could be used for usernames, passwords and other kind of input and
 should allow non latin.

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

Re: [Django] #26528: Fields' validators kwarg must be list.

2016-04-21 Thread Django

#26528: Fields' validators kwarg must be list.
-+-
 Reporter:  loic |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Uncategorized|  Version:  1.9
 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
-+-

Comment (by loic):

 PR https://github.com/django/django/pull/6486.

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

[Django] #26528: Fields' validators kwarg must be list.

2016-04-21 Thread Django

#26528: Fields' validators kwarg must be list.
+
   Reporter:  loic  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Uncategorized |Version:  1.9
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Requiring a `list` is a side effect of concatenating the `validators`
 kwarg with the field's `default_validators` which happens to be a `list`.

 Requiring a specific type of iterables is not very pythonic.

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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-04-21 Thread Django

#26526: Document QuerySet.latest() behavior for null values
--+
 Reporter:  int-ua|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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
--+
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/064.b81647288789d183c24cbe6dd5af28f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26527: HashedFilesMixin StaticFileStorage can't handle nested assets

2016-04-21 Thread Django

#26527: HashedFilesMixin StaticFileStorage can't handle nested assets
-+-
 Reporter:  joshblum |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 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 timgraham):

 For a test, I usually generate a patch and attach it to the ticket (unless
 you also plan to immediately start working on a fix, in which case a PR is
 fine).

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

Re: [Django] #13312: Add a way to customize the order_by() of null fields

2016-04-21 Thread Django

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  binary   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ordering, order_by,  | Triage Stage:  Accepted
  null   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by int-ua):

 AFAIU, it's possible in all main supported engines:

 ORDER BY IF(ISNULL(my_field),1,0),my_field
 [http://forums.mysql.com/read.php?10,208709,208927 in MySQL]
 [NULLS { FIRST | LAST }] [http://www.postgresql.org/docs/8.3/static
 /queries-order.html in both PostgreSQL]
 [http://stackoverflow.com/questions/18698311/oracle-order-null-last-by-
 default and Oracle]
 ORDER BY col1 IS NULL [http://stackoverflow.com/questions/12503120/how-to-
 do-nulls-last-in-sqlite in SqLite3]

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

Re: [Django] #13312: Add a way to customize the order_by() of null fields

2016-04-21 Thread Django

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  binary   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ordering, order_by,  | Triage Stage:  Accepted
  null   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by int-ua):

 * cc: serhiy.int@… (added)


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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-04-21 Thread Django

#26526: Document QuerySet.latest() behavior for null values
-+-
 Reporter:  int-ua   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by int-ua):

 Thank you, I've found related ticket about ordering NULL: #13312

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

Re: [Django] #26527: HashedFilesMixin StaticFileStorage can't handle nested assets

2016-04-21 Thread Django

#26527: HashedFilesMixin StaticFileStorage can't handle nested assets
-+-
 Reporter:  joshblum |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 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 joshblum):

 I think the problem is similar, however the discussions in those tickets
 lead to a slightly different solution and wouldn't solve the problem as
 I've described it. This is the first ticket I am submitted, to add a test
 should I submit a PR or just show an example?

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

Re: [Django] #26527: HashedFilesMixin StaticFileStorage can't handle nested assets (was: Bug in HashedFilesMixin StaticFileStorage)

2016-04-21 Thread Django

#26527: HashedFilesMixin StaticFileStorage can't handle nested assets
-+-
 Reporter:  joshblum |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * easy:  1 => 0


Comment:

 Possible related tickets or duplicates: #22353, #24452.

 If not, could you provide a test for Django's test suite that demonstrates
 the issue?

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

Re: [Django] #26527: Bug in HashedFilesMixin StaticFileStorage

2016-04-21 Thread Django

#26527: Bug in HashedFilesMixin StaticFileStorage
-+-
 Reporter:  joshblum |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by edmorley):

 * cc: emorley@… (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

Re: [Django] #26495: Saving StringIO using custom storage class may result in empty content written to file

2016-04-21 Thread Django

#26495: Saving StringIO using custom storage class may result in empty content
written to file
-+-
 Reporter:  m-novikov|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Ready for checkin


Comment:

 It's a bit odd to me that `bool(file)` is based on the file's name, but in
 light of that, I guess this makes sense.

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

[Django] #26527: Bug in HashedFilesMixin StaticFileStorage

2016-04-21 Thread Django

#26527: Bug in HashedFilesMixin StaticFileStorage
-+
 Reporter:  joshblum |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.staticfiles  |Version:  1.9
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 There seems to be a bug here if there are nested assets. For example, if i
 have `index.js` which references a partial `index.html`, if `index.js` is
 processed first, `index.html -> index..html`. Then if
 `index.html` is processed and rehashed (i.e. this file contains references
 to `index.png`), the `` inside of `index.js` in incorrect, since
 `index.html` was rehashed to account for it's own static assets. It seems
 like instead of just substituting the pattern here, we need to recursively
 rehash the file so the ordering is preserved. Thoughts?

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

Re: [Django] #26495: Saving StringIO using custom storage class may result in empty content written to file

2016-04-21 Thread Django

#26495: Saving StringIO using custom storage class may result in empty content
written to file
-+-
 Reporter:  m-novikov|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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:"4d1c229ee5cb210e8b592a8d9c87d4a66864328e" 4d1c229e]:
 {{{
 #!CommitTicketReference repository=""
 revision="4d1c229ee5cb210e8b592a8d9c87d4a66864328e"
 Fixed #26495 -- Added name arg to Storage.save()'s File wrapping.
 }}}

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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values (was: latest() QuerySet method should ignore null values)

2016-04-21 Thread Django

#26526: Document QuerySet.latest() behavior for null values
-+-
 Reporter:  int-ua   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0


Comment:

 Django simply delegates to the database's ordering of null values. I'm not
 sure if Django should also add filtering to exclude null values -- that
 seems a bit magical to me. However, you could raise the idea on the
 DevelopersMailingList. For now, I'll accept the ticket as a documentation
 improvement.

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

[Django] #26526: latest() QuerySet method should ignore null values

2016-04-21 Thread Django

#26526: latest() QuerySet method should ignore null values
--+
 Reporter:  int-ua|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 When sorting by date null values mean that date is unknown. Is there a
 reason to put them before any known date? Absence of date doesn't
 necessary mean an event will happen in the future, it means that the date
 is unknown. And word 'latest' suggests sorting by a known date.

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

Re: [Django] #26522: Non-determinstic crash in django.db.models.sql.Query.combine() (was: Bug in django.db.models.sql.Query.combine)

2016-04-21 Thread Django

#26522: Non-determinstic crash in django.db.models.sql.Query.combine()
-+-
 Reporter:  OleLaursen   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  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/068.a84e89e684fbe54c5e1f0ae314ebc72d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26521: CreateModel allows duplicate field names

2016-04-21 Thread Django

#26521: CreateModel allows duplicate field names
--+
 Reporter:  w0rp  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.9
 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):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #26429: Name clash of merge migrations after squashing

2016-04-21 Thread Django

#26429: Name clash of merge migrations after squashing
-+-
 Reporter:  xgenadam |Owner:  rtpg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations   | Triage Stage:  Accepted
  merge clash|
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/6485 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/066.083ddeb3df9158db58280370012ed2a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26455: Add lookups and database functions to check for valid geometries and repairing them.

2016-04-21 Thread Django

#26455: Add lookups and database functions to check for valid geometries and
repairing them.
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  isvalid, makevalid,  | Triage Stage:  Ready for
  valid, geometry|  checkin
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:"65006e0b0b5deb2e45c35975b103f0bb041c1e5c" 65006e0b]:
 {{{
 #!CommitTicketReference repository=""
 revision="65006e0b0b5deb2e45c35975b103f0bb041c1e5c"
 Refs #26455 -- Documented isvalid/makevalid in compatibility table.
 }}}

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

Re: [Django] #26524: Change foreign key id list_display reference to display only the id (was: Django Admin list_display - Unable to display foreign key id)

2016-04-21 Thread Django

#26524: Change foreign key id list_display reference to display only the id
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin list_display   | Triage Stage:  Accepted
  changelist |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Seems reasonable, though is backwards-incompatible -- hopefully not too
 many people will be affected by the change but I'd mention it in the
 release notes.

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

Re: [Django] #26429: Name clash of merge migrations after squashing

2016-04-21 Thread Django

#26429: Name clash of merge migrations after squashing
-+-
 Reporter:  xgenadam |Owner:  rtpg
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations   | Triage Stage:  Accepted
  merge clash|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by rtpg):

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


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

Re: [Django] #26522: Bug in django.db.models.sql.Query.combine

2016-04-21 Thread Django

Comment (by OleLaursen):

I've attached a test project. Run it with
{{{
cd combinebug
DJANGO_SETTINGS_MODULE=combinebug.settings PYTHONPATH=../Django-1.7.5:.
python combinebug/triggerbug.py
}}}

If it crashes, congrats, you've reproduced it. If not, try running it
multiple times.

I tested it with Python 2.7 and Django 1.7.5 and could reproduce the crash
and Python 3 and Django 1.9.4 and could also reproduce it.

1.6.2 seems to be working - that was the version I upgraded the whole
project from and it's been stable.

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

Re: [Django] #26522: Bug in django.db.models.sql.Query.combine

2016-04-21 Thread Django

#26522: Bug in django.db.models.sql.Query.combine
-+-
 Reporter:  OleLaursen   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by OleLaursen):

 * Attachment "combinebug.tar.gz" added.

 Test project for reproducing the problem

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

Re: [Django] #26525: Tutorial02 document issue

2016-04-21 Thread Django

#26525: Tutorial02 document issue
---+--
 Reporter:  edwardspbe |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.9
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timgraham):

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


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

Re: [Django] #26525: Tutorial02 document issue

2016-04-21 Thread Django

#26525: Tutorial02 document issue
---+--
 Reporter:  edwardspbe |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by niconoe):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Hmm, that seems to work for me.

 But using just polls seems like the old way to activate an app, prior to
 App loading refcator in Django 1.7:
 https://docs.djangoproject.com/en/1.9/releases/1.7/#app-loading-refactor.

 Since you refer to the Django 1.9 tutorial, may I ask you to check which
 version is running with:

 {{{
 $ python -c "import django; print(django.get_version())"
 }}}

 Thanks!

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

Re: [Django] #19665: 'Command' object has no attribute 'stderr'

2016-04-21 Thread Django

#19665: 'Command' object has no attribute 'stderr'
-+-
 Reporter:  stefankoegl  |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Mike, my guess is that your command overrode the `__init__` method of the
 command without calling the super `__init__`.

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

43 matches

Mail list logo