date:20190211

Re: [Django] #30128: Using database functions with tzinfo=datetime.timezone(datetime.timedelta(...)) results in an incorrect query

2019-02-11 Thread Django

#30128: Using database functions with
tzinfo=datetime.timezone(datetime.timedelta(...)) results in an incorrect
query
-+-
 Reporter:  mvarnar  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  orm, postgresql, | Triage Stage:  Accepted
  timezone, datetime |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

Comment (by Matthias Kestenholz):

I don't think sorting by length is the way to go - it would be trivial to
make the test fail again by extending the first list with unrelated items.
It might be a good real-world heuristic for finding a solution more often,
but that's just trading a reproducible bug for an unpredictable one.

Well yes, if the `ColorPicker` itself would have a longer list of JS files
it depends on then it would fail too. If, on the other hand, it wasn't a
`ColorPicker` widget but a `ColorPicker` formset or form the initially
declared lists would still be preserved and sorting the lists by length
would give the correct result.

Since #30153 the initially declared lists (or tuples) are preserved so
maybe you have many JS and CSS declarations but as long as they are
unrelated there will not be many long sublists.

I'm obviously happy though if you're willing to spend the time finding a
robust solution to this problem.

(For the record: Personally I was happy with the state of things pre-2.0
too... and For the record 2: I'm also using custom widgets and inlines in
feincms3/django-content-editor. It's really surprising to me that we
didn't stumble on this earlier since we're always working on the latest
Django version or even on pre-release versions if at all possible)

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

Re: [Django] #30178: Support duck-typing for database passwords in settings

2019-02-11 Thread Django

#30178: Support duck-typing for database passwords in settings
-+-
 Reporter:  Dan Davis|Owner:  Dan Davis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Dan Davis):

 Updated pull request to be against master, re-built branch on master and
 force pushed branch to github to preserve branch.

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

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

Comment (by Matt Westcott):

I don't think sorting by length is the way to go - it would be trivial to
make the test fail again by extending the first list with unrelated items.
It //might// be a good real-world heuristic for finding a solution more
often, but that's just trading a reproducible bug for an unpredictable
one.

(I'm not sure I'd trust it as a heuristic either: we've encountered this
issue on Wagtail CMS, where we're making extensive use of form media on
hierarchical form structures, and so those media definitions will tend to
bubble up several layers to reach the top level. At that point, there's no
way of knowing whether the longer list is the one with more complex
dependencies, or just one that collected more unrelated files on the way
up the tree...)

I'll do some more thinking on this. My hunch is that even if it does end
up being a travelling-salesman-type problem, it's unlikely to be run on a
large enough data set for performance to 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/064.396382e3d9a36fe1a87720a4cf421146%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30178: Support duck-typing for database passwords in settings

2019-02-11 Thread Django

#30178: Support duck-typing for database passwords in settings
-+-
 Reporter:  Dan Davis|Owner:  Dan Davis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dan Davis):

 * has_patch:  0 => 1


Comment:

 There is  now a pull request -
 https://github.com/django/django/pull/10983, but it may need documentation
 and is directly to `stable/2.2.x` rather than `master`.  Not sure how that
 is usually done.

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

Re: [Django] #30178: Support duck-typing for database passwords in settings

2019-02-11 Thread Django

Comment (by Dan Davis):

Replying to [comment:3 Tim Graham]:
> `str(get_a_password)` in your settings file is not sufficient?

Owing to a mandated separation of duties, we developers don’t have the
ability to restart our applications at will. But we are also mandated to
change passwords regularly. We have handled this up to now with lazy
evaluation of the password at the time the connection is created. Your
suggested alternative would freeze the current password in place, and
require a restart whenever the password changes, which is the behavior we
are trying to avoid.

Our DevOps has an application that will whine at us to change our
passwords, and will generate a random good password. However, it can't
restart the application when the password is changed; it simply
consistently changes the password across MySQL/Oracle/PostgreSQL etc. and
stores the password in a symmetrically encrypted form.

Currently, my internal module will cache the password for 5 minutes, but
typically CONN_MAX_AGE is much larger than this in production, and no race
condition is possible there. We also have a failover mechanism in place,
TCP/IP asynchronous connects, etc. underlying the simple call to
`str(get_a_password)`.

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
---+
 Reporter:  Matt Westcott  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  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 Matthias Kestenholz):

 Thinking some more:

 - `sorted()` is more likely to break existing code because people probably
 haven't listed all dependencies in their `js` attributes now. Yes, that's
 not what they should have done, but breaking peoples' projects sucks and I
 don't really want to do that (even if introducing `sorted()` might be the
 least disruptive and at the same time most correct change)
 - wanting to handle the `jquery`, `widget1`, `noConflict` and `jquery`,
 `widget2`, `noConflict` case has introduced an unexpected amount of
 complexity
 - introducing a complex solving framework will have a really bad impact on
 runtime and will introduce even more complexity and is out of the question
 to me

 I'm happy to help fixing this but right now I only see bad and worse
 choices.

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
---+
 Reporter:  Matt Westcott  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  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 Matthias Kestenholz):

 So
 
https://github.com/django/django/commit/959d0c078a1c903cd1e4850932be77c4f0d2294d
 (the fix for #30153) didn't make this case worse, it just didn't improve
 on it. The problem is actually the same I encountered, with the same
 unintuitive error message too. There is still a way to produce a
 conflicting order but it's harder to trigger in the administration
 interface now but unfortunately still easy. Also, going back to the state
 of things pre 2.0 was already discussed previously and rejected.

 Here's a failing test and and an idea to make this particular test pass:
 Merge the JS sublists starting from the longest list and continuing with
 shorter lists. The CSS case is missing yet. The right thing to do would be
 (against [http://wiki.c2.com/?WorseIsBetter worse is better]) to add some
 sort of dependency resolution solver with backtracking but that's surely a
 bad idea for many other reasons.

 The change makes some old tests fail (I only took a closer look at
 `test_merge_js_three_way` and in this case the failure is fine --
 `custom_widget.js` is allowed to appear before `jquery.js`.)

 {{{
 diff --git a/django/forms/widgets.py b/django/forms/widgets.py
 index 02aa32b207..d85c409152 100644
 --- a/django/forms/widgets.py
 +++ b/django/forms/widgets.py
 @@ -70,9 +70,15 @@ class Media:

  @property
  def _js(self):
 -js = self._js_lists[0]
 +sorted_by_length = list(sorted(
 +filter(None, self._js_lists),
 +key=lambda lst: -len(lst),
 +))
 +if not sorted_by_length:
 +return []
 +js = sorted_by_length[0]
  # filter(None, ...) avoids calling merge() with empty lists.
 -for obj in filter(None, self._js_lists[1:]):
 +for obj in filter(None, sorted_by_length[1:]):
  js = self.merge(js, obj)
  return js

 diff --git a/tests/forms_tests/tests/test_media.py
 b/tests/forms_tests/tests/test_media.py
 index 8cb484a15e..9d17ad403b 100644
 --- a/tests/forms_tests/tests/test_media.py
 +++ b/tests/forms_tests/tests/test_media.py
 @@ -571,3 +571,12 @@ class FormsMediaTestCase(SimpleTestCase):
  # was never specified.
  merged = widget3 + form1 + form2
  self.assertEqual(merged._css, {'screen': ['a.css', 'b.css'],
 'all': ['c.css']})
 +
 +def test_merge_js_some_more(self):
 +widget1 = Media(js=['color-picker.js'])
 +widget2 = Media(js=['text-editor.js'])
 +widget3 = Media(js=['text-editor.js', 'text-editor-extras.js',
 'color-picker.js'])
 +
 +merged = widget1 + widget2 + widget3
 +
 +self.assertEqual(merged._js, ['text-editor.js', 'text-editor-
 extras.js', 'color-picker.js'])
 }}}

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

Re: [Django] #30177: format_number() crashes when the number has over 200 digits

2019-02-11 Thread Django

#30177: format_number() crashes when the number has over 200 digits
+
 Reporter:  Tim Graham  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 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:"5c2b94af2a5dcbce5a88c47b808f5f58bfb7b160" 5c2b94a]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c2b94af2a5dcbce5a88c47b808f5f58bfb7b160"
 [2.1.x] Refs #30177 -- Forwardported 2.0.13 release notes.

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

Re: [Django] #30177: format_number() crashes when the number has over 200 digits

2019-02-11 Thread Django

#30177: format_number() crashes when the number has over 200 digits
+
 Reporter:  Tim Graham  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 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:"f548ac7fa546557f558a445e7823adf01b649395" f548ac7]:
 {{{
 #!CommitTicketReference repository=""
 revision="f548ac7fa546557f558a445e7823adf01b649395"
 [2.2.x] Refs #30177 -- Forwardported 2.0.13 release notes.

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

Re: [Django] #30177: format_number() crashes when the number has over 200 digits

2019-02-11 Thread Django

#30177: format_number() crashes when the number has over 200 digits
+
 Reporter:  Tim Graham  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 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:"1b8f552b08eb7642be598ba7512e7eaecefbdc6d" 1b8f552]:
 {{{
 #!CommitTicketReference repository=""
 revision="1b8f552b08eb7642be598ba7512e7eaecefbdc6d"
 Refs #30177 -- Forwardported 2.0.13 release notes.
 }}}

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
---+
 Reporter:  Matt Westcott  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  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):

 * cc: Johannes Hoppe, Matthias Kestenholz (added)
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #30177: format_number() crashes when the number has over 200 digits

2019-02-11 Thread Django

#30177: format_number() crashes when the number has over 200 digits
+
 Reporter:  Tim Graham  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 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:"392e040647403fc8007708d52ce01d915b014849" 392e0406]:
 {{{
 #!CommitTicketReference repository=""
 revision="392e040647403fc8007708d52ce01d915b014849"
 [2.0.x] Fixed #30177 -- Fixed format_number() crash with over 200 digits.

 There are existing test failures. The incorrect patch was applied
 in 1f42f82566c9d2d73aff1c42790d6b1b243f7676.
 }}}

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
---+--
 Reporter:  Matt Westcott  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  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 Matt Westcott):

 Yes, testing against current master
 (b39bd0aa6d5667d6bbcf7d349a1035c676e3f972).

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
---+--
 Reporter:  Matt Westcott  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  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 Tim Graham):

 Are you testing with the fix from #30153?

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

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
---+--
 Reporter:  Matt Westcott  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  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 Matt Westcott):

 As a tentative fix, I propose that media objects should explicitly
 distinguish between cases where we do / don't care about ordering,
 notionally something like:

 {{{
 class FancyTextWidget(forms.Widget):
 class Media:
 js = {
 ('text-editor.js', 'text-editor-extras.js'),  # tuple = order
 is important
 'color-picker.js'  # set = order is unimportant
 }
 }}}

 (although using a set for this is problematic due to the need for contents
 to be hashable), and the result of adding two media objects should be a
 "don't care" so that we aren't introducing dependencies where the original
 objects didn't have them. We would then defer assembling them into a flat
 list until the final render call. I haven't worked out the rest of the
 algorithm yet, but I'm willing to dig further if this sounds like a
 sensible plan of attack...

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

[Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

2019-02-11 Thread Django

#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
-+
   Reporter:  Matt Westcott  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Forms  |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  |
-+
 Consider the following form definition, where `text-editor-extras.js`
 depends on `text-editor.js` but all other JS files are independent:

 {{{
 from django import forms


 class ColorPicker(forms.Widget):
 class Media:
 js = ['color-picker.js']


 class SimpleTextWidget(forms.Widget):
 class Media:
 js = ['text-editor.js']


 class FancyTextWidget(forms.Widget):
 class Media:
 js = ['text-editor.js', 'text-editor-extras.js', 'color-
 picker.js']


 class MyForm(forms.Form):
 background_color = forms.CharField(widget=ColorPicker())
 intro = forms.CharField(widget=SimpleTextWidget())
 body = forms.CharField(widget=FancyTextWidget())
 }}}

 Django should be able to resolve the JS files for the final form into the
 order text-editor.js, text-editor-extras.js, color-picker.js. However,
 accessing `MyForm().media` results in:

 {{{
 /projects/django/django/forms/widgets.py:145: MediaOrderConflictWarning:
 Detected duplicate Media files in an opposite order:
 text-editor-extras.js
 text-editor.js
   MediaOrderConflictWarning,
 Media(css={}, js=['text-editor-extras.js', 'color-picker.js', 'text-
 editor.js'])
 }}}

 The `MediaOrderConflictWarning` is a result of the order that the
 additions happen in: `ColorPicker().media + SimpleTextWidget().media`
 produces `Media(css={}, js=['color-picker.js', 'text-editor.js'])`, which
 (wrongly) imposes the constraint that color-picker.js must appear before
 text-editor.js.

 The final result is particularly unintuitive here, as it's worse than the
 "naïve" result produced by Django 1.11 before order-checking was added
 (color-picker.js, text-editor.js, text-editor-extras.js), and the pair of
 files reported in the warning message seems wrong too (aren't color-
 picker.js and text-editor.js the wrong-ordered ones?)

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

Re: [Django] #30178: Support duck-typing for database passwords in settings

2019-02-11 Thread Django

#30178: Support duck-typing for database passwords in settings
-+-
 Reporter:  Dan Davis|Owner:  Dan Davis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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):

 `str(get_a_password)` in your settings file is not 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/065.a1c385c91378e129af685831c5f32fb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30178: Support duck-typing for database passwords in settings

2019-02-11 Thread Django

#30178: Support duck-typing for database passwords in settings
-+-
 Reporter:  Dan Davis|Owner:  Dan Davis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dan Davis):

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

Re: [Django] #30177: format_number() crashes when the number has over 200 digits

2019-02-11 Thread Django

#30177: format_number() crashes when the number has over 200 digits
+
 Reporter:  Tim Graham  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  2.0
 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/10979 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/067.14cc9b091bf72a5697d57868d56ae2dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30178: Support duck-typing for database passwords in settings (was: Support duct-typed database passwords in settings)

2019-02-11 Thread Django

#30178: Support duck-typing for database passwords in settings
-+-
 Reporter:  Dan Davis|Owner:  Dan Davis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Dan Davis:

Old description:

> I have a curious use-case where, as a U.S. Federal Agency, we've built a
> rather complete mechanism to avoid having database passwords in our
> settings files.   We have a common library that allows us to "get a
> password", which returns an object which is duck-typed to a string.
> When __str__ is called, it obtains the password (or uses a cached copy of
> the password) using a network protocol, and that returns that.
>
> We are mostly an Oracle shop.   We are now looking at upgrading to Django
> 2.2 which will be LTS, and have formerly been on Django 1.11 which has
> been LTS.
>
> It appears that ticket #29199, aka
> https://github.com/django/django/commit/acfc650f2a6e4a79e80237eabfa923ea3a05d709,
> broke that for us.
>
> My organization would love to see this lack of duck-typing as a bug;
> rather than treating this as a request for all passwords to be pluggable
> (e.g. a Callable).   Supporting duck-typing is consistent with backwards
> compatibility and also with Python philosophy.
>
> I will attempt to provide a test case and a fix.   I will also evaluate
> this on other backends, because #29199 was quite legitimate.

New description:

 I have a curious use-case where, as a U.S. Federal Agency, we've built a
 rather complete mechanism to avoid having database passwords in our
 settings files.   We have a common library that allows us to "get a
 password", which returns an object which is duck-typed to a string.   When
 __str__ is called, it obtains the password (or uses a cached copy of the
 password) using a network protocol, and that returns that.

 We are mostly an Oracle shop.   We are now looking at upgrading to Django
 2.2 which will be LTS, and have formerly been on Django 1.11 which has
 been LTS.

 It appears that ticket #29199, aka
 
https://github.com/django/django/commit/acfc650f2a6e4a79e80237eabfa923ea3a05d709,
 broke that for us.

 My organization would love to see this lack of duck-typing as a bug;
 rather than treating this as a request for all passwords to be pluggable
 (e.g. a Callable).   Supporting duck-typing is consistent with backwards
 compatibility and also with Python philosophy.

 I will attempt to provide a test case and a fix.   Separately from this
 ticket, I'll check the other backends, as some users do use postgresql,
 MySQL, etc. even if it is not the norm.

--

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

Re: [Django] #30172: Incorrect migration applying for new Meta.constraints/indexes and field check/unique or unique/index_together constraints with same fields for postgres

2019-02-11 Thread Django

#30172: Incorrect migration applying for new Meta.constraints/indexes and field
check/unique or unique/index_together constraints with same fields for
postgres
+--
 Reporter:  Pavel Tyslacki  |Owner:  Pavel Tyslacki
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  2.2
 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 Pavel Tyslacki):

 Replying to [comment:3 Tim Graham]:
 > Can you look into the SQLite failures?
 Yep. Hope will fix soon.

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

[Django] #30178: Support duct-typed database passwords in settings

2019-02-11 Thread Django

#30178: Support duct-typed database passwords in settings
-+-
Reporter: Dan Davis | Owner: Dan Davis
Type: Bug| Status: assigned
Component: Database |Version: 2.1
layer (models, ORM)|
Severity: Normal | Keywords: oracle
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-+-
I have a curious use-case where, as a U.S. Federal Agency, we've built a
rather complete mechanism to avoid having database passwords in our
settings files. We have a common library that allows us to "get a
password", which returns an object which is duck-typed to a string. When
__str__ is called, it obtains the password (or uses a cached copy of the
password) using a network protocol, and that returns that.

We are mostly an Oracle shop. We are now looking at upgrading to Django
2.2 which will be LTS, and have formerly been on Django 1.11 which has
been LTS.

It appears that ticket #29199, aka

https://github.com/django/django/commit/acfc650f2a6e4a79e80237eabfa923ea3a05d709,
broke that for us.

My organization would love to see this lack of duck-typing as a bug;
rather than treating this as a request for all passwords to be pluggable
(e.g. a Callable). Supporting duck-typing is consistent with backwards
compatibility and also with Python philosophy.

I will attempt to provide a test case and a fix. I will also evaluate
this on other backends, because #29199 was quite legitimate.

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

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

[Django] #30177: format_number() crashes when the number has over 200 digits

2019-02-11 Thread Django

#30177: format_number() crashes when the number has over 200 digits
--+
   Reporter:  Tim Graham  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Utilities   |Version:  2.0
   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   |
--+
 Only Django 2.0.x is affected. The incorrect patch was applied in
 1f42f82566c9d2d73aff1c42790d6b1b243f7676. `use_l10n` is undefined.

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

Re: [Django] #30172: Incorrect migration applying for new Meta.constraints/indexes and field check/unique or unique/index_together constraints with same fields for postgres

2019-02-11 Thread Django

#30172: Incorrect migration applying for new Meta.constraints/indexes and field
check/unique or unique/index_together constraints with same fields for
postgres
+--
 Reporter:  Pavel Tyslacki  |Owner:  Pavel Tyslacki
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  2.2
 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 Tim Graham):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Can you look into the SQLite failures?

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

Re: [Django] #30173: Use subprocess.run and PGPASSWORD for client in postgres backend

2019-02-11 Thread Django

#30173: Use subprocess.run and PGPASSWORD for client in postgres backend
-+-
 Reporter:  Daniel Bowring   |Owner:  nobody
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 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 Tim Graham):

 * component:  Uncategorized => Database layer (models, ORM)
 * needs_better_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Some test failures need to be addressed.

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

Re: [Django] #30171: Fix Python warning during LiveServerPort

2019-02-11 Thread Django

#30171: Fix Python warning during LiveServerPort
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Tests aren't passing.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson):

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


Comment:

 OK, so this should be fixed. New releases are up. Packages look correct.
 Running the test suite against the src-dist release reveals no issues.

 Sorry for the inconvenience.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson ):

 In [changeset:"f2c5f66c7c7212721ce2de6a44dfd828c7268c16" f2c5f66c]:
 {{{
 #!CommitTicketReference repository=""
 revision="f2c5f66c7c7212721ce2de6a44dfd828c7268c16"
 [1.11.x] Refs #30175 -- Added release notes for 1.11.20 release.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson ):

 In [changeset:"11485a349b20cc8775cc17c51f3b1a05c5fc5c3d" 11485a3]:
 {{{
 #!CommitTicketReference repository=""
 revision="11485a349b20cc8775cc17c51f3b1a05c5fc5c3d"
 [2.0.x] Refs #30175 -- Added release notes for 2.0.12, and 1.11.20
 releases.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson ):

 In [changeset:"168bfdd92b8bf74313fb80ca4ac707d42a1ecc5c" 168bfdd]:
 {{{
 #!CommitTicketReference repository=""
 revision="168bfdd92b8bf74313fb80ca4ac707d42a1ecc5c"
 [2.1.x] Refs #30175 -- Added release notes for 2.1.7, 2.0.12, and 1.11.20
 releases.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson ):

 In [changeset:"1672ed5ccf1215999ec478383a59527335170895" 1672ed5c]:
 {{{
 #!CommitTicketReference repository=""
 revision="1672ed5ccf1215999ec478383a59527335170895"
 [2.2.x] Refs #30175 -- Added release notes for 2.1.7, 2.0.12, and 1.11.20
 releases.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 GitHub ):

 In [changeset:"b39bd0aa6d5667d6bbcf7d349a1035c676e3f972" b39bd0aa]:
 {{{
 #!CommitTicketReference repository=""
 revision="b39bd0aa6d5667d6bbcf7d349a1035c676e3f972"
 Refs #30175 -- Added release notes for 2.1.7, 2.0.12, and 1.11.20
 releases.
 }}}

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+-
 Reporter:  rm_  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson):

 * status:  new => assigned
 * owner:  nobody => Carlton Gibson


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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+
 Reporter:  rm_  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson):

 Hi Giovanni. Yes. Hold off for now. New releases coming.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+
 Reporter:  rm_  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Giovanni Totaro - aka Vanni):

 Probably related anomaly --> After updating Django from 2.1.5 to 2.1.6 via
 pip3 I get:

 {{{
 ./manage.py makemigrations
 Migrations for 'auth':
   /home/---/venvs/---/lib/python3.5/site-
 packages/django/contrib/auth/migrations/0012_auto_20190211_1508.py
 - Alter field name on group
 }}}

 {{{
 cat /home/---/venvs/---/lib/python3.5/site-
 packages/django/contrib/auth/migrations/0012_auto_20190211_1520.py
 }}}

 {{{
 # Generated by Django 2.1.6 on 2019-02-11 14:20

 from django.db import migrations, models


 class Migration(migrations.Migration):

 dependencies = [
 ('auth', '0011_update_proxy_permissions'),
 ]

 operations = [
 migrations.AlterField(
 model_name='group',
 name='name',
 field=models.CharField(max_length=80, unique=True,
 verbose_name='name'),
 ),
 ]
 }}}

 but
 
[https://github.com/django/django/commit/e81955401885a93a459bcc130642b6ea5bf4ba4d
 #diff-49fc6cea24d46bdb27339c1aab392e32L111 commit Fixed #29939 --
 Increased Group.name max_length to 150 characters] has 2.2.x tags, and pip
 version has max_length=80 in django/contrib/auth/models.py:111

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

Re: [Django] #30172: Incorrect migration applying for new Meta.constraints/indexes and field check/unique or unique/index_together constraints with same fields for postgres

2019-02-11 Thread Django

#30172: Incorrect migration applying for new Meta.constraints/indexes and field
check/unique or unique/index_together constraints with same fields for
postgres
+--
 Reporter:  Pavel Tyslacki  |Owner:  Pavel Tyslacki
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  2.2
 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 Pavel Tyslacki):

 * owner:  nobody => Pavel Tyslacki
 * status:  new => assigned
 * has_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/063.106891aaf19e781cb8ba550ec947999c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30170: Refactor and simplify wrapping variables on Oracle

2019-02-11 Thread Django

#30170: Refactor and simplify wrapping variables on Oracle
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Oracle cx_Oracle | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #30174: Forgotten migrations in Django 2.1.6

2019-02-11 Thread Django

#30174: Forgotten migrations in Django 2.1.6
-+-
 Reporter:  Michiel Holtkamp |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  2.1.6 migration  | Triage Stage:
  auth   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Consolidating with #30175.

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

Re: [Django] #30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra files (was: Broken django 1.11.19 release for python2.7)

2019-02-11 Thread Django

#30175: Django 2.1.6, 2.0.11, and 1.11.19 were mispackaged with missing or extra
files
-+
 Reporter:  rm_  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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.5ee7918ef4df90cf1049f2b4056515a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30175: Broken django 1.11.19 release for python2.7

2019-02-11 Thread Django

#30175: Broken django 1.11.19 release for python2.7
-+
 Reporter:  rm_  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Patrick Cloke):

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

Re: [Django] #30176: 1.11.19 release on pypi has a contrib/admin/templatetags/base.py file

2019-02-11 Thread Django

#30176: 1.11.19  release on pypi  has a contrib/admin/templatetags/base.py file
---+--
 Reporter:  Emmanuel Cazenave  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Packaging  |  Version:  1.11
 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 Emmanuel Cazenave):

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


Comment:

 Yes.

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

Re: [Django] #29299: Add type hints (PEP 484) and variable annotations (PEP 526)

2019-02-11 Thread Django

#29299: Add type hints (PEP 484) and variable annotations (PEP 526)
-+-
 Reporter:  Andreas Galazis  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  2.0
 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):

 No updates. The discussion is on the mailing list linked in comment 2.

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

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

Re: [Django] #30174: Forgotten migrations in Django 2.1.6

2019-02-11 Thread Django

#30174: Forgotten migrations in Django 2.1.6
-+-
 Reporter:  Michiel Holtkamp |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  2.1.6 migration  | Triage Stage:
  auth   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by viktoradavid):

 2.0.11 is affected as well - that means all the versions released today.
 {{{
 Migrations for 'admin':
   /home/me/.virtualenvs/cms/lib/python3.7/site-
 packages/django/contrib/admin/migrations/0004_auto_20190211_1228.py
 - Alter field action_flag on logentry
 Migrations for 'auth':
   /home/me/.virtualenvs/cms/lib/python3.7/site-
 packages/django/contrib/auth/migrations/0012_auto_20190211_1228.py
 - Alter field name on group
 }}}

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

Re: [Django] #30175: Broken django 1.11.19 release for python2.7

2019-02-11 Thread Django

#30175: Broken django 1.11.19 release for python2.7
-+
 Reporter:  rm_  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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 Carlton Gibson):

 Yes. I can't currently account for the issue. Commits and tags look OK, as
 does repository status when checking out those tags. I will verify and re-
 issue where 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/061.a56c93de7315f94e21f9b98eb2d59b30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30176: 1.11.19 release on pypi has a contrib/admin/templatetags/base.py file

2019-02-11 Thread Django

#30176: 1.11.19  release on pypi  has a contrib/admin/templatetags/base.py file
---+--
 Reporter:  Emmanuel Cazenave  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Packaging  |  Version:  1.11
 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 rm_):

 Looks like a dup of #30175

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

Re: [Django] #30175: Broken django 1.11.19 release for python2.7

2019-02-11 Thread Django

#30175: Broken django 1.11.19 release for python2.7
-+
 Reporter:  rm_  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.11
 Severity:  Release blocker  |   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:  Uncategorized => Bug
 * component:  Uncategorized => Core (Other)
 * stage:  Unreviewed => Accepted


Comment:

 It appears there was an error in packaging the release.

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

Re: [Django] #30174: Forgotten migrations in Django 2.1.6

2019-02-11 Thread Django

#30174: Forgotten migrations in Django 2.1.6
-+-
 Reporter:  Michiel Holtkamp |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  2.1.6 migration  | Triage Stage:
  auth   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Ewald Moitzi):

 Replying to [comment:2 Bruno Alla]:
 > I noticed the same problem, but looking at the diff on GitHub, there
 doesn't seem to be any model change:
 > https://github.com/django/django/compare/2.1.5...2.1.6
 >
 > Was the wrong release published as 2.1.6?

 Looks like it, the missing auth migration for 1.11 wants to undo a change
 that was made in the master branch
 
(https://github.com/django/django/commit/e81955401885a93a459bcc130642b6ea5bf4ba4d
 #diff-49fc6cea24d46bdb27339c1aab392e32):
 {{{
 class Migration(migrations.Migration):

 dependencies = [
 ('auth', '0011_update_proxy_permissions'),
 ]

 operations = [
 migrations.AlterField(
 model_name='group',
 name='name',
 field=models.CharField(max_length=80, unique=True,
 verbose_name='name'),
 ),
 migrations.AlterField(
 model_name='user',
 name='last_name',
 field=models.CharField(blank=True, max_length=30,
 verbose_name='last name'),
 ),
 ]
 }}}

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

[Django] #30176: 1.11.19 release on pypi has a contrib/admin/templatetags/base.py file

2019-02-11 Thread Django

#30176: 1.11.19  release on pypi  has a contrib/admin/templatetags/base.py file
-+
   Reporter:  Emmanuel Cazenave  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Packaging  |Version:  1.11
   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  |
-+
 This file is not python2 compatible and is not in the git source tree on
 1.11.19 tag.

 This can lead to the following stacktrace :

 {{{#!python
 InvalidTemplateLibrary: Invalid template library specified. ImportError
 raised when trying to load 'django.contrib.admin.templatetags.base':
 cannot import name getfullargspec
 }}}

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

Re: [Django] #30175: Broken django 1.11.19 release for python2.7

2019-02-11 Thread Django

#30175: Broken django 1.11.19 release for python2.7
-+--
 Reporter:  rm_  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Description changed by rm_:

Old description:

> It looks like the distributed django 1.11.19 release does not match the
> code in 1.11.19 tag.
>
> Got this while running my test suite:
> {{{
>   File "/usr/local/lib/python2.7/site-packages/django/template/base.py",
> line 184, in __init__
> engine = Engine.get_default()
>   File "/usr/local/lib/python2.7/site-
> packages/django/utils/lru_cache.py", line 124, in wrapper
> result = user_function(*args, **kwds)
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/engine.py", line 76, in get_default
> django_engines = [engine for engine in engines.all()
>   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
> line 89, in all
> return [self[alias] for alias in self]
>   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
> line 80, in __getitem__
> engine = engine_cls(params)
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 30, in __init__
> options['libraries'] = self.get_templatetag_libraries(libraries)
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 48, in
> get_templatetag_libraries
> libraries = get_installed_libraries()
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 113, in
> get_installed_libraries
> for name in get_package_libraries(pkg):
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 130, in
> get_package_libraries
> "trying to load '%s': %s" % (entry[1], e)
> InvalidTemplateLibrary: Invalid template library specified. ImportError
> raised when trying to load 'django.contrib.admin.templatetags.base':
> cannot import name getfullargspec
> }}}
>
> But 1.11.19 tag on github does not have that file:
>
> {{{
> ~/src/django/django/contrib/admin/templatetags$ ls -ltrh *py
> -rw-r--r-- 1 rm rm0 dic  7  2015 __init__.py
> -rw-r--r-- 1 rm rm 2,1K feb 11 12:57 log.py
> -rw-r--r-- 1 rm rm 1,8K feb 11 12:57 admin_urls.py
> -rw-r--r-- 1 rm rm  304 feb 11 12:57 admin_static.py
> -rw-r--r-- 1 rm rm 3,0K feb 11 12:57 admin_modify.py
> -rw-r--r-- 1 rm rm  18K feb 11 12:57 admin_list.py
> }}}
>
> Downloading and unzipping:
> https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3
> -none-any.whl
>
> There's a `django.contrib.admin.templatetags.base` that is not in git:
>
> {{{
> $ django/contrib/admin/templatetags$ ls -ltrh *py
> -rw-r--r-- 1 rm rm0 gen  1  2014 __init__.py
> -rw-r--r-- 1 rm rm 1,3K feb 11 10:17 base.py
> -rw-r--r-- 1 rm rm  304 feb 11 10:28 admin_static.py
> -rw-r--r-- 1 rm rm 2,1K feb 11 10:30 log.py
> -rw-r--r-- 1 rm rm 1,8K feb 11 10:30 admin_urls.py
> -rw-r--r-- 1 rm rm 3,0K feb 11 10:30 admin_modify.py
> -rw-r--r-- 1 rm rm  18K feb 11 10:30 admin_list.py
> }}}

New description:

 It looks like the distributed django 1.11.19 release does not match the
 code in 1.11.19 tag.

 Got this while running my test suite:
 {{{
   File "/usr/local/lib/python2.7/site-packages/django/template/base.py",
 line 184, in __init__
 engine = Engine.get_default()
   File "/usr/local/lib/python2.7/site-packages/django/utils/lru_cache.py",
 line 124, in wrapper
 result = user_function(*args, **kwds)
   File "/usr/local/lib/python2.7/site-packages/django/template/engine.py",
 line 76, in get_default
 django_engines = [engine for engine in engines.all()
   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
 line 89, in all
 return [self[alias] for alias in self]
   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
 line 80, in __getitem__
 engine = engine_cls(params)
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 30, in __init__
 options['libraries'] = self.get_templatetag_libraries(libraries)
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 48, in
 get_templatetag_libraries
 libraries = get_installed_libraries()
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 113, in
 get_installed_libraries
 for name in

Re: [Django] #30175: Broken django 1.11.19 release for python2.7

2019-02-11 Thread Django

#30175: Broken django 1.11.19 release for python2.7
-+--
 Reporter:  rm_  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Description changed by rm_:

Old description:

> It looks like the distributed django 1.11.19 release does not match the
> code in 1.11.19 tag.
>
> Got this while running my test suite:
> ```
>   File "/usr/local/lib/python2.7/site-packages/django/template/base.py",
> line 184, in __init__
> engine = Engine.get_default()
>   File "/usr/local/lib/python2.7/site-
> packages/django/utils/lru_cache.py", line 124, in wrapper
> result = user_function(*args, **kwds)
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/engine.py", line 76, in get_default
> django_engines = [engine for engine in engines.all()
>   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
> line 89, in all
> return [self[alias] for alias in self]
>   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
> line 80, in __getitem__
> engine = engine_cls(params)
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 30, in __init__
> options['libraries'] = self.get_templatetag_libraries(libraries)
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 48, in
> get_templatetag_libraries
> libraries = get_installed_libraries()
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 113, in
> get_installed_libraries
> for name in get_package_libraries(pkg):
>   File "/usr/local/lib/python2.7/site-
> packages/django/template/backends/django.py", line 130, in
> get_package_libraries
> "trying to load '%s': %s" % (entry[1], e)
> InvalidTemplateLibrary: Invalid template library specified. ImportError
> raised when trying to load 'django.contrib.admin.templatetags.base':
> cannot import name getfullargspec
> ```
> But 1.11.19 tag on github does not have that file:
>
> ```
> ~/src/django/django/contrib/admin/templatetags$ ls -ltrh *py
> -rw-r--r-- 1 rm rm0 dic  7  2015 __init__.py
> -rw-r--r-- 1 rm rm 2,1K feb 11 12:57 log.py
> -rw-r--r-- 1 rm rm 1,8K feb 11 12:57 admin_urls.py
> -rw-r--r-- 1 rm rm  304 feb 11 12:57 admin_static.py
> -rw-r--r-- 1 rm rm 3,0K feb 11 12:57 admin_modify.py
> -rw-r--r-- 1 rm rm  18K feb 11 12:57 admin_list.py
> ```
>
> Downloading and unzipping:
> https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3
> -none-any.whl
>
> There's a `django.contrib.admin.templatetags.base` that is not in git:
>
> ```
> $ django/contrib/admin/templatetags$ ls -ltrh *py
> -rw-r--r-- 1 rm rm0 gen  1  2014 __init__.py
> -rw-r--r-- 1 rm rm 1,3K feb 11 10:17 base.py
> -rw-r--r-- 1 rm rm  304 feb 11 10:28 admin_static.py
> -rw-r--r-- 1 rm rm 2,1K feb 11 10:30 log.py
> -rw-r--r-- 1 rm rm 1,8K feb 11 10:30 admin_urls.py
> -rw-r--r-- 1 rm rm 3,0K feb 11 10:30 admin_modify.py
> -rw-r--r-- 1 rm rm  18K feb 11 10:30 admin_list.py
> ```

New description:

 It looks like the distributed django 1.11.19 release does not match the
 code in 1.11.19 tag.

 Got this while running my test suite:
 {{{
   File "/usr/local/lib/python2.7/site-packages/django/template/base.py",
 line 184, in __init__
 engine = Engine.get_default()
   File "/usr/local/lib/python2.7/site-packages/django/utils/lru_cache.py",
 line 124, in wrapper
 result = user_function(*args, **kwds)
   File "/usr/local/lib/python2.7/site-packages/django/template/engine.py",
 line 76, in get_default
 django_engines = [engine for engine in engines.all()
   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
 line 89, in all
 return [self[alias] for alias in self]
   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
 line 80, in __getitem__
 engine = engine_cls(params)
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 30, in __init__
 options['libraries'] = self.get_templatetag_libraries(libraries)
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 48, in
 get_templatetag_libraries
 libraries = get_installed_libraries()
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 113, in
 get_installed_libraries
 for name in

[Django] #30175: Broken django 1.11.19 release for python2.7

2019-02-11 Thread Django

#30175: Broken django 1.11.19 release for python2.7
---+
   Reporter:  rm_  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Uncategorized|Version:  1.11
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 It looks like the distributed django 1.11.19 release does not match the
 code in 1.11.19 tag.

 Got this while running my test suite:
 ```
   File "/usr/local/lib/python2.7/site-packages/django/template/base.py",
 line 184, in __init__
 engine = Engine.get_default()
   File "/usr/local/lib/python2.7/site-packages/django/utils/lru_cache.py",
 line 124, in wrapper
 result = user_function(*args, **kwds)
   File "/usr/local/lib/python2.7/site-packages/django/template/engine.py",
 line 76, in get_default
 django_engines = [engine for engine in engines.all()
   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
 line 89, in all
 return [self[alias] for alias in self]
   File "/usr/local/lib/python2.7/site-packages/django/template/utils.py",
 line 80, in __getitem__
 engine = engine_cls(params)
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 30, in __init__
 options['libraries'] = self.get_templatetag_libraries(libraries)
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 48, in
 get_templatetag_libraries
 libraries = get_installed_libraries()
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 113, in
 get_installed_libraries
 for name in get_package_libraries(pkg):
   File "/usr/local/lib/python2.7/site-
 packages/django/template/backends/django.py", line 130, in
 get_package_libraries
 "trying to load '%s': %s" % (entry[1], e)
 InvalidTemplateLibrary: Invalid template library specified. ImportError
 raised when trying to load 'django.contrib.admin.templatetags.base':
 cannot import name getfullargspec
 ```
 But 1.11.19 tag on github does not have that file:

 ```
 ~/src/django/django/contrib/admin/templatetags$ ls -ltrh *py
 -rw-r--r-- 1 rm rm0 dic  7  2015 __init__.py
 -rw-r--r-- 1 rm rm 2,1K feb 11 12:57 log.py
 -rw-r--r-- 1 rm rm 1,8K feb 11 12:57 admin_urls.py
 -rw-r--r-- 1 rm rm  304 feb 11 12:57 admin_static.py
 -rw-r--r-- 1 rm rm 3,0K feb 11 12:57 admin_modify.py
 -rw-r--r-- 1 rm rm  18K feb 11 12:57 admin_list.py
 ```

 Downloading and unzipping:
 
https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3
 -none-any.whl

 There's a `django.contrib.admin.templatetags.base` that is not in git:

 ```
 $ django/contrib/admin/templatetags$ ls -ltrh *py
 -rw-r--r-- 1 rm rm0 gen  1  2014 __init__.py
 -rw-r--r-- 1 rm rm 1,3K feb 11 10:17 base.py
 -rw-r--r-- 1 rm rm  304 feb 11 10:28 admin_static.py
 -rw-r--r-- 1 rm rm 2,1K feb 11 10:30 log.py
 -rw-r--r-- 1 rm rm 1,8K feb 11 10:30 admin_urls.py
 -rw-r--r-- 1 rm rm 3,0K feb 11 10:30 admin_modify.py
 -rw-r--r-- 1 rm rm  18K feb 11 10:30 admin_list.py
 ```

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

Re: [Django] #30174: Forgotten migrations in Django 2.1.6

2019-02-11 Thread Django

#30174: Forgotten migrations in Django 2.1.6
-+-
 Reporter:  mjholtkamp   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  2.1.6 migration  | Triage Stage:
  auth   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Bruno Alla):

 I noticed the same problem, but looking at the diff on GitHub, there
 doesn't seem to be any model change:
 https://github.com/django/django/compare/2.1.5...2.1.6

 Was the wrong release published as 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/068.8f671320a7dcf991447394fcc5e9e247%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30174: Forgotten migrations in Django 2.1.6

2019-02-11 Thread Django

#30174: Forgotten migrations in Django 2.1.6
-+-
 Reporter:  mjholtkamp   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  2.1.6 migration  | Triage Stage:
  auth   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Ewald Moitzi):

 Version 1.11.19 is also affected:


 {{{
 Migrations for 'admin':
   /var/lib/python3.6/site-
 packages/django/contrib/admin/migrations/0004_auto_20190211_1249.py
 - Alter field action_flag on logentry
 Migrations for 'auth':
   /var/lib/python3.6/site-
 packages/django/contrib/auth/migrations/0012_auto_20190211_1249.py
 - Alter field name on group
 - Alter field last_name on user
 }}}

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

[Django] #30174: Forgotten migrations in Django 2.1.6

2019-02-11 Thread Django

#30174: Forgotten migrations in Django 2.1.6
-+-
   Reporter: |  Owner:  nobody
  mjholtkamp |
   Type:  Bug| Status:  new
  Component: |Version:  2.1
  contrib.auth   |   Keywords:  2.1.6 migration
   Severity:  Normal |  auth
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Unless I'm mistaken, I think models were changed from 2.1.5 to 2.1.6 but
 new migration files were not created.

 This currently breaks our build because we check for 'forgotten'
 migrations, so we have to stick to 2.1.5 or change our check to exclude
 this migration.

 == Steps to reproduce
 {{{
 python3 -m venv venv
 source venv/bin/activate
 pip install django
 django-admin startproject mwe
 cd mwe
 python manage.py makemigrations
 }}}

 == Result
 {{{
 Migrations for 'auth':
   /Users/michiel/tmmmp/venv/lib/python3.6/site-
 packages/django/contrib/auth/migrations/0012_auto_20190211_1115.py
 - Alter field name on group
 }}}

 == Expected result
 {{{
 No changes detected
 }}}

 == Suggested fix
 run 'makemigrations', commit the file and re-publish :-)

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

55 matches

Mail list logo