Re: [Django] #30564: Cannot create custom field that returns a queryset AND uses pre_save().

2019-06-13 Thread Django 
#30564: Cannot create custom field that returns a queryset AND uses pre_save().
-+-
 Reporter:  Dan J Strohl |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
 * resolution:   => invalid


Comment:

 > Either way though, the bug I am reporting is that when returning a
 django queryset, via a custom field with a pre_save, it raises an
 AttributeError. Since these are all normal Django objects, and I'm using
 documented django approaches, I see this as a bug.

 Your custom field implementation is quite complicated. Custom fields with
 `pre_save()` works properly because you can treat any Django's field as a
 custom field e.g. `DateField`. It seems (but it is hard to tell without
 `pre_save_func()`) that in your case `pre_save()` returns `Query` which is
 not expected by `SQLInsertCompiler.prepare_value()`, that's why IMO it is
 an issue in your implementation/approach.

 > Since these are all normal Django objects.

 You cannot assume that Django internals will handle everything, even if
 these objects are defined by Django.

 I think that `return self.get_db_prep_value(value)` in `pre_save()` in
 branch with `pre_save_func()` should fix your 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/065.70da6bf7f642a2f576a11e5a07c225f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28752: Prevent django.setup() from running multiple times

2019-06-13 Thread Django 
#28752: Prevent django.setup() from running multiple times
-+-
 Reporter:  pascal chambon   |Owner:  pascal
 Type:   |  chambon
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by pascal chambon):

 * status:  new => assigned
 * owner:  nobody => pascal chambon


Comment:

 OK a few tweaks and bugfixes later, this PR seems now ready to me  B-)  ->
 https://github.com/django/django/pull/11440

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

Re: [Django] #28647: Add support for python-brace-format for variables within {% blocktrans %}

2019-06-13 Thread Django 
#28647: Add support for python-brace-format for variables within {% blocktrans 
%}
-+-
 Reporter:  Aidas Bendoraitis|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.11
  Internationalization   |
 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 Ole Laursen):

 Exactly how, I'm not sure, but this would definitely be worthwhile IMHO (I
 have a bunch of i18n projects, and yes, transition would be annoying, but
 something that could be fixed with a script). I'm sort of living with
 this, but today I hit a string that I have defined both in Python and in a
 template, and end up with two strings in the .po file:

 "Some thing %(foo)s"

 "Some thing {foo}"

 G.

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

Re: [Django] #24386: Querysets with filters and exclusions based on deep relations build invalid queries. (was: Querysets with filters and exclusions based on deep relations build invalid queries)

2019-06-13 Thread Django 
#24386: Querysets with filters and exclusions based on deep relations build 
invalid
queries.
-+-
 Reporter:  Raphael Gaschignard  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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):

 * status:  new => closed
 * resolution:   => duplicate
 * needs_tests:  1 => 0


Comment:

 Test added in 9ab1d5559681d3adde4fcfc98a19a7396ed6a42e.
 Fixed in f19a4945e1191e1696f1ad8e6cdc6f939c702728.

 Duplicate of #18726.

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

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

Re: [Django] #30547: Document what happens during model validation with Meta.constraints.

2019-06-13 Thread Django 
#30547: Document what happens during model validation with Meta.constraints.
-+-
 Reporter:  Dirk Groten  |Owner:  Swatantra
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:  constraints, | Triage Stage:  Accepted
  UniqueConstraint   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Swatantra):

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


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

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

Re: [Django] #30564: Cannot create custom field that returns a queryset AND uses pre_save().

2019-06-13 Thread Django 
#30564: Cannot create custom field that returns a queryset AND uses pre_save().
-+-
 Reporter:  Dan J Strohl |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Simon Charette):

 > The issue is that by using if hasattr(value, 'resolve_expression'), you
 cannot deterministically tell the difference between a SQL expression and
 a Django QuerySet.

 FWIW even if the `QuerySet` class doesn't completely implement the
 expression API it partially behaves like one; that's what makes usage of
 `QuerySet` as subqueries work (e.g.
 `.filter(foo__in=Foo.objects.filter(bar=1))`. In that sense `QuerySet` is
 an SQL expression.

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

Re: [Django] #30564: Cannot create custom field that returns a queryset AND uses pre_save().

2019-06-13 Thread Django 
#30564: Cannot create custom field that returns a queryset AND uses pre_save().
-+-
 Reporter:  Dan J Strohl |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Dan J Strohl):

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


Comment:

 Re-opening this, I think you mis-understood my point.  I understand that
 there are other approaches I can take, and I am looking at them  (and am
 happy for the suggestions).  however, the issue as I reported it actually
 IS with Django.  The issue is that by using ```if hasattr(value,
 'resolve_expression')```, you cannot deterministically tell the difference
 between a SQL expression and a Django QuerySet.  perhaps there is a way
 around this that I haven't seen, in which case, I apologize for missing
 it.  however by following the docs, when I return a QuerySet object, and
 when a pre_save method is used, the system raises an error since the
 QuerySet object matches your check, but is not an expression object. (or,
 if you ARE considering it an expression object for some reason, then the
 bug is that it does not have all of the OTHER required methods that the
 expected one does.).

 I understand that using ```if hasattr``` is the preferred approach, and I
 am not saying that the only fix is to change that, you could so a second
 check after it, change the method name in the queryset, have an
 alternative path that doesn't check for the method... etc... (all of which
 seem like much more work than changing the "if" check), but there may be
 other issues that I don't see (I haven't looked deeply enough at the code
 to see what other issues that would cause).  I don't know the flow or code
 well enough to say either way.  I simply brought it up as a potential
 approach.

 Either way though, the bug I am reporting is that when returning a django
 queryset, via a custom field with a pre_save, it raises an AttributeError.
 Since these are all normal Django objects, and I'm using documented django
 approaches, I see this as a bug.  If the returned object was something I
 controlled, I would simply re-name the "resolve_expression" method so it
 didn't' get caught, but I can't (easily) do that for a django QuerySet.

 I won't argue this again if you want to close this again, I'm not trying
 to get into a war here or anything.  I think it's pretty much a corner
 case, but I do see it as a bug and wanted to make sure I was at least
 being clear.

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

Re: [Django] #15042: 1.2.4 regression: send_mail doesn't access email recipient with no domain

2019-06-13 Thread Django 
#15042: 1.2.4 regression: send_mail doesn't access email recipient with no 
domain
-+-
 Reporter:  net147   |Owner:  Łukasz
 |  Rekucki
 Type:   |   Status:  closed
Component:  Core (Mail)  |  Version:  1.2
 Severity:   |   Resolution:  fixed
 Keywords:  blocker regression   | Triage Stage:  Accepted
  send_mail email|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson ):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 In [changeset:"1564e42ad397021093585147875a21dae1a3b3fc" 1564e42a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1564e42ad397021093585147875a21dae1a3b3fc"
 Refs #30512, #15042 -- Added local-only address to sanitize_email() tests
 cases.

 email.headerregistry.parser.get_mailbox() returns a token with a
 `token_type` attribute.

 If `token_type` is `’invalid-mailbox’` then RFC violations have been
 detected. Emails with only the local part, and no domain,  are correctly
 parsed but are marked as `’invalid-mailbox’`.

 As per #15042, local-only are supported, to enable sending to addresses on
 localhost.

 sanitize_email() does not currently check `token_type`. This test is added
 to avoid a regression in case this is revisited in the future.
 }}}

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

Re: [Django] #30512: Update mail backend to use modern standard library parsing approach.

2019-06-13 Thread Django 
#30512: Update mail backend to use modern standard library parsing approach.
-+-
 Reporter:  Joachim Jablon   |Owner:  Joachim
 Type:   |  Jablon
  Cleanup/optimization   |   Status:  closed
Component:  Core (Mail)  |  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 Carlton Gibson ):

 In [changeset:"1564e42ad397021093585147875a21dae1a3b3fc" 1564e42a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1564e42ad397021093585147875a21dae1a3b3fc"
 Refs #30512, #15042 -- Added local-only address to sanitize_email() tests
 cases.

 email.headerregistry.parser.get_mailbox() returns a token with a
 `token_type` attribute.

 If `token_type` is `’invalid-mailbox’` then RFC violations have been
 detected. Emails with only the local part, and no domain,  are correctly
 parsed but are marked as `’invalid-mailbox’`.

 As per #15042, local-only are supported, to enable sending to addresses on
 localhost.

 sanitize_email() does not currently check `token_type`. This test is added
 to avoid a regression in case this is revisited in the future.
 }}}

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

Re: [Django] #30512: Update mail backend to use modern standard library parsing approach.

2019-06-13 Thread Django 
#30512: Update mail backend to use modern standard library parsing approach.
-+-
 Reporter:  Joachim Jablon   |Owner:  Joachim
 Type:   |  Jablon
  Cleanup/optimization   |   Status:  closed
Component:  Core (Mail)  |  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 Carlton Gibson ):

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


Comment:

 In [changeset:"2628ea95151feb68f43a2a740e6fb0799a94b14b" 2628ea95]:
 {{{
 #!CommitTicketReference repository=""
 revision="2628ea95151feb68f43a2a740e6fb0799a94b14b"
 Fixed #30512 -- Used email.headerregistry.parser for parsing emails in
 sanitize_address().
 }}}

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

Re: [Django] #24386: Querysets with filters and exclusions based on deep relations build invalid queries

2019-06-13 Thread Django 
#24386: Querysets with filters and exclusions based on deep relations build 
invalid
queries
-+-
 Reporter:  Raphael Gaschignard  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Can Sarıgöl):

 I think, [https://github.com/django/django/pull/11142 this test] covers
 this.

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

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

Re: [Django] #24386: Querysets with filters and exclusions based on deep relations build invalid queries

2019-06-13 Thread Django 
#24386: Querysets with filters and exclusions based on deep relations build 
invalid
queries
-+-
 Reporter:  Raphael Gaschignard  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * status:  assigned => new
 * cc: Can Sarıgöl (added)
 * owner:  Can Sarıgöl => (none)


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

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

Re: [Django] #24386: Querysets with filters and exclusions based on deep relations build invalid queries

2019-06-13 Thread Django 
#24386: Querysets with filters and exclusions based on deep relations build 
invalid
queries
-+-
 Reporter:  Raphael Gaschignard  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * status:  new => assigned
 * owner:  nobody => Can Sarıgöl


Comment:

 this issue has been solved by
 
[https://github.com/django/django/blob/fc2536fe66c519b306f673672b795d16f87ed57d/django/db/models/sql/query.py#L1664
 this lines] of Simon's [https://github.com/django/django/pull/11062/files
 #diff-0edd853580d56db07e4020728d59e193R1659 PR]

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

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

Re: [Django] #12952: Models history doesn't use verbose names

2019-06-13 Thread Django 
#12952: Models history doesn't use verbose names
-+-
 Reporter:  Antonio Cangiano |Owner:  Sanyam
 Type:   |  Khurana
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Sanyam Khurana):

 * needs_better_patch:  1 => 0


Comment:

 Hi Carlton,

 The PR was approved a long ago.

 Can you please take a look and let me know if you think there is anything
 more to be done here?

 Thanks!

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

Re: [Django] #29548: Add official support for MariaDB.

2019-06-13 Thread Django 
#29548: Add official support for MariaDB.
-+-
 Reporter:  Tim Graham   |Owner:  felixxm
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"fc2536fe66c519b306f673672b795d16f87ed57d" fc2536f]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc2536fe66c519b306f673672b795d16f87ed57d"
 Refs #29548 -- Doc'd MariaDB support for GIS database functions.
 }}}

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

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

2019-06-13 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:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"fde9b7d35e4e185903cc14aa587ca870037941b1" fde9b7d]:
 {{{
 #!CommitTicketReference repository=""
 revision="fde9b7d35e4e185903cc14aa587ca870037941b1"
 Fixed #30128 -- Fixed handling timedelta timezone in database functions.
 }}}

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

Re: [Django] #30512: Update mail backend to use modern standard library parsing approach.

2019-06-13 Thread Django 
#30512: Update mail backend to use modern standard library parsing approach.
-+-
 Reporter:  Joachim Jablon   |Owner:  Joachim
 Type:   |  Jablon
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Mail)  |  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):

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