date:20190927

Re: [Django] #28690: django.utils.http.parse_http_date two digit year check is incorrect

2019-09-27 Thread Django

#28690: django.utils.http.parse_http_date two digit year check is incorrect
-+
 Reporter:  Mads Jensen  |Owner:  Ad Timmering
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Ad Timmering):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c9a350fe7afc8d6a9144af592df80c56%40djangoproject.com.

Re: [Django] #28690: django.utils.http.parse_http_date two digit year check is incorrect

2019-09-27 Thread Django

#28690: django.utils.http.parse_http_date two digit year check is incorrect
-+
 Reporter:  Mads Jensen  |Owner:  Ad Timmering
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by Ad Timmering):

 * cc: Ad Timmering (added)
 * owner:  David Jovanović => Ad Timmering


Old description:

> RFC 850 does not mention this, but in RFC 7231 (and there's something
> similar in RFC 2822), there's the following quote:
>
>Recipients of a timestamp value in rfc850-date format, which uses a
>two-digit year, MUST interpret a timestamp that appears to be more
>than 50 years in the future as representing the most recent year in
>the past that had the same last two digits.
>
> The `< 70` is incorrect, and should have been `< 50`. I inserted a diff
> that applies.

New description:

 RFC 850 does not mention this, but in RFC 7231 (and there's something
 similar in RFC 2822), there's the following quote:

Recipients of a timestamp value in rfc850-date format, which uses a
two-digit year, MUST interpret a timestamp that appears to be more
than 50 years in the future as representing the most recent year in
the past that had the same last two digits.

 Current logic is hard coded to consider 0-69 to be in 2000-2069, and 70-99
 to be 1970-1999, instead of comparing versus the current year.

--

Comment:

 Taking the liberty to reassign due to inactivity (6 months) and adding a
 pull request with revised code and addressing feedback on prior PRs.
 Please add give your comments for any concerns:)

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

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

Re: [Django] #28816: Silent data loss when decreasing the max_length of a CharField

2019-09-27 Thread Django

#28816: Silent data loss when decreasing the max_length of a CharField
+-
 Reporter:  Gavin Wahl  |Owner:  Hasan Ramezani
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-

Comment (by Hasan Ramezani):

 Replying to [comment:7 felixxm]:
 > This solution doesn't prevent silencing data loss when decreasing
 `CharField.max_length` for a base field of `ArrayField` (see
 [https://github.com/django/django/pull/11817#discussion_r328013173
 comment]).

 [https://github.com/django/django/pull/11847 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f95ced9cd932796a40e0a698e74ea16e%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

2019-09-27 Thread Django

#20935: ePub documentation not valid
---+
 Reporter:  mabdullah  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by purplediane):

 * cc: purplediane (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a592f206ea84980765c63e3af8adb27a%40djangoproject.com.

Re: [Django] #20935: ePub documentation not valid

2019-09-27 Thread Django

#20935: ePub documentation not valid
---+
 Reporter:  mabdullah  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Carlton Gibson):

 Digging with Diane Chen at DjangoCon sprints, the Fragment identifier
 errors at least look to be some form of https://github.com/sphinx-
 doc/sphinx/issues/5070, which was in theory fixed over a year ago, so
 we've just asked for more info there. Hopefully we can get a resolution.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.469ce6eb84c20239b369bdf7c6d4aed5%40djangoproject.com.

Re: [Django] #26565: Allow Prefetch query to use .values()

2019-09-27 Thread Django

#26565: Allow Prefetch query to use .values()
-+-
 Reporter:  Maxime Lorant|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch, values | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Micah Lyle):

 I took a stab at this during the DjangoCon 2019 sprints.

 I had very limited experience with the prefetching/ORM internals before
 this, so there could be workarounds/solutions that I'm unaware of, but
 here's what I found so far.

 One thing I tried to tackle is handling the many to many case with just
 `values()`. My goal was to take the `'_prefetch_related_val_%s'` in the
 `queryset.extra(...)` call in the `get_prefetch_queryset()`
 `ManyRelatedManager` and add/apply it to whatever `values()` call was made
 and then join that by doing `pop()` from the dictionary instead of a
 `getattr` call (which would effectively give the developer the same query
 that they originally made by modifying it under the hood). I ran into some
 issues doing this though:

 "Any `extra()` call made after a `values()` call will have its extra
 selected fields ignored" (from the Django 2.2 docs)."

 This means that the `queryset.extra(...)` call in the `ManyRelatedManager`
 (which from my quick search appears to be the only remaining usage of
 `extra(...)` across the entire Django codebase (except the tests)) is
 effectively ignored, and even if I try to add a `.values(*existing_values,
 '_prefetch_related_val_%s')` call, it returns this error (from my example
 test/use case using the models from the prefetch tests):

 {{{
 queryset.values('id', 'title', '_prefetch_related_val_author_id')

 django.core.exceptions.FieldError: Cannot resolve keyword
 '_prefetch_related_val_author_id' into field. Choices are:
 _prefetch_related_val_author_id, authors, bio, bookwithyear,
 first_time_authors, id, read_by, title
 }}}

 Is this a bug? It says it can't resolve a field and then says that field
 is a choice.

 I thought about trying to workaround it by essentially "undoing" the
 `values()` part of the `queryset` and then reapplying it at the end with
 the value from the join table (which then gets `pop`ed, but I'm not sure
 if that's feasible/doable and what that would actually look like. Besides,
 this entire solution so far feels somewhat hacky in the first place.

 I think that whatever change makes this happen may require some sort of
 specification on the developer's end for how to apply the join from the
 prefetched dictionaries to the existing list of instances. Maybe even
 writing parts of a custom prefetcher and specifying that custom prefetcher
 as a fourth keyword argument (something I explored, but didn't get very
 far) to the `Prefetch` object, and then tweaking the logic in
 `prefetch_related_objects` and other functions to support using that
 fourth keyword argument.

 I'm also wondering if there's a way with Django 3.1+ technology/API to
 rewrite the `queryset.extra(...)` call in `ManyRelatedManager`. An out
 there idea I had was replacing the `queryset.extra(...)` call with a query
 on the through table and then doing a select related to the foreign key
 that is on the side we want to bring in to join to the existing instances
 (in the case above, we'd grab
 
`Book.authors.through.objects.filter_based_on_what_we_have_for_books_and_authors().select_related('book')`
 and then transform to a values result from there but that would (I think)
 prevent aggregations in the first place and run into a number of other
 problems.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.bc27cd3ad77e6c908b55310b13b74907%40djangoproject.com.

Re: [Django] #15910: show delete links for all admin inline formset rows

2019-09-27 Thread Django

#15910: show delete links for all admin inline formset rows
-+-
 Reporter:  Arthur de Jong   |Owner:  nobody
   |
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.3
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Nicolas Pantel):

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


Comment:

 I confirm, #29087 is a duplicate of this one.
 As you proposed a PR in the other ticket, and it has a better description,
 I close this one as duplicate.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/089.4962434eb7e108542864871cbb41feee%40djangoproject.com.

Re: [Django] #30780: Make "Getting Help" documentation much more prominent.

2019-09-27 Thread Django

#30780: Make "Getting Help" documentation much more prominent.
-+-
 Reporter:  Shai Berger  |Owner:  Abdul-
 Type:   |  Aziz-T
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Abdul-Aziz-T):

 * cc: Abdul-Aziz-T (added)
 * owner:  nobody => Abdul-Aziz-T
 * status:  new => assigned


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

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

Re: [Django] #30802: Manifest file is updated when running collectstatic with --dry-run

2019-09-27 Thread Django

#30802: Manifest file is updated when running collectstatic with --dry-run
-+-
 Reporter:  ryphill  |Owner:  Paul
 |  Stieber
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  ManifestStaticFilesStorage,|
  ManifestFilesMixin |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"5d63bf0bc338840cfbb10f3528cc5b5ca3170f9b" 5d63bf0b]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d63bf0bc338840cfbb10f3528cc5b5ca3170f9b"
 [3.0.x] Fixed #30802 -- Prevented manifest creation when running
 collectstatic in dry run mode.

 Backport of fa8fe09e4e2b538c5d50a559081861d5c0635d55 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.70b9ca7ceba712097a2b7bdc1f1a04ae%40djangoproject.com.

Re: [Django] #30802: Manifest file is updated when running collectstatic with --dry-run

2019-09-27 Thread Django

#30802: Manifest file is updated when running collectstatic with --dry-run
-+-
 Reporter:  ryphill  |Owner:  Paul
 |  Stieber
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  ManifestStaticFilesStorage,|
  ManifestFilesMixin |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"fa8fe09e4e2b538c5d50a559081861d5c0635d55" fa8fe09e]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa8fe09e4e2b538c5d50a559081861d5c0635d55"
 Fixed #30802 -- Prevented manifest creation when running collectstatic in
 dry run mode.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b6aa2c40c8f01f3c131513f61dd13186%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"4116b369b191f1830bbe761fa7fb29bf1becc8ef" 4116b369]:
 {{{
 #!CommitTicketReference repository=""
 revision="4116b369b191f1830bbe761fa7fb29bf1becc8ef"
 [2.2.x] Fixed #30597 -- Clarified how to unapply migrations.

 Backport of 45554fd5c5c6a536db3ce70d78646d3dc398cf08 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cd3f3dfd33319ae9d3d9d424ae04acea%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"0c655f1df2b167d7f24cf41910500850722b0c17" 0c655f1d]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c655f1df2b167d7f24cf41910500850722b0c17"
 [3.0.x] Fixed #30597 -- Clarified how to unapply migrations.

 Backport of 45554fd5c5c6a536db3ce70d78646d3dc398cf08 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a5f7d44f498a4edac55139b7c9510311%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"45554fd5c5c6a536db3ce70d78646d3dc398cf08" 45554fd5]:
 {{{
 #!CommitTicketReference repository=""
 revision="45554fd5c5c6a536db3ce70d78646d3dc398cf08"
 Fixed #30597 -- Clarified how to unapply migrations.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6fd99d9ab343a37e17539634847037f4%40djangoproject.com.

Re: [Django] #29501: Add support for ./manage.py dbshell -c SQL

2019-09-27 Thread Django

#29501: Add support for ./manage.py dbshell -c SQL
-+-
 Reporter:  Artem Skoretskiy |Owner:
 |  introquest
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Absolutely, feel free to work on issues obviously stalled. Just credit
 original patch writers if appropriate.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.61f19be1c75b1b55775b170e1ee3ccc5%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #29501: Add support for ./manage.py dbshell -c SQL

2019-09-27 Thread Django

#29501: Add support for ./manage.py dbshell -c SQL
-+-
 Reporter:  Artem Skoretskiy |Owner:
 |  introquest
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by David Vaz):

 So the PR is closed due to missing Tests and Documentation. Does anybody
 care that I take this?
 I could make a PR based on the original one and add tests and docs

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1106398fd88aca379f54243f6ebd22b9%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"1ac2f25ec091847a2db313210eb9743ed3b0dabf" 1ac2f25e]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ac2f25ec091847a2db313210eb9743ed3b0dabf"
 [2.2.x] Refs #30597 -- Added a warning about dependent apps when
 unapplying migrations.

 Backport of abba563c8635a52e8b657dee7708202e1f69433c 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ab85068b691dc6cb9cb8824b5eac0821%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"abba563c8635a52e8b657dee7708202e1f69433c" abba563c]:
 {{{
 #!CommitTicketReference repository=""
 revision="abba563c8635a52e8b657dee7708202e1f69433c"
 Refs #30597 -- Added a warning about dependent apps when unapplying
 migrations.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.005a7e8a2699410d59efd7c050fe1e16%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"5d40de08566cc7f0987ea414e06f37e6ed4e019a" 5d40de0]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d40de08566cc7f0987ea414e06f37e6ed4e019a"
 [3.0.x] Refs #30597 -- Added a warning about dependent apps when
 unapplying migrations.

 Backport of abba563c8635a52e8b657dee7708202e1f69433c 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f1d96ebcbbdf9a4a19a4d3a4870f43e4%40djangoproject.com.

Re: [Django] #28296: Add support for aggregation through subqueries

2019-09-27 Thread Django

#28296: Add support for aggregation through subqueries
-+-
 Reporter:  László Károlyi   |Owner:  B
 |  Martsberger
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11841 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.180fe9d648ad2efe971d2eb5fe3b235b%40djangoproject.com.

Re: [Django] #25762: Optimize numberformat.format

2019-09-27 Thread Django

Comment (by tim-mccurrach):

The approach used in the linked PR
(https://github.com/django/django/pull/5668/files) actually has a problem.
The following approach is used to avoid the rounding behaviour of the
builtin `format` function:
{{{
# If `number` is 10.888 and `decimal_pos` is 2 return
10.88 not 10.89.
format_string = '.%sf' % (decimal_pos + 1)
}}}
and the string is then truncated to `decimal_pos` decimals places.
However, for a number such as 10.999, this will still be rounded 11.00.
This is inconsistent with the behaviour of the rest of the function, which
truncates and doesn't round.

We therefore can't use the bultin `format` to do any kind of decimal
formatting as there doesn't appear (as it currently stands) to be an
option to truncate with it, however the speed advantages it offers can
still be used for the common case of seperating a number into thousands.

Using the test cases in `bench_number_format.py` linked above, an improved
function performs anywhere between 2x and 5x faster for most cases, and
again in the worst case is roughly the same (fluctuating between +2% and
-2% compared with the original function).

I'll add a new 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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.eda003801fef1f4c3138e5f516d27263%40djangoproject.com.

Re: [Django] #25762: Optimize numberformat.format

2019-09-27 Thread Django

#25762: Optimize numberformat.format
-+-
 Reporter:  Jaap Roes|Owner:  tim-
 Type:   |  mccurrach
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tim-mccurrach):

 * status:  new => assigned
 * owner:  nobody => tim-mccurrach


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.9e03e9d050d67578bfeecd1cd85fd25f%40djangoproject.com.

Re: [Django] #30813: dumpdata > flush > loaddata. (was: dumpdata > flush > loaddata)

2019-09-27 Thread Django

#30813: dumpdata > flush > loaddata.
-+-
 Reporter:  Maksych  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 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 felixxm):

 * status:  new => closed
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 `dumpdata` dumps primary keys by default which don't exist anymore after
 `flush`, so it's expected that such combination of commands fails. You
 should try:
 {{{
 django-admin dumpdata  --natural-foreign --natural-primary
 }}}
 to avoid dumping auto primary keys (see
 [https://docs.djangoproject.com/en/2.2/ref/django-admin/#dumpdata
 documentation]).

 Closing per TicketClosingReasons/UseSupportChannels.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.82c505f0a1a582fa0c490565b14aa836%40djangoproject.com.

Re: [Django] #30813: dumpdata > flush > loaddata

2019-09-27 Thread Django

#30813: dumpdata > flush > loaddata
-+-
 Reporter:  Maksych  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  2.2
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Maksych):

 * Attachment "photo_2019-09-27_18-12-35.jpg" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.7c99a8f57e7fb7fa61b2c1ad2de01aaa%40djangoproject.com.

[Django] #30813: dumpdata > flush > loaddata

2019-09-27 Thread Django

#30813: dumpdata > flush > loaddata
-+-
   Reporter:  Maksych|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Core   |Version:  2.2
  (Management commands)  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 After commands:
 > python manage.py dumpdata > db.json
 > python manage.py loaddata db.json
 All it`s okay, but after:
 > python manage.py flush
 > python manage.py loaddata db.json
 Have exception:
 > django.db.utils.IntegrityError: Problem installing fixture
 'D:\projects\python\django\ultrashop_backend\db.json': Could not load
 contenttypes.ContentType

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.801defecf82bf0a5b416334f741d9f3a%40djangoproject.com.

Re: [Django] #20601: intcomma and floatformat internationalization error

2019-09-27 Thread Django

#20601: intcomma and floatformat internationalization error
-+-
 Reporter:  c.schmitt@…  |Owner:  Ram
 |  Parameswaran
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, humanize,|
  contrib, float, floatcomma |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #28296: Add support for aggregation through subqueries

2019-09-27 Thread Django

#28296: Add support for aggregation through subqueries
-+-
 Reporter:  László Károlyi   |Owner:  B
 |  Martsberger
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by B Martsberger):

 * owner:  nobody => B Martsberger
 * status:  new => assigned


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

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

Re: [Django] #20601: intcomma and floatformat internationalization error

2019-09-27 Thread Django

#20601: intcomma and floatformat internationalization error
-+-
 Reporter:  c.schmitt@…  |Owner:  Ram
 |  Parameswaran
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, humanize,|
  contrib, float, floatcomma |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  (none) => Ram Parameswaran
 * status:  new => assigned
 * has_patch:  0 => 1
 * version:  1.10 => master


Comment:

 [https://github.com/django/django/pull/11834 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.816ddfd2282d7eb76dc0026109ff0e82%40djangoproject.com.

Re: [Django] #30798: models.E015 is raised when Meta.ordering contains "pk" of a related field.

2019-09-27 Thread Django

#30798: models.E015 is raised when Meta.ordering contains "pk" of a related 
field.
-+-
 Reporter:  felixxm  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak ):

 In [changeset:"0dc39ca8677347ecf25aebd056a130cdbfb8df21" 0dc39ca8]:
 {{{
 #!CommitTicketReference repository=""
 revision="0dc39ca8677347ecf25aebd056a130cdbfb8df21"
 [3.0.x] Fixed #30798 -- Fixed Meta.ordering validation for pk of related
 fields.

 Regression in 440505cb2cadbe1a5b9fba246bcde6c04f51d07e.

 Backport of 95a11578ce41de1e152fe7d173f109e280aebd6d 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.cf38fb53ef3e2892f45231b1eddba16a%40djangoproject.com.

Re: [Django] #30798: models.E015 is raised when Meta.ordering contains "pk" of a related field.

2019-09-27 Thread Django

#30798: models.E015 is raised when Meta.ordering contains "pk" of a related 
field.
-+-
 Reporter:  felixxm  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"95a11578ce41de1e152fe7d173f109e280aebd6d" 95a11578]:
 {{{
 #!CommitTicketReference repository=""
 revision="95a11578ce41de1e152fe7d173f109e280aebd6d"
 Fixed #30798 -- Fixed Meta.ordering validation for pk of related fields.

 Regression in 440505cb2cadbe1a5b9fba246bcde6c04f51d07e.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.52e122da155a16b65f3bebad8108a188%40djangoproject.com.

Re: [Django] #30798: models.E015 is raised when Meta.ordering contains "pk" of a related field.

2019-09-27 Thread Django

#30798: models.E015 is raised when Meta.ordering contains "pk" of a related 
field.
-+-
 Reporter:  felixxm  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak ):

 In [changeset:"da8f85aa82a8810cac8c0225c1f8862e5d9aea64" da8f85a]:
 {{{
 #!CommitTicketReference repository=""
 revision="da8f85aa82a8810cac8c0225c1f8862e5d9aea64"
 [3.0.x] Refs #30798 -- Prevented chaining fields from the same related
 model multiple times in model Meta.ordering.

 Backport of c7944628a1979453468d67818c63957532d396d8 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.bd7090526d4ea4d1827e53133bb6e10d%40djangoproject.com.

Re: [Django] #30798: models.E015 is raised when Meta.ordering contains "pk" of a related field.

2019-09-27 Thread Django

#30798: models.E015 is raised when Meta.ordering contains "pk" of a related 
field.
-+-
 Reporter:  felixxm  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 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 Mariusz Felisiak ):

 In [changeset:"c7944628a1979453468d67818c63957532d396d8" c7944628]:
 {{{
 #!CommitTicketReference repository=""
 revision="c7944628a1979453468d67818c63957532d396d8"
 Refs #30798 -- Prevented chaining fields from the same related model
 multiple times in model Meta.ordering.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6b09c42c855be9b1f9b1a1ebbf93f006%40djangoproject.com.

Re: [Django] #30597: Improve documentation on reseting an app's migrations to zero.

2019-09-27 Thread Django

#30597: Improve documentation on reseting an app's migrations to zero.
-+-
 Reporter:  Keryn Knight |Owner:  David Vaz
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #30216: Document BooleanField is no longer blank=True in Django 2.1+

2019-09-27 Thread Django

#30216: Document BooleanField is no longer blank=True in Django 2.1+
-+-
 Reporter:  Ed Morley|Owner:  David Vaz
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 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 felixxm):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.910f39b9816d2a5752c8914b921f375f%40djangoproject.com.

Re: [Django] #30216: Document BooleanField is no longer blank=True in Django 2.1+

2019-09-27 Thread Django

#30216: Document BooleanField is no longer blank=True in Django 2.1+
-+-
 Reporter:  Ed Morley|Owner:  David Vaz
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"1556a67c65c336ab12961c6123b129ac10e729b8" 1556a67c]:
 {{{
 #!CommitTicketReference repository=""
 revision="1556a67c65c336ab12961c6123b129ac10e729b8"
 [2.1.x] Fixed #30216 -- Doc'd that BooleanField is no longer blank=True in
 Django 2.1.

 Backport of a6972e88547ad5a51592f2b6d5046754c4b59394 from stable/2.2.x
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.353b3ae19e9d4d43e52d0d27d8ccaa41%40djangoproject.com.

Re: [Django] #30216: Document BooleanField is no longer blank=True in Django 2.1+

2019-09-27 Thread Django

#30216: Document BooleanField is no longer blank=True in Django 2.1+
-+-
 Reporter:  Ed Morley|Owner:  David Vaz
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"a6972e88547ad5a51592f2b6d5046754c4b59394" a6972e88]:
 {{{
 #!CommitTicketReference repository=""
 revision="a6972e88547ad5a51592f2b6d5046754c4b59394"
 [2.2.x] Fixed #30216 -- Doc'd that BooleanField is no longer blank=True in
 Django 2.1.
 }}}

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

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

Re: [Django] #30811: Django throws 'UnicodeEncodeError' when using Cyrillic symbols to override field upload_to.

2019-09-27 Thread Django

#30811: Django throws 'UnicodeEncodeError' when using Cyrillic symbols to 
override
field upload_to.
-+-
 Reporter:  Kirill   |Owner:  Kirill
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  UnicodeEncodeError,  | Triage Stage:
  Cyrillic, upload_to, File, |  Unreviewed
  FileField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  assigned => closed
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 Thanks for this report, however I don't think that it is an issue in
 Django, but rather in your implementation if you want to set `upload_to`
 dynamically you should set it to a callable, e.g.
 {{{

 def callable_upload_to(instance, filename):
 return posixpath.join(instance.title, filename)

 class Book(models.Model):
 pdf = FileField(..., upload_to=callable_upload_to)
 ...
 }}}

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

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

Re: [Django] #30807: test_extract_file_permissions test fails when umask is set to 000. (was: Test Suite fails with umask set to 000)

2019-09-27 Thread Django

#30807: test_extract_file_permissions test fails when umask is set to 000.
---+
 Reporter:  Brady  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 felixxm):

 * cc: Nick Pope (added)
 * stage:  Unreviewed => Accepted
 * component:  Uncategorized => Testing framework


Comment:

 Thanks for the report. I have a similar issue on Linux after setting
 `umask` to `0`, e.g.
 {{{
 FAIL: test_extract_file_permissions (utils_tests.test_archive.TestArchive)
 [foobar.tar.bz2]
 archive.extract() preserves file permissions.
 --
 Traceback (most recent call last):
   File "django/tests/utils_tests/test_archive.py", line 48, in
 test_extract_file_permissions
 self.assertEqual(os.stat(filepath).st_mode & mask, 0o664 & ~umask)
 AssertionError: 438 != 436
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6aebdcdd105d3cb9a4f3b340878c93aa%40djangoproject.com.

Re: [Django] #27921: Documentation of make_aware() with is_dst is misleading

2019-09-27 Thread Django

#27921: Documentation of make_aware() with is_dst is misleading
-+-
 Reporter:  Kevin Christopher|Owner:  Glenn
  Henry  |  Paquette
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b1eea8a73a4fcf13844559e24d147287aafae994" b1eea8a7]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1eea8a73a4fcf13844559e24d147287aafae994"
 [2.2.x] Fixed #27921 -- Clarified usage of make_aware() with is_dst
 argument.

 Backport of c2678e49759e5c4c329bff0eeca2886267005d21 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ac8390ee07a50fdcad0cc4d551908b73%40djangoproject.com.

Re: [Django] #27921: Documentation of make_aware() with is_dst is misleading

2019-09-27 Thread Django

#27921: Documentation of make_aware() with is_dst is misleading
-+-
 Reporter:  Kevin Christopher|Owner:  Glenn
  Henry  |  Paquette
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"311177d5d1cf0e372492896ee9a084f0fc39e569" 311177d5]:
 {{{
 #!CommitTicketReference repository=""
 revision="311177d5d1cf0e372492896ee9a084f0fc39e569"
 [3.0.x] Fixed #27921 -- Clarified usage of make_aware() with is_dst
 argument.

 Backport of c2678e49759e5c4c329bff0eeca2886267005d21 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.22c34587a3e669e7729939692048c9cd%40djangoproject.com.

Re: [Django] #27921: Documentation of make_aware() with is_dst is misleading

2019-09-27 Thread Django

#27921: Documentation of make_aware() with is_dst is misleading
-+-
 Reporter:  Kevin Christopher|Owner:  Glenn
  Henry  |  Paquette
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"c2678e49759e5c4c329bff0eeca2886267005d21" c2678e49]:
 {{{
 #!CommitTicketReference repository=""
 revision="c2678e49759e5c4c329bff0eeca2886267005d21"
 Fixed #27921 -- Clarified usage of make_aware() with is_dst argument.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.341d8e8c2bd651dfbf0981937712e639%40djangoproject.com.

41 matches

Mail list logo