Re: [Django] #29048: Add **extra_context arg to as_vendor methods in database functions

2018-02-06 Thread Django
#29048: Add **extra_context arg to as_vendor methods in database functions
-+-
 Reporter:  Matthew Pava |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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 Matthew Pava):

 Correct, Tim.

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


Re: [Django] #29116: Geometry editing issue when widget map_srid different from original value srid

2018-02-06 Thread Django
#29116: Geometry editing issue when widget map_srid different from original 
value
srid
-+--
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  2.0
 Severity:  Release blocker  |   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 Claude Paroz):

 * has_patch:  0 => 1


Comment:

 Added a possible resolution in [https://github.com/django/django/pull/9668
 this 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.94a9d9c80a6fa658b02c3af4260be1f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28814: Python 3.7 compatibility

2018-02-06 Thread Django
#28814: Python 3.7 compatibility
--+-
 Reporter:  Tim Graham|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
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:"0f0a07ac278dc2be6da81e519188f77e2a2a00cf" 0f0a07ac]:
 {{{
 #!CommitTicketReference repository=""
 revision="0f0a07ac278dc2be6da81e519188f77e2a2a00cf"
 Refs #28814 -- Fixed migrations crash with namespace packages on Python
 3.7.

 Due to https://bugs.python.org/issue32303.
 }}}

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


Re: [Django] #29098: Allow assertRedirects to handle regex matches.

2018-02-06 Thread Django
#29098: Allow assertRedirects to handle regex matches.
-+-
 Reporter:  Dan J Strohl |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Testing framework|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  unittest redirect| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 It sounds like you'd like `assertRedirects()` to be able to  do the
 `reverse()` itself. I don't see much advantage to that (complicating
 things by allowing `assertRedirects()` to take all the parameters of
 `reverse()`). If I misunderstood, can you clarify what API change you're
 proposing?

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


Re: [Django] #29052: test database setup can truncate non-test database if two database aliases point to the same database (was: running test command will truncate the data source database at some con

2018-02-06 Thread Django
#29052: test database setup can truncate non-test database if two database 
aliases
point to the same database
---+
 Reporter:  Muse   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  2.0
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 I haven't reproduced this, but the report makes sense.

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

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


Re: [Django] #29030: Make construction of "View on site" and "View Site" URLs consistent (was: contrib.sites incorrectly documents its use in django.contrib.admin "View Site" functionality)

2018-02-06 Thread Django
#29030: Make construction of "View on site" and "View Site" URLs consistent
-+-
 Reporter:  Kaleb Hornsby|Owner:
 Type:   |  ChiragMaliwal
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 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 Tim Graham):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted
 * component:  Documentation => contrib.admin
 * easy:  1 => 0


Comment:

 It might be feasible to make the links consistent, although backwards
 compatibility could be an issue.

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

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


Re: [Django] #29049: Add slicing notation to F expressions

2018-02-06 Thread Django
#29049: Add slicing notation to F expressions
-+-
 Reporter:  Matthew Pava |Owner:  Priyansh
 |  Saxena
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  slice F  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Priyansh Saxena):

 * has_patch:  0 => 1


Comment:

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


Re: [Django] #29082: Make the test client automatically encode JSON data

2018-02-06 Thread Django
#29082: Make the test client automatically encode JSON data
-+-
 Reporter:  Nick Sarbicki|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"47268242b071895dd269d97540e45dce646f675c" 47268242]:
 {{{
 #!CommitTicketReference repository=""
 revision="47268242b071895dd269d97540e45dce646f675c"
 Fixed #29082 -- Allowed the test client to encode JSON request data.
 }}}

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


Re: [Django] #28833: "Cache-Control: private" responses should not be cached by server

2018-02-06 Thread Django
#28833: "Cache-Control: private" responses should not be cached by server
-+-
 Reporter:  Nathan Vander Wilt   |Owner:
 Type:   |  shangdahao
  Cleanup/optimization   |   Status:  closed
Component:  HTTP handling|  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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"d968788b57f41b7def88046d1178fd2932a32a4e" d968788b]:
 {{{
 #!CommitTicketReference repository=""
 revision="d968788b57f41b7def88046d1178fd2932a32a4e"
 Fixed #28833 -- Prevented CacheMiddleware from caching responses with
 "Cache-Control: private".
 }}}

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


[Django] #29118: Uncertainty in proper signature for resolve_expression method

2018-02-06 Thread Django
#29118: Uncertainty in proper signature for resolve_expression method
-+-
   Reporter:  Raphael|  Owner:  nobody
  Gaschignard|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In {{{BaseExpression}}} we have the following:


 {{{
 def resolve_expression(self, query=None, allow_joins=True, reuse=None,
 summarize=False, for_save=False):
   ...
 }}}

 Here we have a couple default arguments. A decent number of callsites for
 this method only provide positional arguments. The {{{Exists}}} subclass
 assumes keyword-only arguments:

 {{{
 def resolve_expression(self, query=None, **kwargs):
 # As a performance optimization, remove ordering since EXISTS
 doesn't
 # care about it, just whether or not a row matches.
 self.queryset = self.queryset.order_by()
 return super(Exists, self).resolve_expression(query, **kwargs)
 }}}

 I've submitted a patch ([https://github.com/django/django/pull/9671]) that
 adds support for positional arguments for {{{Exists.resolve_expression}}},
 but perhaps the intention was for the base method to be keyword-only.

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

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


Re: [Django] #29115: Allow rendering of admin forms with Jinja2

2018-02-06 Thread Django
#29115: Allow rendering of admin forms with Jinja2
---+
 Reporter:  Joey Wilhelm   |Owner:  Joey Wilhelm
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 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 Carlton Gibson):

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


Re: [Django] #29115: Allow rendering of admin forms with Jinja2

2018-02-06 Thread Django
#29115: Allow rendering of admin forms with Jinja2
---+
 Reporter:  Joey Wilhelm   |Owner:  Joey Wilhelm
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 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 Carlton Gibson):

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


Re: [Django] #28933: Implement a range-based filter for Django Admin date_hierarchy

2018-02-06 Thread Django
#28933: Implement a range-based filter for Django Admin date_hierarchy
-+-
 Reporter:  hakib|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  date_hierarchy   | 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 Carlton Gibson):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch looks good!

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


Re: [Django] #29114: `django-admin shell` TypeError crash with ipython installed (was: Please make `django-admin shell` easier to use.)

2018-02-06 Thread Django
#29114: `django-admin shell` TypeError crash with ipython installed
-+-
 Reporter:  pannous  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  2.0
  commands)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  django-admin | Triage Stage:
  manage.py shell repl   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  Uncategorized => Core (Management commands)
 * type:  Uncategorized => Bug
 * resolution:  needsinfo => worksforme


Comment:

 For what it's worth, I couldn't reproduce the reported crash:
 {{{
 $ PYTHONPATH=. django-admin shell --settings=mysite.settings
 Python 3.5.5 (default, Feb  4 2018, 21:11:55)
 Type 'copyright', 'credits' or 'license' for more information
 IPython 6.2.1 -- An enhanced Interactive Python. Type '?' for help.

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


Re: [Django] #27999: Add test Client support for HTTP 307 and 308 redirects

2018-02-06 Thread Django
#27999: Add test Client support for HTTP 307 and 308 redirects
-+-
 Reporter:  anentropic   |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"272f685794de0b8dead220ee57b30e65c9aa097c" 272f685]:
 {{{
 #!CommitTicketReference repository=""
 revision="272f685794de0b8dead220ee57b30e65c9aa097c"
 Fixed #27999 -- Added test client support for HTTP 307 and 308 redirects.
 }}}

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