Re: [Django] #29464: Move collectstatic post processing messages to verbosity 2

[Django]

#29464: Move collectstatic post processing messages to verbosity 2
-+-
 Reporter:  David Szotten|Owner:  Arthur
 Type:   |  Silva
  Cleanup/optimization   |   Status:  new
Component:  contrib.staticfiles  |  Version:  2.1
 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
-+-

Comment (by Arthur Silva):

 My bad.

 Thanks for changing it to "Has patch".

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

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

Re: [Django] #29464: Move collectstatic post processing messages to verbosity 2

[Django]

#29464: Move collectstatic post processing messages to verbosity 2
-+-
 Reporter:  David Szotten|Owner:  Arthur
 Type:   |  Silva
  Cleanup/optimization   |   Status:  new
Component:  contrib.staticfiles  |  Version:  2.1
 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 Tim Graham):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  fixed =>


Comment:

 The ticket is closed when the PR is merged. You should instead check "Has
 patch" when adding a 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/070.55a39975a1b342b928467c9d4b7dd622%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29464: Move collectstatic post processing messages to verbosity 2

[Django]

#29464: Move collectstatic post processing messages to verbosity 2
-+-
 Reporter:  David Szotten|Owner:  Arthur
 Type:   |  Silva
  Cleanup/optimization   |   Status:  closed
Component:  contrib.staticfiles  |  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 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 Arthur Silva):

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


Comment:

 Thanks David.

 I've submitted a [https://github.com/django/django/pull/10042 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/070.c25b9a105037f6398a4eca7284ef7815%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22900: ugettext_lazy with arguments causes RuntimeError

[Django]

#22900: ugettext_lazy with arguments causes RuntimeError
--+
 Reporter:  Karmo Rosental|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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 Claude Paroz):

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


Comment:

 I guess that the `format_lazy` addition in docs should now be sufficient.

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

Re: [Django] #22961: StaticFilesHandler should not run middleware on 404

[Django]

#22961: StaticFilesHandler should not run middleware on 404
-+-
 Reporter:  Wil Tan  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.6
 Severity:  Normal   |   Resolution:  duplicate
 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 Claude Paroz):

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


Comment:

 I think that #29353 was a duplicate. It was recently fixed and should be
 in Django 2.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/064.bc3290814e880f70b31ea6ef5c8f0763%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29452: makemessages command doesn't set .pot file charset properly

[Django]

#29452: makemessages command doesn't set .pot file charset properly
-+-
 Reporter:  Bartosz Grabski  |Owner:  Bartosz
 |  Grabski
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.11
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Bartosz Grabski):

 Thanks Claude, that was actually my idea. Will do.
 Ramiro: thanks for the tip.

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

Re: [Django] #29433: templatefilter "make_list" should receive a optional split variable

[Django]

#29433: templatefilter "make_list" should receive a optional split variable
-+-
 Reporter:  danilovmy|Owner:  Prakash
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  templatefilter,  | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Prakash):

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


Comment:

 Assigning  to myself

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

Re: [Django] #29443: Unify registries in Django

[Django]

#29443: Unify registries in Django
-+-
 Reporter:  Johannes Hoppe   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  plugin, registry,| Triage Stage:  Accepted
  pattern, utils |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 I took a look to the Django own registry implementations, and struggled to
 find much code that could be factorized in a common class. The structure
 of the registries themselves are various: list, set, mapping, sometimes
 several of them. Then the implementations differ much depending on the
 internal registry structure.

 Johannes, could you explore that a bit and show us some example of current
 code that would benefit from a utility class?

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

Re: [Django] #29464: Move collectstatic post processing messages to verbosity 2

[Django]

#29464: Move collectstatic post processing messages to verbosity 2
-+-
 Reporter:  David Szotten|Owner:  Arthur
 Type:   |  Silva
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  2.1
 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
-+-

Comment (by David Szotten):

 you probably need to enable a storage backend that uses post processing,
 e.g. using


 {{{
 
@override_settings(STATICFILES_STORAGE='django.contrib.staticfiles.storage.CachedStaticFilesStorage')
 def test_foo(self):

 }}}

 see
 
https://github.com/django/django/blob/7a266e25be1b64ab5889f9808ff6d258d27f/django/contrib/staticfiles/management/commands/collectstatic.py#L125

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

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

Re: [Django] #29205: MultiValueField ignores a required value of a sub field

[Django]

#29205: MultiValueField ignores a required value of a sub field
+
 Reporter:  Takayuki Hirai  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.11
 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 Herbert Fortes):

 * cc: Herbert Fortes (added)


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

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

Re: [Django] #29427: RequestDataTooBig raised in request.py prevents Middleware from returning a valid response

[Django]

#29427: RequestDataTooBig raised in request.py prevents Middleware from 
returning a
valid response
---+
 Reporter:  S. Paquette|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.11
 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 Herbert Fortes):

 I liked [https://docs.djangoproject.com/en/2.0/topics/http/middleware
 /#process-exception process-exception] proposed by Josh Schneier. I did
 not test it though.

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

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

Re: [Django] #29484: Remove the need to specify SPATIALITE_LIBRARY_PATH with Spatialite 4.2+

[Django]

#29484: Remove the need to specify SPATIALITE_LIBRARY_PATH with Spatialite 4.2+
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  GIS  |  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 Claude Paroz ):

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


Comment:

 In [changeset:"f3836144db1dc05bce5a2a1cc7e46a01b0f67db6" f383614]:
 {{{
 #!CommitTicketReference repository=""
 revision="f3836144db1dc05bce5a2a1cc7e46a01b0f67db6"
 Fixed #29484 -- Removed the need to specify SPATIALITE_LIBRARY_PATH with
 Spatialite 4.2+.

 Thanks Tim Graham for the review.
 }}}

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

Re: [Django] #29483: Confirm support for GDAL 2.3

[Django]

#29483: Confirm support for GDAL 2.3
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  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
--+

Comment (by Claude Paroz ):

 In [changeset:"69e2d173e5082a8c475586cff7920b2fb962c333" 69e2d173]:
 {{{
 #!CommitTicketReference repository=""
 revision="69e2d173e5082a8c475586cff7920b2fb962c333"
 [2.1.x] Refs #29483 -- Relaxed WGS 84 check regex

 With GDAL 2.3, the exact string changed again.
 Backport of 86988dd890671aa8935f86eab2bbe22ad917db70 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/067.5ecc4e228b24e60f62c7daee39a58a4a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29483: Confirm support for GDAL 2.3

[Django]

#29483: Confirm support for GDAL 2.3
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  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
--+

Comment (by Claude Paroz ):

 In [changeset:"86988dd890671aa8935f86eab2bbe22ad917db70" 86988dd]:
 {{{
 #!CommitTicketReference repository=""
 revision="86988dd890671aa8935f86eab2bbe22ad917db70"
 Refs #29483 -- Relaxed WGS 84 check regex

 With GDAL 2.3, the exact string changed again.
 }}}

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