date:20170217

Re: [Django] #27855: Django 2.0 Python version support

2017-02-17 Thread Django

#27855: Django 2.0 Python version support
-+-
 Reporter:  Raffaele Salmaso |Owner:  Raffaele
 Type:   |  Salmaso
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  2.0  | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Raffaele Salmaso):

 Ok,
 this is because some projects (in this case django-rest-framework =>
 https://github.com/tomchristie/django-rest-
 framework/commit/7d4706fbcc28429489a4e01f3c29dd5121e35157 and
 https://groups.google.com/forum/#!topic/django-rest-framework/we77U58fcWQ
 ) see this stub and think it as a final decision.

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

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

Re: [Django] #27845: Possible Migration Optimizer Strategy Improvement

2017-02-17 Thread Django

#27845: Possible Migration Optimizer Strategy Improvement
-+-
 Reporter:  Raphael Gaschignard  |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * status:  new => assigned
 * owner:  nobody => Simon Charette
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7999 PR]

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

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

Re: [Django] #27818: Use contextlib.suppress to suppress exceptions.

2017-02-17 Thread Django

#27818: Use contextlib.suppress to suppress exceptions.
--+
 Reporter:  Mads Jensen   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 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 rtnpro):

 * owner:  rtnpro => (none)
 * status:  assigned => new


Comment:

 Sorry, I assigned it to myself, by mistake.

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

Re: [Django] #27818: Use contextlib.suppress to suppress exceptions.

2017-02-17 Thread Django

#27818: Use contextlib.suppress to suppress exceptions.
-+-
 Reporter:  Mads Jensen  |Owner:  Ratnadeep
 Type:   |  Debnath
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ratnadeep Debnath):

 * status:  new => assigned
 * owner:  Mads Jensen => Ratnadeep Debnath


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

Re: [Django] #27856: Date subtraction loses accuracy on PostgreSQL for differences larger than month

2017-02-17 Thread Django

#27856: Date subtraction loses accuracy on PostgreSQL for differences larger 
than
month
-+-
 Reporter:  Vytis Banaitis   |Owner:  Vytis
 |  Banaitis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * version:  1.10 => master
 * stage:  Unreviewed => Accepted


Comment:

 This is something I missed when implementing generalized temporal
 subtraction in #24793, thanks for the report and 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/064.0df17ee88d19abb794b6a95c0c11d497%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27857: Cleanups and features to use when dropping support for Python 3.4

2017-02-17 Thread Django

#27857: Cleanups and features to use when dropping support for Python 3.4
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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
-+-
Changes (by Tim Graham):

 * Attachment "27857.diff" added.


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

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

Re: [Django] #27857: Cleanups and features to use when dropping support for Python 3.4

2017-02-17 Thread Django

#27857: Cleanups and features to use when dropping support for Python 3.4
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Someday/Maybe


Comment:

 Initial patch of cleanups attached.

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

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

[Django] #27857: Cleanups and features to use when dropping support for Python 3.4

2017-02-17 Thread Django

#27857: Cleanups and features to use when dropping support for Python 3.4
+
   Reporter:  Tim Graham|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Django 1.11 or 2.0 is likely to be the last version of Django to support
 Python 3.4. (see [https://groups.google.com/d/topic/django-
 developers/4rbVKJYm8DI/discussion django-developers discussion])

 Meanwhile, let's track cleanups and improvements we can make after that.

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

Re: [Django] #27856: Date subtraction loses accuracy on PostgreSQL for differences larger than month

2017-02-17 Thread Django

#27856: Date subtraction loses accuracy on PostgreSQL for differences larger 
than
month
-+-
 Reporter:  Vytis Banaitis   |Owner:  Vytis
 |  Banaitis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (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 Vytis Banaitis):

 * status:  new => assigned
 * owner:  nobody => Vytis Banaitis
 * has_patch:  0 => 1


Comment:

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

[Django] #27856: Date subtraction loses accuracy on PostgreSQL for differences larger than month

2017-02-17 Thread Django

#27856: Date subtraction loses accuracy on PostgreSQL for differences larger 
than
month
-+-
   Reporter:  Vytis  |  Owner:  nobody
  Banaitis   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.10
  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  |
-+-
 On PostgreSQL backend date subtraction is implemented via `age` function.

 From [https://www.postgresql.org/docs/current/static/functions-
 datetime.html#FUNCTIONS-DATETIME-TABLE PostgreSQL docs]:

  Subtract arguments, producing a "symbolic" result that uses years and
 months, rather than just days

 When converting this year-month-day interval to a python `timedelta`, year
 equals 365 days and month equals 30 days. This can (and in the case of
 longer intervals, most likely will) differ from the result of the same
 subtraction done in python.

 Example:
 {{{#!python
 class DateModel(models.Model):
 d1 = models.DateField()
 d2 = models.DateField()
 }}}
 {{{#!python
 In [2]: DateModel.objects.create(d1=datetime.date(2017, 2, 5),
 d2=datetime.date(2016, 3, 1))

 In [3]: dm = DateModel.objects.annotate(diff=F('d1') - F('d2')).get()

 In [4]: dm.diff
 Out[4]: datetime.timedelta(334)

 In [5]: dm.d1 - dm.d2
 Out[5]: datetime.timedelta(341)
 }}}

 Solution:

 Use date subtraction which returns an integer, the difference in days, and
 convert it to an interval in days only:
 {{{
 (interval '1 day' * (lhs - rhs))
 }}}

 Or on PostgreSQL 9.4 or later:
 {{{
 make_interval(days := lhs - rhs)
 }}}

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

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

Re: [Django] #27855: Django 2.0 Python version support

2017-02-17 Thread Django

#27855: Django 2.0 Python version support
-+-
 Reporter:  Raffaele Salmaso |Owner:  Raffaele
 Type:   |  Salmaso
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  2.0  | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * keywords:   => 2.0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Someday/Maybe


Comment:

 This is yet to be decided, see [https://groups.google.com/d/topic/django-
 developers/4rbVKJYm8DI/discussion django-developers thread]. There are
 more places to update than what you've done so far, I'll do it later if
 needed.

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

Re: [Django] #24977: Template variables with a value of None are considered to be == to non-existent properties

2017-02-17 Thread Django

#24977: Template variables with a value of None are considered to be == to non-
existent properties
-+-
 Reporter:  Daniel Quinn |Owner:  Tim
 Type:   |  Martin
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  string, if,  | Triage Stage:  Accepted
  equivalence|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #27855: Django 2.0 Python version support

2017-02-17 Thread Django

#27855: Django 2.0 Python version support
-+-
 Reporter:  Raffaele Salmaso |Owner:  Raffaele
 |  Salmaso
 Type:  Uncategorized|   Status:  assigned
Component:  Documentation|  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 Raffaele Salmaso):

 * owner:  nobody => Raffaele Salmaso
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 PR => https://github.com/django/django/pull/8078

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

[Django] #27855: Django 2.0 Python version support

2017-02-17 Thread Django

#27855: Django 2.0 Python version support
+
   Reporter:  Raffaele Salmaso  |  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  Documentation |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 |
+
 The current django 2.0 release notes say that django 2.0 supports python
 3.5+, not 3.4.
 But in https://groups.google.com/forum/#!msg/django-
 developers/4rbVKJYm8DI/tVciTPHOEQAJ there is consensus not to drop 3.4 for
 now, at least for 2.0.
 And django master is currently tested against python 3.4 3.5 and 3.6
 
https://github.com/django/django/blob/1c466994d9729a8902d34e277a3a685bef2a08e1/tox.ini#L24

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

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

Re: [Django] #27308: BytesWarning exception raised when running with python 3 -bb option

2017-02-17 Thread Django

#27308: BytesWarning exception raised when running with python 3 -bb option
-+-
 Reporter:  Gustavo J. A. M. |Owner:  nobody
  Carneiro   |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8077 PR] to fix `BytesWarnings`
 identified by Django's test suite.

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

Re: [Django] #27176: django.setup() should raise an exception instead of hanging on re-entrant calls

2017-02-17 Thread Django

#27176: django.setup() should raise an exception instead of hanging on 
re-entrant
calls
--+
 Reporter:  Aymeric Augustin  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

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

Re: [Django] #20296: django.utils.safestring.mark_safe forces evaluation of lazy objects

2017-02-17 Thread Django

#20296: django.utils.safestring.mark_safe forces evaluation of lazy objects
---+
 Reporter:  Baptiste Mispelon  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham):

 In the steps to reproduce, should `mark_safe()` be inside
 `ugettext_lazy()` as in #27803 instead of the other way around? If so,
 maybe this is a wontfix, assuming the documentation is clear about proper
 usage.

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

Re: [Django] #27639: Add a chunk size argument to QuerySet.iterator()

2017-02-17 Thread Django

#27639: Add a chunk size argument to QuerySet.iterator()
-+-
 Reporter:  François Freitag |Owner:  François
 |  Freitag
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  cursors database | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #27486: intword and filesizeformat filters shouldn't pass non-integers to gettext

2017-02-17 Thread Django

#27486: intword and filesizeformat filters shouldn't pass non-integers to 
gettext
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  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 Tim Graham):

 * status:  assigned => new
 * owner:  Tim Graham => (none)


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

Re: [Django] #6989: Inability to define DNS_NAME in django.core.mail results in e-mail messages being rejected or marked as spam

2017-02-17 Thread Django

#6989: Inability to define DNS_NAME in django.core.mail results in e-mail 
messages
being rejected or marked as spam
-+-
 Reporter:  Franklin |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  local_hostname,  | Triage Stage:  Accepted
  DNS_NAME, CachedDnsName, smtplib,  |
  SMTPConnection |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I think a setting is fine considering we added other mail settings
 recently. The patch needs to be updated, checked against the
 PatchReviewChecklist, and turned into 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/066.18fc891643f334e64bc5c2c31f3da8c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27818: Use contextlib.suppress to suppress exceptions.

2017-02-17 Thread Django

#27818: Use contextlib.suppress to suppress exceptions.
--+
 Reporter:  Mads Jensen   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 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 Nithun Harikrishnan):

 * owner:  Nithun Harikrishnan => (none)
 * 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/068.ada3efb69eca96b4c806107dc8b490e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
-+-
 Reporter:  David Evans  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 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 David Evans):

 That's an interesting idea. So referencing a non-existent directory in
 `STATICFILES_DIRS` would trigger a warning in the system check framework,
 but wouldn't prevent `collectstatic` from running. Aymeric, would that
 address your concerns?

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

Re: [Django] #27818: Use contextlib.suppress to suppress exceptions.

2017-02-17 Thread Django

#27818: Use contextlib.suppress to suppress exceptions.
-+-
 Reporter:  Mads Jensen  |Owner:  Nithun
 Type:   |  Harikrishnan
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Nithun Harikrishnan):

 * owner:  Mads Jensen => Nithun Harikrishnan
 * 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/068.d3ed58dc5279bc3befda4fa72b5a3054%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
-+-
 Reporter:  David Evans  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 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 Tim Graham):

 Another trend is moving runtime warnings to the system check framework,
 e.g. 0ec4dc91e0e7befdd06aa0613b5d0fbe3c785ee7. Could that be appropriate
 here?

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

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

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
-+-
 Reporter:  David Evans  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 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 Aymeric Augustin):

 As long as that doesn't obscure errors, yes, it should be an improvement.

 Historically we've removed lots of "helpful" error handling which made
 other errors harder to diagnose. Often the raw stack trace is the best way
 to see what went wrong. I wanted to share that experience with the first
 case that came to my mind.

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

Re: [Django] #27656: Fix comment verb style according to PEP 257

2017-02-17 Thread Django

#27656: Fix comment verb style according to PEP 257
-+-
 Reporter:  Anton Samarchyan |Owner:  Anton
 Type:   |  Samarchyan
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"4696078832f486ba63f0783a0795294b3d80d862" 46960788]:
 {{{
 #!CommitTicketReference repository=""
 revision="4696078832f486ba63f0783a0795294b3d80d862"
 Refs #27656 -- Updated django.template/tag docstring verbs according to
 PEP 257.
 }}}

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

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
-+-
 Reporter:  David Evans  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 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 David Evans):

 Replying to [comment:3 Aymeric Augustin]:
 > In the case of Heroku which swallows the output of collectstatic, if
 `STATICFILES_DIRS` doesn't have a correct value, the change suggested here
 will make it pretend that it succeeded, even though it didn't collect
 files, while it currently says it's failing. I think that's a problem:
 "errors shouldn't pass silently" :-)

 Yes, absolutely agree that errors shouldn't pass silently. In the case of
 the Heroku buildpack, it does suppress some of the output but any warning
 messages will get displayed:
 https://github.com/heroku/heroku-buildpack-
 
python/blob/677dfeec119f28b4d1a8f679b38b2d4e407f4533/bin/steps/collectstatic#L33

 Would another option be for `collectstatic` to note that a directory was
 missing, issue a warning, ''proceed with collecting the rest of the static
 files'', and then exit with status > 0 at the end? That way, the user
 would still have a working set of static files.

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

Re: [Django] #27843: M2M db table names with explicit `username`

2017-02-17 Thread Django

#27843: M2M db table names with explicit `username`
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"87775b64cdda97567a33c7bad65ad42853048525" 87775b64]:
 {{{
 #!CommitTicketReference repository=""
 revision="87775b64cdda97567a33c7bad65ad42853048525"
 [1.11.x] Fixed #27843 -- Fixed truncate_name() when the name contains a
 username.

 Backport of b9351905721771fb49ea0020c751ae4280754c43 from master
 }}}

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

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

Re: [Django] #27843: M2M db table names with explicit `username`

2017-02-17 Thread Django

#27843: M2M db table names with explicit `username`
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 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:"b9351905721771fb49ea0020c751ae4280754c43" b9351905]:
 {{{
 #!CommitTicketReference repository=""
 revision="b9351905721771fb49ea0020c751ae4280754c43"
 Fixed #27843 -- Fixed truncate_name() when the name contains a username.
 }}}

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

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
-+-
 Reporter:  David Evans  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 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 Aymeric Augustin):

 In the case of Heroku which swallows the output of collectstatic, if
 `STATICFILES_DIRS` doesn't have a correct value, the change suggested here
 will make it pretend that it succeeded, even though it didn't collect
 files, while it currently says it's failing. I think that's a problem:
 "errors shouldn't pass silently" :-)

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

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

Comment (by David Evans):

Replying to [comment:1 Tim Graham]:
> Maybe the current error message could be improved. What does it say?
>
> Did you research the origin of the current exception to see if you can
find any design decisions there?

The exception is just `OSError: [Errno 2] No such file or directory`

This bubbles up from directly from the call to `os.listdir` here:

https://github.com/django/django/blob/1f7ca858664491589ba400419a491dd0a9af5dff/django/core/files/storage.py#L312

So I don't think there was any deliberate design decision here.

Also, I don't think improving the error message will solve this specific
problem because:
a. If the user is deploying to Heroku then they are just told that the
collectstatic step was skipped due to errors, but they have to run the
command themselves to see what those errors were.
b. An error message about missing directories is confusing to them because
they can see the directory right there on their filesystem. The fact that
git doesn't track empty directories is then yet another bit of weird
computer arcanery that we need to expose them to when they are just trying
to deploy "My First Website".

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

Re: [Django] #27852: Admin Delete Object Block Page Doesn't Show All Related Objects Blocking Deletion

2017-02-17 Thread Django

#27852: Admin Delete Object Block Page Doesn't Show All Related Objects Blocking
Deletion
--+
 Reporter:  Kenny Loveall |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

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


Comment:

 I haven't confirmed the issue or looked into if it's feasible to fix, but
 if you provide a patch, it seems okay to change.

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

Re: [Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
-+-
 Reporter:  David Evans  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.10
 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 Tim Graham):

 Maybe the current error message could be improved. What does it say?

 Did you research the origin of the current exception to see if you can
 find any design decisions there?

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

Re: [Django] #27849: Support Postgres FILTER WHERE conditions in ArrayAgg

2017-02-17 Thread Django

#27849: Support Postgres FILTER WHERE conditions in ArrayAgg
--+
 Reporter:  Tom   |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 You can ask on the DevelopersMailingList to get feedback about the design
 decisions such as the syntax.

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

[Django] #27854: Make `collectstatic` warn (rather than blow up) on missing directories

2017-02-17 Thread Django

#27854: Make `collectstatic` warn (rather than blow up) on missing directories
---+
Reporter: David Evans | Owner: nobody
Type: Uncategorized| Status: new
Component: contrib.staticfiles |Version: 1.10
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|
---+
At present if the `STATICFILES_DIRS` setting contains references to
directories which do not exist then the whole command will die with an
`OSError`.

A situation I've seen bite a few newcomers to Django is that they will
have an empty static directory which (being empty) won't get tracked by
git. This means that `collectstatic` works when they run it locally, but
blows up with a (to them) cryptic error when they try to deploy.

If we made `collectstatic` simply log a warning in the case of non-
existent directories and continue processing then we could avoid this
problem and remove one possible source of frustration for newcomers.

If this approach seems acceptable to others I am happy to submit an
appropriate 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/049.a073579d693a0f9435ac0981bca4bfec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27853: When AdminEmailHandler is configured with include_html, DisallowedHost causes a 500 instead of a 400

2017-02-17 Thread Django

#27853: When AdminEmailHandler is configured with include_html, DisallowedHost
causes a 500 instead of a 400
-+--
 Reporter:  Douglas Thrift   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  1.8
 Severity:  Normal   |   Resolution:  duplicate
 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 Tim Graham):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  Core (Mail) => Error reporting


Comment:

 Duplicate of #25099 (see ticket:25099#comment:9). It's fixed in Django
 1.9.

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

Re: [Django] #27842: class GenericSitemap doesn't handle "protocol" in init

2017-02-17 Thread Django

#27842: class GenericSitemap doesn't handle "protocol" in __init__
-+-
 Reporter:  chex |Owner:  chex
 Type:  New feature  |   Status:  assigned
Component:  contrib.sitemaps |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  sitemaps | Triage Stage:  Accepted
  genericsitemap |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by chex):

 * needs_docs:  1 => 0


Comment:

 Update [https://github.com/django/django/pull/8065 pr] with documentation.
 Non specific to the ticket tests are moved to another
 [https://github.com/django/django/pull/8075 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.a01c027c63d019a1c15e8c1e07b43674%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

37 matches

Mail list logo