Re: [Django] #24462: Using .distinct().order_by() on a queryset produces unexpected results

[Django]

#24462: Using .distinct().order_by() on a queryset produces unexpected results
-+-
 Reporter:  trosos   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  distinct order_by| Triage Stage:
  subquery   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 I don't find changing the way .order_by().distinct().order_by() works a
 good idea. It *will* break a lot of existing code. For example, if you
 have automatic Meta ordering for model, what should
 `Human.objects.distinct('name').order_by('name', 'age')` return?

 Instead I think we need a new queryset operation to force Django use the
 current results as a subquery. There are various cases where you'd want
 this. Simplest one is
 `SomeModel.objects.order_by('posted')[0:10].subquery().order_by('-posted')`.

 This feature is likely pretty hard to implement correctly. Generating the
 SQL for the subquery is easy, but generating references to the subquery's
 available fields correctly is likely going to be hard.

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

Re: [Django] #21961: ForeignKey.on_delete supports database-level cascading options

[Django]

#21961: ForeignKey.on_delete supports database-level cascading options
-+-
 Reporter:  Xof  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by akaariai):

 I won't oppose an approach where checks framework will warn about
 dangerous behavior.

 For issue 1+2 mentioned by Shai in comment:5: we should disable signals
 when cascading along CASCADE_DB converted to normal CASCADE due to not
 having support for CASCADE by the backend.

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

Re: [Django] #24476: Allow using set_script_prefix as a contextmanager

[Django]

#24476: Allow using set_script_prefix as a contextmanager
-+-
 Reporter:  timgraham|Owner:  bpeschier
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (URLs)  |  Version:  master
 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 bpeschier):

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

Re: [Django] #21961: ForeignKey.on_delete supports database-level cascading options

[Django]

#21961: ForeignKey.on_delete supports database-level cascading options
-+-
 Reporter:  Xof  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by Suor):

 For me it actually ok that signals won't be called and some deletion
 propagation could be broken. It's kind of `.raw()` and `.extra()` if you
 mess with database you should handle all these things.

 My use case is using a database with another non-django app. So I can't
 rely on Djangos cascading.

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

Re: [Django] #23347: Add --dry-run to migrate

[Django]

#23347: Add --dry-run to migrate
-+--
 Reporter:  Naddiseo |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  1.7-rc-3
 Severity:  Normal   |   Resolution:  needsinfo
 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 Suor):

 This would be use full even without `RunPython` support. I used this
 feature a lot in south.

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

[Django] #24477: Error Outputting System Checks in django/core/management/base.py

[Django]

#24477: Error Outputting System Checks in django/core/management/base.py
--+--
 Reporter:  DavidMuller   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Core (System checks)  |Version:  1.8beta2
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 I'm trying to install celery==3.1.17 with django 1.8b2 (following the
 [http://celery.readthedocs.org/en/latest/django/first-steps-with-
 django.html#starting-the-worker-process celery + django install
 instructions)].

 I get the following TypeError when I try to launch a celery worker AND
 have unresolved system warnings:

 Trying to launch celery worker...
 {{{
 celery -A my_project worker -l info
 }}}

 yields ...

 {{{
   File "/usr/local/etc/virtualenvs/gears/local/lib/python2.7/site-
 packages/celery/fixups/django.py", line 162, in validate_models
 cmd.check()
   File "/usr/local/etc/virtualenvs/gears/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 530, in check
 self.stderr.write(msg, lambda x: x)
 TypeError: function takes exactly 1 argument (2 given)
 }}}

 It appears that Django is throwing a TypeError at
 
[https://github.com/django/django/blob/stable/1.8.x/django/core/management/base.py#L530
 this line in django/core/management/base.py]

 The problem "goes away" if I silence Django's system checks.

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

Re: [Django] #24394: Running tests fails when DATABASES['default'] = {}

[Django]

#24394: Running tests fails when DATABASES['default'] = {}
---+
 Reporter:  trecouvr   |Owner:  akulakov
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  test   | 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
 * has_patch:  0 => 1


Comment:

 I've reviewed the [https://github.com/django/django/pull/4308 pull
 request].

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

Re: [Django] #24139: The response reason phrases should evaluate lazily

[Django]

#24139: The response reason phrases should evaluate lazily
---+
 Reporter:  jdufresne  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  HTTP handling  |  Version:  master
 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:"d861f95c445652e4269c9015836d14dcf8b9a587" d861f95]:
 {{{
 #!CommitTicketReference repository=""
 revision="d861f95c445652e4269c9015836d14dcf8b9a587"
 Fixed #24139 -- Changed HttpResponse.reason_phrase to evaluate based on
 status_code.
 }}}

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

[Django] #24476: Allow using set_script_prefix as a contextmanager

[Django]

#24476: Allow using set_script_prefix as a contextmanager
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (URLs)   |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 It would be useful if `set_script_prefix()` could be used as a
 contextmanager in addition to as a regular function. That would allow
 replacing this redundant pattern in tests:

 {{{
 set_script_prefix('/beverages/')
 try:
 self.assertEqual(pf.get_absolute_url(), '/beverages/tea/')
 finally:
 clear_script_prefix()
 }}}

 with:

 {{{
 with set_script_prefix('/beverages/'):
 self.assertEqual(pf.get_absolute_url(), '/beverages/tea/')
 }}}

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

Re: [Django] #24226: Need to be able to change "(None)" display for null fields in Django admin

[Django]

#24226: Need to be able to change "(None)" display for null fields in Django 
admin
--+-
 Reporter:  meesterguyperson  |Owner:  gannetson
 Type:  New feature   |   Status:  closed
Component:  Generic views |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"a535e4acdcf1e75cc4d6302726876efc4c3a91c9" a535e4ac]:
 {{{
 #!CommitTicketReference repository=""
 revision="a535e4acdcf1e75cc4d6302726876efc4c3a91c9"
 Added myself to AUTHORS; refs #24226.
 }}}

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

Re: [Django] #24013: reverse() escapes unreserved characters supplied by prefix

[Django]

#24013: reverse() escapes unreserved characters supplied by prefix
-+-
 Reporter:  tgerdes  |Owner:  bpeschier
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ams2015  | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"c9f1a12925ef18d82b5f9683d589bb2c1e067650" c9f1a129]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9f1a12925ef18d82b5f9683d589bb2c1e067650"
 Fixed #24013 -- Fixed escaping of reverse() prefix.

 Prefix was treated as a part of the url pattern, which it is not.
 Improved tests to conform with RFC 3986 which allows certain
 characters in path segments without being escaped.
 }}}

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

Re: [Django] #24052: Document how to use models from other apps in RunPython

[Django]

#24052: Document how to use models from other apps in RunPython
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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.885c6708c54f7c6eef2e4781b14f4579%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22955: Admin: reloading clears filter_horizontal entries on Firefox (was: Admin: reloading clears filter_horizontal entries)

[Django]

#22955: Admin: reloading clears filter_horizontal entries on Firefox
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin| Triage Stage:  Accepted
  filter_horizontal reload   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I tested on Internet Explorer 9 and there's no problem there either. To
 me, this still seems like an issue that would be better addressed in
 Firefox itself so older versions of Django can benefit from the fix 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/067.381168f511cdb96423b036cc258fe3da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23463: Add Historical models note to upload_to/limit_choices_to sections

[Django]

#23463: Add Historical models note to upload_to/limit_choices_to sections
--+
 Reporter:  jpadilla  |Owner:  jpadilla
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 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):

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


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

Re: [Django] #23984: Document all available javascript_catalog's functions

[Django]

#23984: Document all available javascript_catalog's functions
--+
 Reporter:  bmispelon |Owner:
 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):

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

Re: [Django] #23814: Documented apps refactored out of Django

[Django]

#23814: Documented apps refactored out of Django
--+
 Reporter:  shabda|Owner:
 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):

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


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

Re: [Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
---+-
 Reporter:  gannetson  |Owner:  gannetson
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  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 timgraham):

 * version:  1.7 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 By settings, I think attributes of `ModelAdmin` and `AdminSite` would
 probably be the way to go.

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

Re: [Django] #24475: Add a new testconnections management command

[Django]

#24475: Add a new testconnections management command
-+-
 Reporter:  gannetson|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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):

 * component:  Core (System checks) => Core (Management commands)
 * version:  1.7 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a071c5023bb81e6a28bb25d523dc9e9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
---+--
 Reporter:  gannetson  |Owner:  gannetson
 Type:  Uncategorized  |   Status:  assigned
Component:  contrib.admin  |  Version:  1.7
 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 gannetson):

 * component:  Uncategorized => contrib.admin


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

Re: [Django] #24475: Add a new testconnections management command

[Django]

#24475: Add a new testconnections management command
-+-
 Reporter:  gannetson|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (System |  Version:  1.7
  checks)|
 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 gannetson):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Core (System checks)
 * 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/067.778f3765205bfec3f16abb213897b212%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24475: Add a new testconnections management command

[Django]

#24475: Add a new testconnections management command
---+
 Reporter:  gannetson  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Add a management command to check connection to mail server (without
 actually sending emails). This command can be extended later with testing
 other connections like caching ad maybe other settings.

 Here's a snippet that would test a smtp connection

 {{{
 from django.core import mail
 from django.core.mail.backends.smtp import EmailBackend

 def _check_mail_settings(self):
 connection = mail.get_connection()
 if isinstance(connection, EmailBackend):
 connection.open()
 }}}

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 timgraham):

 How would the tests be adapted? Where is the file closed in the first
 place?

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 aethemba):

 * cc: aethemba (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/066.46d75a0c7a553b95151f3aa9c52597a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24243: HashedFilesMixin doesn't handle file name fragments (thus the url template tag neither)

[Django]

#24243: HashedFilesMixin doesn't handle file name fragments (thus the url 
template
tag neither)
-+-
 Reporter:  atleta   |Owner:  atleta
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.7
 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 atleta):

 It does not. In this case, cache busting doesn't work.

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

Re: [Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
---+--
 Reporter:  gannetson  |Owner:  gannetson
 Type:  Uncategorized  |   Status:  assigned
Component:  Uncategorized  |  Version:  1.7
 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 gannetson):

 * owner:  nobody => gannetson
 * needs_better_patch:   => 0
 * status:  new => assigned
 * 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/067.bda3fce6981dccd458e65dd689a24592%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
---+
 Reporter:  gannetson  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Display value for null fields is '-' now. It would be nice if this is
 configurable in settings. '-' can be a bit hard to click if you use it in
 a list filter.

 This relates to changes made in
 https://code.djangoproject.com/ticket/24226.

 ​http://stackoverflow.com/questions/18324030/how-to-change-empty-
 changelist-value-in-django-admin
 ​http://stackoverflow.com/questions/28174881/in-the-django-admin-
 changelist-how-do-i-display-a-blank-space-instead-of-the-
 de?noredirect=1#comment44719629_28174881

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 aethemba):

 Would it be a problem to simply open image files (specifically
 ImageFieldFile objects) in the ___get___ function of the FileDescriptor
 object? Please see the "simple approach" attachment with a potential diff.

 Currently, it fixes the new regression test but approximately  31 other
 tests fail because they test for the "open-ness" of a file. However, these
 failing tests could be adapted if people agree to this solution. (See
 13750_tests.txt)

 I'm happy to hear people's suggestions or other feedback.

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 aethemba):

 * Attachment "13750_tests.txt" added.

 Results of tests with simple solution

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 aethemba):

 * Attachment "13750_simple_approach_solution.diff" added.

 Simple approach to solve #13750

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 aethemba):

 * Attachment "regression_13750.diff" added.

 Test to replicate the behaviour described in the ticket

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

Re: [Django] #24226: Need to be able to change "(None)" display for null fields in Django admin

[Django]

#24226: Need to be able to change "(None)" display for null fields in Django 
admin
--+-
 Reporter:  meesterguyperson  |Owner:  gannetson
 Type:  New feature   |   Status:  closed
Component:  Generic views |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"e4a578e70e2e48ab792e38c67579808a1def6024" e4a578e]:
 {{{
 #!CommitTicketReference repository=""
 revision="e4a578e70e2e48ab792e38c67579808a1def6024"
 Fixed #24226 -- Changed admin EMPTY_CHANGELIST_VALUE from (None) to -
 }}}

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

Re: [Django] #13750: ImageField accessing height or width and then data results in "I/O operation on closed file"

[Django]

#13750: ImageField accessing height or width and then data results in "I/O
operation on closed file"
--+
 Reporter:  ROsborne  |Owner:  aethemba
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  1.2
 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 aethemba):

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"fee18ce415cd817c20f64009600b0c7158353974" fee18ce]:
 {{{
 #!CommitTicketReference repository=""
 revision="fee18ce415cd817c20f64009600b0c7158353974"
 [1.8.x] Fixed #24364 -- Doc'ed that ManifestStaticFileStorage shouldn't be
 used during testing.

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b4d8b16e5109170614ba505e36f60c2ad64dafc2" b4d8b16]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4d8b16e5109170614ba505e36f60c2ad64dafc2"
 Fixed #24364 -- Doc'ed that ManifestStaticFileStorage shouldn't be used
 during testing.
 }}}

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"8084a68f7844ee61bcc5798c7557e2c3b4770b8a" 8084a68]:
 {{{
 #!CommitTicketReference repository=""
 revision="8084a68f7844ee61bcc5798c7557e2c3b4770b8a"
 [1.7.x] Fixed #24364 -- Doc'ed that ManifestStaticFileStorage shouldn't be
 used during testing.

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

Re: [Django] #12943: Unnamed captures are not passed to views in included URLconfs

[Django]

#12943: Unnamed captures are not passed to views in included URLconfs
-+-
 Reporter:  petri.lehtinen@… |Owner:  bpeschier
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ams2015  | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"f0f5212624d7a3edbf77126e0a3060d38db501e1" f0f5212]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0f5212624d7a3edbf77126e0a3060d38db501e1"
 Fixed #12943 -- Allowed unnamed arguments to be propagated in includes

 Propagated unnamed arguments as positional arguments into included
 URLconfs if no named arguments are defined. Positional and keyword
 arguments are never combined.
 }}}

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by aethemba):

 * Attachment "24364_revised.diff" added.

 Diff for ticket #24364

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

Re: [Django] #24468: signed_cookies backend crashes when switching from JSONSerializer to PickleSerializer

[Django]

#24468: signed_cookies backend crashes when switching from JSONSerializer to
PickleSerializer
-+-
 Reporter:  Drife59  |Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.sessions |  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  PickleSerializer | Triage Stage:  Accepted
  signed_cookies |
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:"8a481498aa995b435d8c3a0c90d7d917046f59b3" 8a481498]:
 {{{
 #!CommitTicketReference repository=""
 revision="8a481498aa995b435d8c3a0c90d7d917046f59b3"
 Fixed #24468 -- Made signed cookies cache backend resilient to unpickling
 exceptions.
 }}}

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by aethemba):

 * Attachment "24364.diff" added.

 Diff file for ticket 24364

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by aethemba):

 * cc: aethemba (added)
 * has_patch:  0 => 1


Comment:

 This is my first commit to Django so please bear with me.

 I wrote a simple piece of documentation for this issue. I'm attaching the
 diff file to this ticket.

 Furthermore, I've sent a pull request to Django's stable/1.7.x branch.

 I'm eager to hear if I've done all steps correctly.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.697393d0ddc7830f27b623af9dbd7fca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24226: Need to be able to change "(None)" display for null fields in Django admin

[Django]

#24226: Need to be able to change "(None)" display for null fields in Django 
admin
--+-
 Reporter:  meesterguyperson  |Owner:  gannetson
 Type:  New feature   |   Status:  assigned
Component:  Generic views |  Version:  1.7
 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 gannetson):

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

Re: [Django] #24364: Document that ManifestStaticFilesStorage shouldn't be used during testing

[Django]

#24364: Document that ManifestStaticFilesStorage shouldn't be used during 
testing
--+
 Reporter:  natevw|Owner:  aethemba
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 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 aethemba):

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

Re: [Django] #12943: Unnamed captures are not passed to views in included URLconfs

[Django]

#12943: Unnamed captures are not passed to views in included URLconfs
-+-
 Reporter:  petri.lehtinen@… |Owner:  bpeschier
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:  ams2015  | 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 knbk):

 * needs_tests:  1 => 0
 * 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/080.a3e1c94ce4933f224b02958fded7ea1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24473: Hstore Case Insensitive Lookups

[Django]

#24473: Hstore Case Insensitive Lookups
--+--
 Reporter:  DavidMuller   |  Owner:
 Type:  Uncategorized | Status:  new
Component:  contrib.postgres  |Version:  1.8beta2
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 The docs on
 [https://docs.djangoproject.com/en/1.8/ref/contrib/postgres/fields
 /#querying-hstorefield querying Hstore] mention 'contains' look ups, but
 no 'icontains' lookups are mentioned.

 Is it not possible to query over hstore in a case insensitive manner?
 This seems like a very basic (and very useful) feature.

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

Re: [Django] #23986: Collectstatic --clear fails if the static dir doesn't exist yet

[Django]

#23986: Collectstatic --clear fails if the static dir doesn't exist yet
-+-
 Reporter:  mvantellingen|Owner:
 |  sztrovacsek
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.7
 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:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"389baccac5fce72c67cfed7a6ebcf9273edf9282" 389bacca]:
 {{{
 #!CommitTicketReference repository=""
 revision="389baccac5fce72c67cfed7a6ebcf9273edf9282"
 Fixed staticfiles test on Windows; refs #23986.
 }}}

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

Re: [Django] #24468: signed_cookies backend crashes when switching from JSONSerializer to PickleSerializer (was: signed_cookies and PickleSerializer seems incompatible.)

[Django]

#24468: signed_cookies backend crashes when switching from JSONSerializer to
PickleSerializer
-+-
 Reporter:  Drife59  |Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.sessions |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  PickleSerializer | Triage Stage:  Accepted
  signed_cookies |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => assigned
 * component:  Uncategorized => contrib.sessions
 * owner:  nobody => timgraham
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I think you had an existing session created with the `JSONSerializer` and
 are trying to load it with `PickleSerializer`. We can modify the signed
 cookies backend to silently create a new session in this case. This is
 similar to the behavior of other backends.

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

Re: [Django] #24467: jQuery error in Django admin site when use "get_prepopulated_fields"

[Django]

#24467: jQuery error in Django admin site when use "get_prepopulated_fields"
-+-
 Reporter:  1st  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  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 charettes):

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

Re: [Django] #16213: View collections in the generic views

[Django]

#16213: View collections in the generic views
---+
 Reporter:  hvdklauw   |Owner:  auvipy
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  dceu2011   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Description changed by auvipy:

Old description:

> A class that handles multiple class based views and also handles the urls
> for it.
>
> A base class that just handles the urls for the views.
> And for instance a Crud collection does basic crud

New description:

 A class that handles multiple class based views and also handles the urls
 for it.

 A base class that just handles the urls for the views.
 And for instance a Crud collection does basic crud

 """
 Note that REST framework has an existing implementation of view
 collections...
 ​http://django-rest-framework.org/tutorial/6-viewsets-and-routers.html
 ​http://django-rest-framework.org/api-guide/viewsets.html
 ​http://django-rest-framework.org/api-guide/routers.html
 If Django works towards a view collection implementation, probably worth
 reviewing that approach too.

 """

--

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

Re: [Django] #16256: More class based views: formsets derived generic views

[Django]

#16256: More class based views: formsets derived generic views
---+
 Reporter:  rasca  |Owner:  rasca
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by auvipy):

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


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

Re: [Django] #17569: i18n_patterns and set_language

[Django]

#17569: i18n_patterns and set_language
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Uncategorized|  Version:
 |  1.4-alpha-1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  i18n_patterns,   | Triage Stage:
  set_language   |  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * resolution:  needsinfo => duplicate


Comment:

 Set as duplicate for #24122

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

Re: [Django] #24122: Redirect to translated url after setting language

[Django]

#24122: Redirect to translated url after setting language
-+-
 Reporter:  gbdlin   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  set_language,| Triage Stage:  Accepted
  i18n_patterns, translating urls|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * version:  1.7 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 https://github.com/django/django/pull/4303

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

Re: [Django] #24469: forms, form fields and media are escaped wrongfully in non django templates

[Django]

#24469: forms, form fields and media are escaped wrongfully in non django 
templates
-+-
 Reporter:  MoritzS  |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.8beta2
 Severity:  Normal   |   Resolution:
 Keywords:  forms fields media   | Triage Stage:
  escape template jinja2 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Thanks a lot for doing this research. That's the reason I suspected, but I
 wasn't sure.

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

Re: [Django] #16213: View collections in the generic views

[Django]

#16213: View collections in the generic views
---+
 Reporter:  hvdklauw   |Owner:  auvipy
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  dceu2011   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by auvipy):

 * owner:  hvdklauw => auvipy
 * status:  new => assigned
 * version:  1.3 => 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/066.395cedebeff0d71dc390b203076633a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16213: View collections in the generic views

[Django]

#16213: View collections in the generic views
---+
 Reporter:  hvdklauw   |Owner:  hvdklauw
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords:  dceu2011   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by auvipy):

 @tomchristie you idea is nice! i would love to have that on django proper!

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

Re: [Django] #24463: Remove old functionality from `HttpRequest`

[Django]

#24463: Remove old functionality from `HttpRequest`
-+-
 Reporter:  rednaw   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  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
-+-
Changes (by rednaw):

 * has_patch:  0 => 1


Comment:

 Here it is:
 https://github.com/django/django/pull/4290

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

Re: [Django] #24472: Define internal types explicitly for related fields

[Django]

#24472: Define internal types explicitly for related fields
-+-
 Reporter:  coldmind |Owner:  coldmind
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

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


Comment:

 https://github.com/django/django/pull/4296

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

Re: [Django] #24463: Remove old functionality from `HttpRequest`

[Django]

#24463: Remove old functionality from `HttpRequest`
-+-
 Reporter:  rednaw   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 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 rednaw):

 Ok, in that case I guess we should keep WSGIRequest and HttpRequest
 separate. That might also make sense in the case WSGI might ever be
 replaced or alternatives arise.

 Back to the core issue here: could we remove the checking of the
 environment variable in `_get_scheme()` in `HttpRequest`?

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

Re: [Django] #24463: Remove old functionality from `HttpRequest`

[Django]

#24463: Remove old functionality from `HttpRequest`
-+-
 Reporter:  rednaw   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 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 collinanderson):

 I'm looking at `HttpRequest.__init__`. By default, you'll get an error if
 you try to add or remove items from the request.GET and request.POST dict-
 likes.

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

Re: [Django] #24463: Remove old functionality from `HttpRequest`

[Django]

#24463: Remove old functionality from `HttpRequest`
-+-
 Reporter:  rednaw   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 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 rednaw):

 If you have code running outside a request that needs a request object, it
 seems to me like a flaw in the design of the program. However, I can
 understand there are people who have this anyway, and we should try to not
 break their code by changing this.

 About the mutability of GET and POST, what do you mean by that? In Python,
 any property of a class is mutable.

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