date:20150609

Re: [Django] #24914: Include basic permission mixins into Django

2015-06-09 Thread Django

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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
--+

Comment (by Rundll):

 What would be the recommend approach for stacking different permission
 mixins on a CBV?

 e.g. using LoginRequiredMixin and a PermissionRequiredMixin on the same
 view.

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

2015-06-09 Thread Django

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
---+--
 Reporter:  jmfederico |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 jmfederico):

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


Comment:

 A bit of debugging shows that when deleting an instance, django admin
 finds all the instances that are related to it in order to delete them as
 well.

 Problem is the dictionary created to store all the related instances to be
 deleted uses those same instances as keys in order to recursively find the
 whole tree.

 When GenericRelation has a related_query_name, it generates a dynamic
 "RelatedManager" class that is not hashable.

 This all happens in a NestedObjects class defined in
 django.contrib.admin.utils

 From there, I got lost.

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

Re: [Django] #24950: Add unicode_literals to startapp's template models.py

2015-06-09 Thread Django

#24950: Add unicode_literals to startapp's template models.py
-+-
 Reporter:  MarkusH  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  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 MarkusH):

 I'd like to think that, too, Tim. But I don't see that happening for the
 next year or two.

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

Re: [Django] #24914: Include basic permission mixins into Django

2015-06-09 Thread Django

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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):

 * owner:  raphaelm => MarkusH
 * needs_better_patch:  0 => 1


Comment:

 The current implementation has some drawbacks as pointed out on the PR.
 I'll fix the in aforementioned 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.876d7d811e6d2967db41fa216c79b8ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24963: Missing `seekable()` method in Files

2015-06-09 Thread Django

#24963: Missing `seekable()` method in Files
--+
Reporter: carsongee | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
Neither in django/core/files/utils.py or django/core/files/base.py::File
is the seekable method implemented. In python 3 this results in issues
when attempting to use python standard interfaces such as `bz2` or
`tarfile` and results in `AttributeError: 'File' object has no attribute
'seekable'` errors when using File class objects.

I'm not sure the best way to patch this though. The seekable property
isn't available in python2, but I think it can be duplicated in 2, by
checking if it has `seek`, `tell`, and `truncate` based on
https://docs.python.org/3/library/io.html#io.IOBase.seekable. I'm happy
to write the patch, but it would be worth knowing the preference for how
to fix it.

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-09 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by timgraham):

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


Comment:

 I couldn't reproduce this. We'll need more details such as a sample
 project that reproduces the error. I got a yellow "debug page" when
 `DEBUG=True` and a 500 error page when `DEBUG=False`. 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/065.97b02f1d687bc48d09109f8fc57872eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24769: Cast optparse verbosity argument to an integer for better backwards compatibility

2015-06-09 Thread Django

#24769: Cast optparse verbosity argument to an integer for better backwards
compatibility
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"76c526f80e43b0bf5199dfe33b1ce31e813fa2fb" 76c526f8]:
 {{{
 #!CommitTicketReference repository=""
 revision="76c526f80e43b0bf5199dfe33b1ce31e813fa2fb"
 [1.8.x] Fixed #24769 -- Cast optparse verbosity argument to an integer for
 better backwards compatibility.

 Using `BaseCommand.options_list` makes Django use the legacy optparse
 parser, which does not set the verbosity attribute correctly. Now the
 verbosity argument is always cast to int. Regression in 8568638 (#19973).

 Initial report and patch from blueyed.

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

Re: [Django] #24769: Cast optparse verbosity argument to an integer for better backwards compatibility

2015-06-09 Thread Django

#24769: Cast optparse verbosity argument to an integer for better backwards
compatibility
-+-
 Reporter:  blueyed  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a0047c6242fd48068eb444e0a58f7a5d2bc1bcd3" a0047c62]:
 {{{
 #!CommitTicketReference repository=""
 revision="a0047c6242fd48068eb444e0a58f7a5d2bc1bcd3"
 Fixed #24769 -- Cast optparse verbosity argument to an integer for better
 backwards compatibility.

 Using `BaseCommand.options_list` makes Django use the legacy optparse
 parser, which does not set the verbosity attribute correctly. Now the
 verbosity argument is always cast to int. Regression in 8568638 (#19973).

 Initial report and patch from blueyed.
 }}}

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2015-06-09 Thread Django

#21231: Limiting the number of variables and files that a POST request can 
contain
---+
 Reporter:  epandurski@…   |Owner:
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 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):

 * owner:  timo =>
 * 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/078.a2de96bee43f576b789bf999429e57ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

2015-06-09 Thread Django

#24944: Have password_reset pass extra_context to the email template rendering 
as
well
--+
 Reporter:  twelveeighty  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 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):

 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.auth
 * needs_tests:   => 0
 * needs_docs:   => 0
 * has_patch:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 I guess it's unlikely, but we'd have a small backwards compatibility issue
 if someone is using `extra_context` with a key that clashes with one in
 `opts`. For that reason, it might be better to use a separate parameter.

 There is also the idea of converting these views to class-based views in
 #17209 which might help here.

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

Re: [Django] #24959: date_interval_sql Implementations for Database Backends Do Not Handle Negative timedelta Objects Properly

2015-06-09 Thread Django

#24959: date_interval_sql Implementations for Database Backends Do Not Handle
Negative timedelta Objects Properly
-+-
 Reporter:  fredpalmer   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  date_interval_sql,   | Triage Stage:
  timedelta, F, orm  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by fredpalmer):

 Where it came up for me was a bulk `QuerySet.update()` using the `F()`
 object, e.g.:

 {{{
 ...
 delta = start_current - start_previous# Get the offset to add to
 filtered objects
 Event.objects.filter(**filters).update(start=F("start") + delta)
 }}}

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

Re: [Django] #24950: Add unicode_literals to startapp's template models.py

2015-06-09 Thread Django

#24950: Add unicode_literals to startapp's template models.py
-+-
 Reporter:  MarkusH  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  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 timgraham):

 There's a tentative implementation that needs I test I guess, although I
 have mixed feelings about whether to accept or reject this ticket as I'd
 like to think most new projects are using Python 3. :-) Of course, there
 may be existing projects starting new apps on Python 2.

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

Re: [Django] #24950: Add unicode_literals to startapp's template models.py

2015-06-09 Thread Django

#24950: Add unicode_literals to startapp's template models.py
-+-
 Reporter:  MarkusH  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  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):

 * Attachment "24950.diff" 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/065.64d0bb0370698133f68fd4c6cf0da26a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24947: Move admin changelist filters into a separate class (Mixin)

2015-06-09 Thread Django

#24947: Move admin changelist filters into a separate class (Mixin)
-+-
 Reporter:  nanuxbe  |Owner:  nanuxbe
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin changelist | Triage Stage:  Accepted
  filter |
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
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 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/065.b3a25e72a26b92da4e9c0bf1b46aa9d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24945: Add support for fuzzystrmatch to contrib.postgres

2015-06-09 Thread Django

#24945: Add support for fuzzystrmatch to contrib.postgres
--+
 Reporter:  dracos|Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  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:   => 1
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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.61d2c0c40e364bc6c3eeebfcc8eaff22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24903: Backport assertRaisesMessage fix

2015-06-09 Thread Django

#24903: Backport assertRaisesMessage fix
-+-
 Reporter:  MoritzS  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  test assert raises   | Triage Stage:  Accepted
  message|
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:"90c59db7a3e1c9725ed6e3683ef8beba4eb77333" 90c59db]:
 {{{
 #!CommitTicketReference repository=""
 revision="90c59db7a3e1c9725ed6e3683ef8beba4eb77333"
 Forwardported release notes for refs #24903.
 }}}

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

Re: [Django] #24903: Backport assertRaisesMessage fix

2015-06-09 Thread Django

#24903: Backport assertRaisesMessage fix
-+-
 Reporter:  MoritzS  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  test assert raises   | Triage Stage:  Accepted
  message|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8bc18ebf0fc7d82dda266812a1920d179c54223c" 8bc18eb]:
 {{{
 #!CommitTicketReference repository=""
 revision="8bc18ebf0fc7d82dda266812a1920d179c54223c"
 [1.8.x] Fixed #24903 -- Fixed assertRaisesMessage on Python 2.7.10.

 A regression in Python 2.7.10 rc1 wasn't reverted in the final
 release: https://bugs.python.org/issue24134

 Backport of two commits from master:
 * c2bc1cefdcbbf074408f4a4cace88b315cf9d652
 * e89c3a46035e9fe17c373a6c9cd63b9fd631d596
 }}}

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

Re: [Django] #24903: Backport assertRaisesMessage fix

2015-06-09 Thread Django

#24903: Backport assertRaisesMessage fix
-+-
 Reporter:  MoritzS  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  test assert raises   | Triage Stage:  Accepted
  message|
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:"207da07d5988dc80439a10810ba28fc1fba42fe3" 207da07]:
 {{{
 #!CommitTicketReference repository=""
 revision="207da07d5988dc80439a10810ba28fc1fba42fe3"
 [1.7.x] Fixed #24903 -- Fixed assertRaisesMessage on Python 2.7.10.

 A regression found in in Python 2.7.10 rc1 wasn't reverted for the final
 release: https://bugs.python.org/issue24134

 Backport of two commits from master:
 * c2bc1cefdcbbf074408f4a4cace88b315cf9d652
 * e89c3a46035e9fe17c373a6c9cd63b9fd631d596
 }}}

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

Re: [Django] #24931: 404 error for "Views by namespace admin" at Admin Docs

2015-06-09 Thread Django

#24931: 404 error for "Views by namespace admin" at Admin Docs
---+
 Reporter:  girishkumarkh  |Owner:  zedr
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Admin, AdminDocs   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by zedr):

 I believe the problem might be due to the fact that those views are
 actually methods of `django.contrib.admin.sites.AdminSite`.

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

Re: [Django] #24955: Allow BC and > 10000 years dates in Django ORM & forms

2015-06-09 Thread Django

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

Comment:

Since I had something to do with the boolean-evaluation-of-midnight
change, I can tell you that it met with very strong opposition, and in
fact it did take years (the bug was pointed out in 2012, and Python 3.5
which fixes it is still not out). You do not pull rugs from under your
users for no good reason; at least, Python and Django try hard not to.

I suspect the problem of year 0 and the choice of representation of BC
years would be enough to take down the suggestion -- one of the less-
often-quoted, but more valuable IMO, pieces of advice in the Zen of Python
is "in the face of ambiguity, resist the temptation to guess". But anyway,
there's not much use having that discussion here; if you want to change
Python, take it to the [https://bugs.python.org/ Python bug tracker] or
the [https://mail.python.org/mailman/listinfo/python-ideas python-ideas
mailing list]. If you can convince them, all the power to you, and Django
will add support for the feature.

However, until they do, there's no room for this in Django. Feel free to
reopen when Python support is available, and feel
free to implement wider date fields as 3rd-party packages until then.

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

Re: [Django] #24903: Backport assertRaisesMessage fix

2015-06-09 Thread Django

* has_patch: 0 => 1

Comment:

From bitdancer in #python-dev regarding merging of fixes to the release
branches of Python:
the way it is supposed to work is that issue like that get marked as
"release blocker" in the tracker, and the release manager makes sure they
are dealt with before cutting the release. Things do slip through the
cracks, though, and once they do the need to go into NEWS.

And as to why the Windows version contains the fix:
things being different between different builds of the release is a bug
in the release process. I'm not sure what happened there.

I'll fix this on 1.8 and 1.7. 1.4 isn't affected.
[https://github.com/django/django/pull/4841 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/065.8e5ee9f7d50f73bf235284e4ee0a63cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24933: Make FormSet management forms optional

2015-06-09 Thread Django

#24933: Make FormSet management forms optional
---+--
 Reporter:  patrys |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  master
 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
---+--
Description changed by timgraham:

Old description:

> They are only required if the form class used consists of nothing but
> checkbox fields. Dealing with management forms makes it unnecessarily
> hard to dynamically alter the list of forms in front-end and forgetting
> to render one will result in the `FormSet.__init__()` raising an
> exception.
>
> I've submitted a discussion to the mailing list but I'm creating a ticket
> here to provide a pull request for people to play with to make an
> informed decision.

New description:

 They are only required if the form class used consists of nothing but
 checkbox fields. Dealing with management forms makes it unnecessarily hard
 to dynamically alter the list of forms in front-end and forgetting to
 render one will result in the `FormSet.__init__()` raising an exception.

 I've [https://groups.google.com/d/topic/django-developers/skbT_7b-
 uFY/discussion submitted a discussion to the mailing list] but I'm
 creating a ticket here to provide a pull request for people to play with
 to make an informed decision.

--

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

Re: [Django] #24920: Database type NUMERIC with no parameters is not supported

2015-06-09 Thread Django

#24920: Database type NUMERIC with no parameters is not supported
-+-
 Reporter:  shaib|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Maybe you could raise the idea on the DevelopersMailingList. I think I'd
 prefer if we didn't need to add a new field, but if so, I'll propose the
 name `ImpreciseDecimalField`. Seems like a name like that might scare
 people away from using it though.

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

Re: [Django] #24959: date_interval_sql Implementations for Database Backends Do Not Handle Negative timedelta Objects Properly

2015-06-09 Thread Django

#24959: date_interval_sql Implementations for Database Backends Do Not Handle
Negative timedelta Objects Properly
-+-
 Reporter:  fredpalmer   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  date_interval_sql,   | Triage Stage:
  timedelta, F, orm  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 What does your QuerySet look like?

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

Re: [Django] #24858: Add support for get_foo_display() with ArrayField

2015-06-09 Thread Django

#24858: Add support for get_foo_display() with ArrayField
--+
 Reporter:  MounirMesselmeni  |Owner:  asser
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by asser):

 I think the usage in the description is slightly wrong; if specifying
 choices for an ArrayField the choices themselves should be lists:


 {{{#!python
 class Example(models.Model):
 CHOICES = (
 ([1, 2], 'value1'),
 ([3, 4], 'value2'),
 ([5], 'value3'),
 )
 multi_choices_array = ArrayField(
 base_field=models.IntegerField(),
 choices=CHOICES,
 )
 }}}

 To have an ArrayField that only accepts certain values on the base field,
 the usage would probably be:

 {{{#!python
 class Example(models.Model):
 CHOICES = (
 (1, 'value1'),
 (2, 'value2'),
 (3, 'value3'),
 )
 multi_choices_array = ArrayField(
 base_field=models.IntegerField(choices=CHOICES),
 )
 }}}

 Then supposedly you could add a forms.MultipleChoiceField to fill in the
 array's values?

 Neither of the two forms above currently work. I've managed to modify the
 postgres-specific code to handle the first case (choices being lists on
 the ArrayField) based on chedi's patch -- see
 https://github.com/asser/django/tree/ticket_24858 -- and am currently
 trying to figure out what goes wrong in the validation handling of the
 second case (choices on the base field).

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

Re: [Django] #24961: Show links to all auth docs from main index

2015-06-09 Thread Django

#24961: Show links to all auth docs from main index
--+
 Reporter:  danielr   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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:"b3f61f6e0840473cfd9485b95752aba572e9a9c9" b3f61f6e]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3f61f6e0840473cfd9485b95752aba572e9a9c9"
 [1.8.x] Fixed #24961 -- Added links to all auth docs pages from index.

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

Re: [Django] #24961: Show links to all auth docs from main index

2015-06-09 Thread Django

#24961: Show links to all auth docs from main index
--+
 Reporter:  danielr   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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:"fd0949181f993fb8a15c5b0128840f71ee1d7b0e" fd09491]:
 {{{
 #!CommitTicketReference repository=""
 revision="fd0949181f993fb8a15c5b0128840f71ee1d7b0e"
 Fixed #24961 -- Added links to all auth docs pages from index.
 }}}

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

Re: [Django] #24943: Update contributing tutorial to use virtualenv

2015-06-09 Thread Django

#24943: Update contributing tutorial to use virtualenv
-+-
 Reporter:  timgraham|Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 timgraham):

 Yes, we need to say that Python 3 is required. Notes for Windows are okay.

 Use your judgement on the caveats. I am not sure about attribution as it
 seems parts of thir chapter comes from other sources too. We usually give
 credits only in AUTHORS.

 Don't worry about the build failure. It's an occasional hiccup.

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

Re: [Django] #24961: Show links to all auth docs from main index

2015-06-09 Thread Django

#24961: Show links to all auth docs from main index
--+
 Reporter:  danielr   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 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 danielr):

 * has_patch:  0 => 1


Comment:

 Thanks @timgraham, updated and PR made:
 https://github.com/django/django/pull/4840

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

Re: [Django] #24961: Show links to all auth docs from main index

2015-06-09 Thread Django

#24961: Show links to all auth docs from main index
--+
 Reporter:  danielr   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 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):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I think your tentative patch is okay. You could also add
 `ref/contrib/auth`.

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

Re: [Django] #24943: Update contributing tutorial to use virtualenv

2015-06-09 Thread Django

#24943: Update contributing tutorial to use virtualenv
-+-
 Reporter:  timgraham|Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 giuliettamasina):

 Seems like one test set failed on last push due to some random hickup:

 http://djangoci.com/job/pull-requests-trusty/2071/database=mysql,label
 =trusty-pr,python=python3.4/console

 How can I retrigger the build without making any changes to the branch?

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

Re: [Django] #11642: Specify default namespace in urls.py

2015-06-09 Thread Django

#11642: Specify default namespace in urls.py
-+-
 Reporter:  mrmachine|Owner:  abki
 Type:  New feature  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  url namespace| Triage Stage:  Accepted
  default|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by knbk):

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


Comment:

 Fixed/superseded by #21927.

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

Re: [Django] #24914: Include basic permission mixins into Django

2015-06-09 Thread Django

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  raphaelm
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 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):

 Updated PR: https://github.com/django/django/pull/4836

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

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-09 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  1  |
---+
Changes (by alito):

 * Attachment "djangoquotepatch.txt" added.

 Two-character patch wrt github master as of 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/063.7dc9736bd54813d314e0b994d5991ef8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-09 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  1  |
---+
Changes (by alito):

 * Attachment "bugged.png" added.

 List with bug in it. Those two black entries have newlines in them

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

Re: [Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-09 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  1  |
---+
Changes (by alito):

 * Attachment "fixed.png" added.

 Same list fixed

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

[Django] #24962: Objects with primary keys containing newlines do not get links to being edited in the admin list view

2015-06-09 Thread Django

#24962: Objects with primary keys containing newlines do not get links to being
edited in the admin list view
---+
 Reporter:  alito  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  1
---+
 The admin list view of an object lists each object and does a

 reverse('admin:%s_%s_change' % (self.opts.app_label,
 self.opts.model_name), args=(quote(pk),),
 current_app=self.model_admin.admin_site.name)

 to assign a change url for each one, skipping the link if the reverse
 fails. The 'quote' function there escapes a whole bunch of characters so
 as not to confuse the url pattern matcher but it forgets to escape
 newline.

 Therefore, a model like this:

 class Name(models.Model):
name = models.TextField(primary_key=True)

 with:
 n = Name('John')
 n.save()
 o = Name('Have a \n newline')
 o.save()

 will list a link for John, but no link for 'Have a
 newline'

 (The bug actually is triggered in quite a few other places in admin but
 the list view is the easiest one to see. I've attached some screenshots
 that I prepared earlier)

 Change is a 2-character change to quote \n as well (attached)

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

[Django] #24961: Show links to all auth docs from main index

2015-06-09 Thread Django

#24961: Show links to all auth docs from main index
---+
Reporter: danielr| Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized |Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
There's a whole set of pages in the auth docs - about using the framework,
password management, and customizing - but these are not surfaced on the
main docs index page.

I have a branch
(https://github.com/danielroseman/django/tree/auth_docs_on_index) which
adds links to these in the same bold heading/pipe-separated details format
that we use for other subsections like Testing and Deployment, but that
would make this the only element under "Common Web application tools" to
use that format, which might look odd.

The alternative is to extract Authentication into its own main heading, as
we do with Internationalization, Performance, etc.

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

Re: [Django] #24961: Show links to all auth docs from main index

2015-06-09 Thread Django

#24961: Show links to all auth docs from main index
---+--
 Reporter:  danielr|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.8
 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 danielr):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 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/065.e500f760f5a3d2c6628097e9883b2ec2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24960: Blank pages due to {{ block.super }} (was: {{ block.super }} hides UnicodeDecodeErrors)

2015-06-09 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by srkunze):

 * keywords:  block.super UnicodeDecodeError => block.super blank pages


Old description:

> When using {{ block.super }}, it behaves like a normal variable which
> leads to the following issue:
>
> As soon as the block.super raises a UnicodeDecodeError, {{ block.super }}
> evaluates to an empty string.
>
> When using {{ block.super }} in cascading base templates, this frequently
> leads to blank pages which are hard to debug.

New description:

 When using {{ block.super }}, it behaves like a normal variable which
 leads to the following issue:

 As soon as the block.super raises (e.g.) a UnicodeDecodeError, {{
 block.super }} evaluates to an empty string.

 When using {{ block.super }} in cascading base templates, this frequently
 leads to blank pages which are hard to debug.

--

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

Re: [Django] #24960: {{ block.super }} hides UnicodeDecodeErrors (was: {{ block.super }} hides UnicodeEncodeErrors)

2015-06-09 Thread Django

#24960: {{ block.super }} hides UnicodeDecodeErrors
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super  | Triage Stage:
  UnicodeDecodeError |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by srkunze):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * keywords:  block.super UnicodeEncodeError => block.super
   UnicodeDecodeError
 * needs_docs:   => 0


Old description:

> When using {{ block.super }}, it behaves like a normal variable which
> leads to the following issue:
>
> As soon as the block.super raises a UnicodeEncodeError, {{ block.super }}
> evaluates to an empty string.
>
> When using {{ block.super }} in cascading base templates, this frequently
> leads to blank pages which are hard to debug.

New description:

 When using {{ block.super }}, it behaves like a normal variable which
 leads to the following issue:

 As soon as the block.super raises a UnicodeDecodeError, {{ block.super }}
 evaluates to an empty string.

 When using {{ block.super }} in cascading base templates, this frequently
 leads to blank pages which are hard to debug.

--

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

[Django] #24960: {{ block.super }} hides UnicodeEncodeErrors

2015-06-09 Thread Django

#24960: {{ block.super }} hides UnicodeEncodeErrors
--+
 Reporter:  srkunze   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Template  |Version:  master
  system  |
 Severity:  Normal|   Keywords:  block.super UnicodeEncodeError
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  1
--+
 When using {{ block.super }}, it behaves like a normal variable which
 leads to the following issue:

 As soon as the block.super raises a UnicodeEncodeError, {{ block.super }}
 evaluates to an empty string.

 When using {{ block.super }} in cascading base templates, this frequently
 leads to blank pages which are hard to debug.

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

Re: [Django] #24955: Allow BC and > 10000 years dates in Django ORM & forms

2015-06-09 Thread Django

#24955: Allow BC and > 1 years dates in Django ORM & forms
-+-
 Reporter:  BertrandBordage  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by BertrandBordage):

 Dependencies are not a problem, it’s their job to follow what’s new in
 each major CPython version, otherwise that would mean that nothing can be
 changed in Python. Recently, CPython changed the boolean evaluation of
 {{{time(0, 0, 0)}}} (see [https://bugs.python.org/issue13936 issue
 13936]), and it didn’t take years to make that. Similarly, in Django we
 don’t stick to bad choices just because a hundred libraries rely on it.

 About the year 0, that’s right, it’s mainly a matter of representation.
 The real problem is to decide whether we return 0 or -1 for year -1.
 Returning 0 is more logic if we want to do arithmetic with years, but it’s
 more misleading. The best solution IMO is to return -1 for year -1 and 1
 for year 1. This mean arithmetic with extracted years will be false, but
 not with dates. Since few people will use BC dates, and it’ll be more
 likely for historic purposes, and we usually don’t have precise dates BC
 (at least because of the mess of the multiple calendars that can lead to
 several years of error). So if someone makes calculus on extracted years
 (which isn’t recommended), it’ll be false, but this is an acceptable
 approximation.
 For info, PostgreSQL returns -1 when we extract the year of {{{0001-01-01
 BC}}}.

 The solution of using Astropy as answered in the stackoverflow issue is a
 total overkill.

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

Re: [Django] #24931: 404 error for "Views by namespace admin" at Admin Docs

2015-06-09 Thread Django

#24931: 404 error for "Views by namespace admin" at Admin Docs
---+
 Reporter:  girishkumarkh  |Owner:  zedr
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Admin, AdminDocs   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by zedr):

 I am able to reproduce this in 1.9.dev20150607202342.

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

Re: [Django] #24954: ManyToMany field fails with non-integer ids

2015-06-09 Thread Django

#24954: ManyToMany field fails with non-integer ids
--+--
 Reporter:  cloudOver |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  ManyToMany, UUID  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by cloudOver):

 * needs_better_patch:   => 0
 * component:  Database layer (models, ORM) => Migrations
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The problem refers to migration system. In some cases, Django migration
 didn't change types of foreign keys in ManyToMany.

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

45 matches

Mail list logo