date:20191121

Re: [Django] #31022: Setup GitHub tracking links

2019-11-21 Thread Django

#31022: Setup GitHub tracking links
+--
 Reporter:  Johannes Hoppe  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Documentation   |  Version:  master
 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


Old description:

> Can someone setup automated tracking links from GitHub to Track?
>
> https://github.com/django/django/settings/key_links/new
>
> I don't know about the prefix, but maybe `TRACK-`? We should also
> probably document that somewhere, right?

New description:

 Can someone setup automated tracking links from GitHub to Trac?

 https://github.com/django/django/settings/key_links/new

 I don't know about the prefix, but maybe `TRAC-`? We should also probably
 document that somewhere, right?

--

Comment:

 This not an issue in Django so I'm marking this as invalid, nevertheless I
 added `ticket-` autolink references.

-- 
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.e27e6b4c36123f0ecfa2bc57033c1292%40djangoproject.com.

Re: [Django] #31019: The database backend specific checks could be bypassed when using multiple databases.

2019-11-21 Thread Django

#31019: The database backend specific checks could be bypassed when using 
multiple
databases.
-+-
 Reporter:  Shipeng Feng |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 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
-+-

Comment (by felixxm):

 `allow_migrate()` is [https://docs.djangoproject.com/en/2.2/topics/db
 /multi-db/#allow_migrate documented] also you should also read carefully
 the entire [https://docs.djangoproject.com/en/2.2/topics/db/multi-db
 Multiple databases topic].

-- 
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/064.afd1ea039e71eee5c7136b1eeb51bf08%40djangoproject.com.

[Django] #31022: Setup GitHub tracking links

2019-11-21 Thread Django

#31022: Setup GitHub tracking links
--+
   Reporter:  Johannes Hoppe  |  Owner:  nobody
   Type:  New feature | Status:  new
  Component:  Documentation   |Version:  master
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Can someone setup automated tracking links from GitHub to Track?

 https://github.com/django/django/settings/key_links/new

 I don't know about the prefix, but maybe `TRACK-`? We should also probably
 document that somewhere, right?

-- 
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/052.a6317fa9703380d748b09a280852e464%40djangoproject.com.

Re: [Django] #31019: The database backend specific checks could be bypassed when using multiple databases.

2019-11-21 Thread Django

#31019: The database backend specific checks could be bypassed when using 
multiple
databases.
-+-
 Reporter:  Shipeng Feng |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 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
-+-

Comment (by Shipeng Feng):

 I couldn't find any documentation for this, is this documented anywhere?
 Or we could add some notices about this in the documentation
 so that others won't encounter the same problem.

-- 
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/064.35e9e132c4bba4cc48aba8a0bbcec725%40djangoproject.com.

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

2019-11-21 Thread Django

#8467: For ManyToMany manager, we should convert objects being added or removed 
to
the pk type if they are not.
-+-
 Reporter:  Wonlay   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Duplicate entry, | Triage Stage:  Accepted
  add, remove, ManyToManyField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 https://github.com/django/django/pull/12123

-- 
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/064.c45b2dc59027c7462d6aaf4facc3e1f6%40djangoproject.com.

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

2019-11-21 Thread Django

#8467: For ManyToMany manager, we should convert objects being added or removed 
to
the pk type if they are not.
-+-
 Reporter:  Wonlay   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Duplicate entry, | Triage Stage:  Accepted
  add, remove, ManyToManyField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Actually, this is more than an optimization because it will still crash
 after 28712d8acfffa9cdabb88cb610bae14913fa185d on backends that don't have
 the `supports_ignore_conflicts` feature flag enabled (only Oracle).

 I'll submit a PR for it.

-- 
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/064.5ead4e630b9f78a042dd2605b82f5828%40djangoproject.com.

Re: [Django] #31010: Add subdomains of localhost to ALLOWED_HOSTS in DEBUG mode

2019-11-21 Thread Django

#31010: Add subdomains of localhost to ALLOWED_HOSTS in DEBUG mode
---+--
 Reporter:  thenewguy  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  2.2
 Severity:  Normal |   Resolution:  needsinfo
 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 thenewguy):

 For reference, the conversation chain has been started:
 https://groups.google.com/forum/#!topic/django-developers/xcoAF9Gm_dI

-- 
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.a03ace606e1b2775134fe2e25fa60f9e%40djangoproject.com.

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

2019-11-21 Thread Django

#8467: For ManyToMany manager, we should convert objects being added or removed 
to
the pk type if they are not.
-+-
 Reporter:  Wonlay   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Duplicate entry, | Triage Stage:  Accepted
  add, remove, ManyToManyField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 A regression test for the above optimization could be to
 `assertNumQueries(1)` on the `b.a.add(str(pk))` call when a `m2m_changed`
 signal is registered for the relationship. That is to disable the ''fast''
 insertion mechanism that is enabled on all backends except for Oracle.

-- 
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/064.37268d33b90f2a42b855d5fc258cbc3a%40djangoproject.com.

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

2019-11-21 Thread Django

Comment (by Simon Charette):

I'm pretty sure we can consider this fixed by
28712d8acfffa9cdabb88cb610bae14913fa185d.

Even if we don't perform the conversion to the pk type in

[https://github.com/django/django/blob/master/django/db/models/fields/related_descriptors.py#L1066-L1067
the branch handling non-model instances] of `_get_target_ids` we now
ignore conflicts on bulk insertions so the collision on insertion is now
ignored.

I guess we could adjust the branch as an optimization if we wanted to by
calling `target_field.to_python(obj)` by re-purposing this ticket as an
optimization.

--
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/064.916f8a063eb161e596d7c58237b5de5c%40djangoproject.com.

Re: [Django] #30995: Feature/docs: how should url converters decline to match for a named route?

2019-11-21 Thread Django

#30995: Feature/docs: how should url converters decline to match for a named 
route?
-+-
 Reporter:  Jack Cushman |Owner:  Jack
 |  Cushman
 Type:  New feature  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  reverse, urls,   | Triage Stage:  Accepted
  converter  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jack Cushman):

 * has_patch:  0 => 1


Comment:

 Here's a PR for review: [https://github.com/django/django/pull/12121 PR]

 Simon, thanks for finding those related links! This ticket is distinct
 from #16774, though. That one is about allowing views to raise
 `ContinueResolving` internally once control is handed off to them, which
 would be a much larger change to the internal resolution logic.

 This one involves adding a single `try: ... except ValueError: continue`
 to the {{{reverse()}}} logic to give url converters an explicit way to
 deny a match in {{{to_url()}}}, which they can already do by returning
 empty string or other non-regex-matching response, and which is consistent
 with the handling of {{{ValueError}}} in {{{to_python()}}}. As you can see
 from the new tests in the PR, Django already supports type-based reverse
 resolution in a variety of cases, and this PR just fills in one edge case.

 I do see how the two are related, though! Depending why someone wants to
 raise {{{ContinueResolving}}} from a view, they might be able to solve the
 same problem by raising {{{ValueError}}} from {{{converter.to_python}}}
 since converters landed in Django 2.0. That's not affected one way or
 another by this patch to {{{reverse()}}}, though.

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

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

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

2019-11-21 Thread Django

#8467: For ManyToMany manager, we should convert objects being added or removed 
to
the pk type if they are not.
-+-
 Reporter:  Wonlay   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Duplicate entry, | Triage Stage:  Accepted
  add, remove, ManyToManyField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Baptiste Mispelon):

 I was unable to reproduce this on a recent version (tag `3.0rc1` for
 example).

 I'm using the following test case (same models as in the original ticket):
 {{{
 from django.db import IntegrityError
 from django.test import TestCase

 from .models import A, B


 class Ticket8467TestCase(TestCase):
 def test_integrityerror(self):
 pk = A.objects.create().pk

 b = B.objects.create()
 b.a.add(str(pk))
 with self.assertRaises(IntegrityError):
 b.a.add(str(pk))
 }}}

 This test fails (meaning that an `IntegrityError` is not raised) on
 `3.0rc1` but passes for `2.2`.
 Using `git bisect`, I tracked it down to this commit:
 28712d8acfffa9cdabb88cb610bae14913fa185d.

 However it's not immediately clear to me why that commit would fix this
 ticket so I'm unsure whether I should close this ticket.

-- 
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/064.9bc96ed050357fdf893fa164f9c126ad%40djangoproject.com.

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
-+
 Reporter:  Kevin Brown  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 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:"947f8e3485b1406d18ea062fd275c083d7ffbed5" 947f8e3]:
 {{{
 #!CommitTicketReference repository=""
 revision="947f8e3485b1406d18ea062fd275c083d7ffbed5"
 [3.0.x] Fixed #31012 -- Reverted "Fixed #29056 -- Fixed HTML5 validation
 of required SelectDateWidget."

 This reverts commit f038214d917c982613f5a15db8dfe325b1f7479b.

 The initial issue was incorrect. Django 2.2, and before, did not
 generate invalid HTML as reported. With f03821 in place invalid HTML
 was generated.

 Thanks to Kevin Brown for follow-up report and investigation.
 Backport of ee4a19053a32d41cdd79e087b1968980804ce658 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/069.dd4d8ded181497a3281d8c2177150410%40djangoproject.com.

Re: [Django] #29056: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

Comment (by Mariusz Felisiak ):

In [changeset:"947f8e3485b1406d18ea062fd275c083d7ffbed5" 947f8e3]:
{{{
#!CommitTicketReference repository=""
revision="947f8e3485b1406d18ea062fd275c083d7ffbed5"
[3.0.x] Fixed #31012 -- Reverted "Fixed #29056 -- Fixed HTML5 validation
of required SelectDateWidget."

This reverts commit f038214d917c982613f5a15db8dfe325b1f7479b.

The initial issue was incorrect. Django 2.2, and before, did not
generate invalid HTML as reported. With f03821 in place invalid HTML
was generated.

Thanks to Kevin Brown for follow-up report and investigation.
Backport of ee4a19053a32d41cdd79e087b1968980804ce658 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/063.d036baf0beb0ec41ffab7c09cc991506%40djangoproject.com.

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
-+
 Reporter:  Kevin Brown  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"ee4a19053a32d41cdd79e087b1968980804ce658" ee4a1905]:
 {{{
 #!CommitTicketReference repository=""
 revision="ee4a19053a32d41cdd79e087b1968980804ce658"
 Fixed #31012 -- Reverted "Fixed #29056 -- Fixed HTML5 validation of
 required SelectDateWidget."

 This reverts commit f038214d917c982613f5a15db8dfe325b1f7479b.

 The initial issue was incorrect. Django 2.2, and before, did not
 generate invalid HTML as reported. With f03821 in place invalid HTML
 was generated.

 Thanks to Kevin Brown for follow-up report and investigation.
 }}}

-- 
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/069.42f8073a8baf3ad458d78fa1f4eb73c3%40djangoproject.com.

Re: [Django] #29056: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#29056: Required SelectDateWidget renders invalid HTML
+--
 Reporter:  Vlastimil Zíma  |Owner:  Hasan Ramezani
 Type:  Bug |   Status:  closed
Component:  Forms   |  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:"ee4a19053a32d41cdd79e087b1968980804ce658" ee4a1905]:
 {{{
 #!CommitTicketReference repository=""
 revision="ee4a19053a32d41cdd79e087b1968980804ce658"
 Fixed #31012 -- Reverted "Fixed #29056 -- Fixed HTML5 validation of
 required SelectDateWidget."

 This reverts commit f038214d917c982613f5a15db8dfe325b1f7479b.

 The initial issue was incorrect. Django 2.2, and before, did not
 generate invalid HTML as reported. With f03821 in place invalid HTML
 was generated.

 Thanks to Kevin Brown for follow-up report and investigation.
 }}}

-- 
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.f69eb941bd187c8c8557a90b70ec32a1%40djangoproject.com.

Re: [Django] #9762: template filter |date:"r" not valid RFC 2822 formatted when LANGUAGE_CODE different than english

2019-11-21 Thread Django

#9762: template filter |date:"r" not valid RFC 2822 formatted when LANGUAGE_CODE
different than english
--+
 Reporter:  Antonio Melé  |Owner:  kgrandis
 Type:  Bug   |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  date template filter  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Baptiste Mispelon):

 * needs_better_patch:  1 => 0
 * component:  Template system => Utilities


Comment:

 Pull request available at https://github.com/django/django/pull/12122

-- 
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.bea967871b64e0c236d2f932d316dfda%40djangoproject.com.

Re: [Django] #30413: admin_views.test_multidb fails with persistent test SQLite database.

2019-11-21 Thread Django

#30413: admin_views.test_multidb fails with persistent test SQLite database.
-+-
 Reporter:  Daniel Hahler|Owner:  Farhaan
 |  Bukhsh
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  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:"664c98f1f8c63a932a9c767a7364a6a1826799bb" 664c98f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="664c98f1f8c63a932a9c767a7364a6a1826799bb"
 Fixed #30413 -- Fixed test database signature on SQLite when test database
 name is provided.

 Previously, the same signature was created for multiple in-memory
 databases on SQLite when they had tests databases names
 DATABASES['TEST']['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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.88b77e602d28e97b4abfaf51cb2ecec3%40djangoproject.com.

Re: [Django] #30995: Feature/docs: how should url converters decline to match for a named route?

2019-11-21 Thread Django

#30995: Feature/docs: how should url converters decline to match for a named 
route?
-+-
 Reporter:  Jack Cushman |Owner:  Jack
 |  Cushman
 Type:  New feature  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  reverse, urls,   | Triage Stage:  Accepted
  converter  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 FWIW [https://groups.google.com/forum/#!searchin/django-
 developers/ContinueResolving%7Csort:date this was discussed before] and
 accepted in #16774

 The idea was to introduce new exceptions dedicated to this purpose, e.g.
 `ContinueResolving`. I guess this ticket should be closed as a 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/066.bd562337e097e58c5bcbb8f5fcd3bc55%40djangoproject.com.

Re: [Django] #30413: admin_views.test_multidb fails with persistent test SQLite database.

2019-11-21 Thread Django

#30413: admin_views.test_multidb fails with persistent test SQLite database.
-+-
 Reporter:  Daniel Hahler|Owner:  Farhaan
 |  Bukhsh
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  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/065.c0dbb841399f7a15c7ceaced5f632f09%40djangoproject.com.

[Django] #31021: migration doesn't work on multi database environment

2019-11-21 Thread Django

#31021: migration doesn't work on multi database environment
+
   Reporter:  haudoing  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.auth  |Version:  2.2
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 The tutorial said that we can omit to set the default database if default
 doesn't makes sense
 https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#defining-your-
 databases

 But the following script brake it
 
https://github.com/django/django/blob/stable/2.2.x/django/contrib/auth/migrations/0011_update_proxy_permissions.py

 on line 42, it use

 {{{
 with transaction.atomic():
 Permission.objects.filter(
 permissions_query,
 content_type=old_content_type,
 ).update(content_type=new_content_type)
 }}}

 This will brake the migration if default database doesn't set

-- 
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/051.acbdd66110cc2c3fab0078515a0e34fc%40djangoproject.com.

Re: [Django] #28535: Message on conflicting migrations is misleading for rebase workflows

2019-11-21 Thread Django

#28535: Message on conflicting migrations is misleading for rebase workflows
-+---
 Reporter:  karyon   |Owner:  Masashi SHIBATA
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 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
-+---
Changes (by Masashi SHIBATA):

 * version:  1.11 => 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/064.450fc24ccd2c6c8eb95afaa462f01024%40djangoproject.com.

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

2019-11-21 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 Johannes Hoppe):

 * cc: Johannes Hoppe (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/063.a5afe7960312b166223647be376b0ded%40djangoproject.com.

Re: [Django] #30032: Allow expressions to be used for default

2019-11-21 Thread Django

#30032: Allow expressions to be used for default
-+-
 Reporter:  Gavin Wahl   |Owner:  Johannes
 |  Hoppe
 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 Johannes Hoppe):

 * cc: Johannes Hoppe (added)
 * owner:  nobody => Johannes Hoppe
 * has_patch:  0 => 1
 * 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/067.d562a80afdd9e1a92e478328b9bf0fed%40djangoproject.com.

Re: [Django] #30974: Selenium asserts should be wait statements

2019-11-21 Thread Django

#30974: Selenium asserts should be wait statements
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 |  Hoppe
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Johannes Hoppe):

 * owner:  nobody => Johannes Hoppe
 * 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/067.550ca9b9586a40beea26d85065c982d7%40djangoproject.com.

Re: [Django] #31013: Remove jQuery dependency from SelectBox.js

2019-11-21 Thread Django

#31013: Remove jQuery dependency from SelectBox.js
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 Type:   |  Hoppe
  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 Johannes Hoppe):

 * 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/067.2e1279294c51ab381e3d1696239b130f%40djangoproject.com.

Re: [Django] #30995: Feature/docs: how should url converters decline to match for a named route?

2019-11-21 Thread Django

#30995: Feature/docs: how should url converters decline to match for a named 
route?
-+-
 Reporter:  Jack Cushman |Owner:  Jack
 |  Cushman
 Type:  New feature  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  reverse, urls,   | Triage Stage:  Accepted
  converter  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * owner:  nobody => Jack Cushman
 * status:  new => assigned


Comment:

 Hey Jack, super follow-up.

 > Sure! Haven't contributed before, but the contributor docs look great --
 I'll take a pass at it and see if I can figure it out.

 Great! Welcome aboard! 🚀

 If you need an input open a PR early and we'll do that.

 A docs clarification may be in order whilst you're in here. 🙂

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

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

Re: [Django] #30995: Feature/docs: how should url converters decline to match for a named route?

2019-11-21 Thread Django

#30995: Feature/docs: how should url converters decline to match for a named 
route?
-+-
 Reporter:  Jack Cushman |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  reverse, urls,   | Triage Stage:  Accepted
  converter  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jack Cushman):

 ''Is your second "Resolution based on values" example right? It should be
 number of positional args, rather then type, no?''

 Yeah, just for the sake of documenting this, the actual logic of
 {{{reverse()}}} is a little more sophisticated than the docs suggest.
 Reversing by name returns the last-defined url with the given name, where
 (a) the arg count or kwarg keywords match, and (b) the generated url
 matches the path or re_path's regex. The second test means that we match
 based on argument type as well as count in practice. While matching on
 type isn't documented (that I know of), I think it's implicit to the user
 expectation that {{{reverse()}}} should return URLs that resolve back to
 the matched path -- otherwise in basic {{{}}} cases you get a
 weird situation where passing the wrong value to {{{reverse()}}} appears
 to work but then returns a non-resolvable URL.

 I hadn't noticed, but that also means that resolving based on url
 converter type already works in some situations!

 {{{
 path('import/foo/', index, name='import'),  # {% url "import"
 "abc" %}
 path('import/bar/', index, name='import'),  # {% url "import"
 123 %}
 }}}

 The above works because {{{IntConverter}}} happens to follow the
 undocumented protocol that converters can decline a match by returning a
 string that doesn't match their regex, so reversing on "abc" falls through
 to the previous route.

 ''Then, yes, your suggestion to raise a ValueError seems plausible enough.
 Want to take that on?''

 Sure! Haven't contributed before, but the contributor docs look great --
 I'll take a pass at it and see if I can figure it out.

-- 
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.73a7845c475c7912a1a7cbd7141246d4%40djangoproject.com.

Re: [Django] #31020: Disabled ModelChoiceField produces an error in to_python

2019-11-21 Thread Django

#31020: Disabled ModelChoiceField produces an error in to_python
--+--
 Reporter:  John Supplee  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  2.2
 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
--+--

Comment (by Carlton Gibson):

 [https://docs.djangoproject.com/en/dev/internals/release-process
 /#supported-versions-policy It doesn't qualify for a backport under our
 Supported Versions Policy]. Django 3.0 will be released on Dec 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b48e7c824d489d11cab302fa8e68%40djangoproject.com.

Re: [Django] #31020: Disabled ModelChoiceField produces an error in to_python

2019-11-21 Thread Django

#31020: Disabled ModelChoiceField produces an error in to_python
--+--
 Reporter:  John Supplee  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  2.2
 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
--+--

Comment (by John Supplee):

 Why can't this bug be fixed in Django 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ed48b0856d12cba6835c9a8e9d0cfb87%40djangoproject.com.

Re: [Django] #31020: Disabled ModelChoiceField produces an error in to_python

2019-11-21 Thread Django

#31020: Disabled ModelChoiceField produces an error in to_python
--+--
 Reporter:  John Supplee  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  2.2
 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 Carlton Gibson):

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


Comment:

 Duplicate of #30014. (Fixed in Django 3.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/067.17a2470a02b138d492960d20fd664377%40djangoproject.com.

Re: [Django] #31019: The database backend specific checks could be bypassed when using multiple databases. (was: The database backend specific checks could be bypassed when using multiple databases wi

2019-11-21 Thread Django

#31019: The database backend specific checks could be bypassed when using 
multiple
databases.
-+-
 Reporter:  Shipeng Feng |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 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:

 You're router should define
 [https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#allow_migrate
 allow_migrate()] method that will return `True` only for the `customer`
 db.


 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/064.5c9fc7a0321e62b994fc2a5fd00dfe07%40djangoproject.com.

[Django] #31020: Disabled ModelChoiceField produces an error in to_python

2019-11-21 Thread Django

#31020: Disabled ModelChoiceField produces an error in to_python
+
   Reporter:  John Supplee  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Forms |Version:  2.2
   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 |
+
 When a form with a disabled `ModelChoiceField` with an initial value is
 validated it produces an error.

 It seems that disabled fields go through the data cleaning process and the
 `.to_python(value)` method is called.  For most fields that is not a
 problem as the value passed to the `to_python()` method is massaged and
 returned.  In the case of a `ModelChoiceField` the initial value passed is
 a `Model` object.  This causes `to_python()` to throw a `ValidationError`
 of:

  Select a valid choice. That choice is not one of the available
 choices.

 It seems that `to_python()` is expecting a text value from a POST.

 `ModelChoiceField.to_python()` needs to be modified to return the passed
 value if the field is disabled.

 The below code is from 2.2.7 with the addition of two new lines at the
 beginning of the method.

 {{{
 def to_python(self, value):
 if self.disabled:
 return value
 if value in self.empty_values:
 return None
 try:
 key = self.to_field_name or 'pk'
 value = self.queryset.get(**{key: value})
 except (ValueError, TypeError, self.queryset.model.DoesNotExist):
 raise ValidationError(self.error_messages['invalid_choice'],
 code='invalid_choice')
 return value
 }}}

-- 
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/052.070f8a9ad559faba8f633c6da78a0413%40djangoproject.com.

Re: [Django] #31019: The database backend specific checks could be bypassed when using multiple databases with one empty default database.

2019-11-21 Thread Django

#31019: The database backend specific checks could be bypassed when using 
multiple
databases with one empty default database.
-+-
 Reporter:  Shipeng Feng |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (System |  Version:  master
  checks)|
 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
-+-
Description changed by Shipeng Feng:

Old description:

> Here is the settings:
>
> {{{
> #!python
> DATABASES = {
> 'default': {},
> 'users': {
> 'NAME': 'user_data',
> 'ENGINE': 'django.db.backends.mysql',
> 'USER': 'mysql_user',
> 'PASSWORD': 'superS3cret'
> },
> }
> }}}
>
> Here is the related source code:
> https://github.com/django/django/blob/f97a6123c07de5099fdf8b7d00ef7d20ed354e07/django/db/models/fields/__init__.py#L340
>
> We only run checks for the first db, and the behavior of the first is
> undetermined (the first entry of a dictionary),
> if the first db is `default`, then we would only run dummy backend
> checks, mysql checks are bypassed.

New description:

 Here is the settings:

 {{{
 #!python
 DATABASES = {
 'default': {},
 'users': {
 'NAME': 'user_data',
 'ENGINE': 'django.db.backends.mysql',
 'USER': 'mysql_user',
 'PASSWORD': 'superS3cret'
 },
 }
 }}}

 Here is the related source code:
 
https://github.com/django/django/blob/f97a6123c07de5099fdf8b7d00ef7d20ed354e07/django/db/models/fields/__init__.py#L340

 We only run checks for the first db, and the behavior of the first db is
 undetermined (the first entry of a dictionary),
 if the first db is `default`, then we would only run dummy backend checks,
 mysql checks are bypassed.

--

-- 
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/064.c46104adcf7ddaa56822547999c6708b%40djangoproject.com.

Re: [Django] #31019: The database backend specific checks could be bypassed when using multiple databases with one empty default database.

2019-11-21 Thread Django

#31019: The database backend specific checks could be bypassed when using 
multiple
databases with one empty default database.
-+-
 Reporter:  Shipeng Feng |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (System |  Version:  master
  checks)|
 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
-+-
Description changed by Shipeng Feng:

Old description:

> Here is the settings:
>
> {{{
> #!python
> DATABASES = {
> 'default': {},
> 'users': {
> 'NAME': 'user_data',
> 'ENGINE': 'django.db.backends.mysql',
> 'USER': 'mysql_user',
> 'PASSWORD': 'superS3cret'
> },
> 'customers': {
> 'NAME': 'customer_data',
> 'ENGINE': 'django.db.backends.mysql',
> 'USER': 'mysql_cust',
> 'PASSWORD': 'veryPriv@ate'
> }
> }
> }}}
>
> Here is the related source code:
> https://github.com/django/django/blob/f97a6123c07de5099fdf8b7d00ef7d20ed354e07/django/db/models/fields/__init__.py#L340
>
> We only run checks for the first db, and the behavior of the first is
> undetermined (the first entry of a dictionary),
> if the first db is `default`, then we would only run dummy backend
> checks, mysql checks are bypassed.

New description:

 Here is the settings:

 {{{
 #!python
 DATABASES = {
 'default': {},
 'users': {
 'NAME': 'user_data',
 'ENGINE': 'django.db.backends.mysql',
 'USER': 'mysql_user',
 'PASSWORD': 'superS3cret'
 },
 }
 }}}

 Here is the related source code:
 
https://github.com/django/django/blob/f97a6123c07de5099fdf8b7d00ef7d20ed354e07/django/db/models/fields/__init__.py#L340

 We only run checks for the first db, and the behavior of the first is
 undetermined (the first entry of a dictionary),
 if the first db is `default`, then we would only run dummy backend checks,
 mysql checks are bypassed.

--

-- 
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/064.f9a8c6103c4d867eee2732291041201d%40djangoproject.com.

[Django] #31019: The database backend specific checks could be bypassed when using multiple databases with one empty default database.

2019-11-21 Thread Django

#31019: The database backend specific checks could be bypassed when using 
multiple
databases with one empty default database.
+
   Reporter:  Shipeng Feng  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (System checks)  |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 |
+
 Here is the settings:

 {{{
 #!python
 DATABASES = {
 'default': {},
 'users': {
 'NAME': 'user_data',
 'ENGINE': 'django.db.backends.mysql',
 'USER': 'mysql_user',
 'PASSWORD': 'superS3cret'
 },
 'customers': {
 'NAME': 'customer_data',
 'ENGINE': 'django.db.backends.mysql',
 'USER': 'mysql_cust',
 'PASSWORD': 'veryPriv@ate'
 }
 }
 }}}

 Here is the related source code:
 
https://github.com/django/django/blob/f97a6123c07de5099fdf8b7d00ef7d20ed354e07/django/db/models/fields/__init__.py#L340

 We only run checks for the first db, and the behavior of the first is
 undetermined (the first entry of a dictionary),
 if the first db is `default`, then we would only run dummy backend checks,
 mysql checks are bypassed.

-- 
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/049.63a10a89cbac7c0ed029286a65d41417%40djangoproject.com.

Re: [Django] #31016: Documentation: MySQL notes: utf8.

2019-11-21 Thread Django

#31016: Documentation: MySQL notes: utf8.
-+-
 Reporter:  minusf   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  mysql mariadb utf8   | Triage Stage:
  utf8mb4|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by minusf):

 Well if django cannot support `utf8mb4` out of the box at the moment, then
 I would argue it's even more important to have a warning about it in the
 same section of the documentation...

-- 
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/064.98f6164095dda426ee9228f26fede5ba%40djangoproject.com.

Re: [Django] #31016: Documentation: MySQL notes: utf8. (was: Documentation: MySQL notes: utf8)

2019-11-21 Thread Django

#31016: Documentation: MySQL notes: utf8.
-+-
 Reporter:  minusf   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  mysql mariadb utf8   | Triage Stage:
  utf8mb4|  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:   => duplicate
 * version:  2.2 => master
 * easy:  1 => 0
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Marking as a duplicate of #18392 because this change is a part of proposed
 [https://github.com/django/django/pull/8886 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/064.16020154fce18d095f6052431fc35b7f%40djangoproject.com.

Re: [Django] #30484: Add conditional expression support to CheckConstraint.

2019-11-21 Thread Django

#30484: Add conditional expression support to CheckConstraint.
-+-
 Reporter:  David Sanders|Owner:  Simon
 |  Charette
 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
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"e9a0e1d4f6ecfc4227acff74e1f56f288a0b30aa" e9a0e1d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="e9a0e1d4f6ecfc4227acff74e1f56f288a0b30aa"
 Fixed #30484 -- Added conditional expressions support to CheckConstraint.
 }}}

-- 
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.19da297cb396368a76275cd05b047451%40djangoproject.com.

Re: [Django] #25367: Allow expressions in .filter() calls

2019-11-21 Thread Django

#25367: Allow expressions in .filter() calls
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Matthew
 Type:   |  Schinckel
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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:"37e6c5b79bd0529a3c85b8c478e4002fd33a2a1d" 37e6c5b]:
 {{{
 #!CommitTicketReference repository=""
 revision="37e6c5b79bd0529a3c85b8c478e4002fd33a2a1d"
 Refs #25367 -- Moved conditional expression wrapping to the Exact lookup.
 }}}

-- 
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.280d2fc224d9b2a996fd9cb2123d9ecf%40djangoproject.com.

Re: [Django] #11964: Add the ability to use database-level CHECK CONSTRAINTS

2019-11-21 Thread Django

#11964: Add the ability to use database-level CHECK CONSTRAINTS
-+-
 Reporter:  Matthew Schinckel|Owner:  Ian Foote
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  check constraint | 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:"306b6875209cfedce2536a6679e69adee7c9bc6a" 306b6875]:
 {{{
 #!CommitTicketReference repository=""
 revision="306b6875209cfedce2536a6679e69adee7c9bc6a"
 Refs #11964 -- Removed SimpleCol in favor of Query(alias_cols).

 This prevent having to pass simple_col through multiple function calls
 by defining whether or not references should be resolved with aliases
 at the Query level.
 }}}

-- 
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.ccaad36ff64e67a1f15d9e1061b6e2b5%40djangoproject.com.

Re: [Django] #25367: Allow expressions in .filter() calls

2019-11-21 Thread Django

#25367: Allow expressions in .filter() calls
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Matthew
 Type:   |  Schinckel
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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:"f97a6123c07de5099fdf8b7d00ef7d20ed354e07" f97a6123]:
 {{{
 #!CommitTicketReference repository=""
 revision="f97a6123c07de5099fdf8b7d00ef7d20ed354e07"
 Refs #25367 -- Made Query.build_filter() raise TypeError on non-
 conditional expressions.
 }}}

-- 
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.9026b561a15449c63ac2dc3c8f6265ba%40djangoproject.com.

Re: [Django] #31017: Search on online Django documentation is not working for 2.2 and 3

2019-11-21 Thread Django

#31017: Search on online Django documentation is not working for 2.2 and 3
---+--
 Reporter:  Ramez Issac|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  2.2
 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:

 Thanks for this ticket, however this should be reported in
 [https://github.com/django/djangoproject.com/issues the issue tracker] for
 the djangoproject.com website.

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

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

[Django] #31017: Search on online Django documentation is not working for 2.2 and 3

2019-11-21 Thread Django

#31017: Search on online Django documentation is not working for 2.2 and 3
-+
   Reporter:  Ramez Issac|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  2.2
   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  |
-+
 Searching documentation site is showing 0 results for version 2.2 / 3 and
 dev
 Working on 2.1 and below

-- 
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/053.e4e95224530d0383ac2a0f4fa2be9adc%40djangoproject.com.

Re: [Django] #31017: Search on online Django documentation is not working for 2.2 and 3

2019-11-21 Thread Django

#31017: Search on online Django documentation is not working for 2.2 and 3
---+--
 Reporter:  Ramez Issac|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  2.2
 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 Ramez Issac):

 * Attachment "Selection_140.png" added.

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

Re: [Django] #30998: Make it easier to use the model instance in ChoiceWidget.create_option()

2019-11-21 Thread Django

#30998: Make it easier to use the model instance in ChoiceWidget.create_option()
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

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


Old description:

> I often find myself needing to add extra attributes to subwdiget HTML
> elements that depend on the model instance object. For example, HTML
> `data-*` attributes.
>
> Others have had similar needs and created their own solutions. For
> example:  field/>.
>
> As this isn't built-in, there have been some backward incompatible
> changes on some releases: #27758.
>
> This ticket proposes to make this feature built-in to remove the need for
> third party applications to copy this boilerplate.
>
> ---
>
> Right now, the `ModelChoiceField.iterator` and `ModelChoiceIterator
> aren't documented. We could take this opportunity to do so if desired.

New description:

 I often find myself needing to add extra attributes to subwdiget HTML
 elements that depend on the model instance object. For example, HTML
 `data-*` attributes.

 Others have had similar needs and created their own solutions. For
 example: .

 As this isn't built-in, there have been some backward incompatible changes
 on some releases: #27758.

 This ticket proposes to make this feature built-in to remove the need for
 third party applications to copy this boilerplate.

 ---

 Right now, the `ModelChoiceField.iterator` and `ModelChoiceIterator`
 aren't documented. We could take this opportunity to do so if desired.

--

Comment:

 Hi Jon. Yes, super.

 ([https://github.com/carltongibson/django-
 
filter/blob/9a11b0bb8c3aaf8275b586458ec7acffcaaea104/django_filters/fields.py#L214-L275
 We have this exact kind of thing in Django Filter].) I think it should be
 a documented pattern. The `data-*` attribute is a nice example.

-- 
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.9366a31f1e8ee5268f39d4ed9871abb2%40djangoproject.com.

[Django] #31016: Documentation: MySQL notes: utf8

2019-11-21 Thread Django

Currently the documentation recommends using the following SQL to create a
'utf8' database:

{{{
CREATE DATABASE CHARACTER SET utf8;
}}}

Claiming "This ensures all tables and columns will use UTF-8 by default."

Currently in mysql (and mariadb) `utf8` means only a subset of `UTF-8`. To
get the full range one must use `utf8mb4` (which will be the default
somewhere in mysql 8).

I think the advice should be amended to use `utf8mb4` as it is misleading
at the moment. Or at the very least the followup sentence should mention
that `utf8` creates only a subset of characters, and not all utf8 can be
stored in it.

--
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/049.31aed75eb66ceddb9bd2d5acc380a10c%40djangoproject.com.

[Django] #31015: loss of precision of geometry coordinates on Oracle 18

2019-11-21 Thread Django

#31015: loss of precision of geometry coordinates on Oracle 18
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  GIS  |Version:  2.2
   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 test fails on Oracle 18, but works on Oracle 12 and other backends:

 {{{
 def test_round_trip(self):
 g = City.objects.values_list(models.Value(Point(-87.650175,
 41.850385), models.PointField()), flat=True)[0]
 self.assertEqual(g.wkt, 'POINT (-87.650175 41.850385)')
 }}}

 {{{
 Traceback (most recent call last):
   File "/home/jenkins/workspace/pull-requests-
 oracle/database/oragis18/label/bionic-
 pr/python/python3.8/tests/gis_tests/geoapp/tests.py", line 228, in
 test_round_trip
 self.assertEqual(g.wkt, 'POINT (-87.650175 41.850385)')
 AssertionError: 'POINT (-87.650174 41.850385)' != 'POINT
 (-87.650175 41.850385)'
 - POINT (-87.650174 41.850385)
 ? ^
 + POINT (-87.650175 41.850385)
 ? ^
 }}}

 I'm not sure if we should fix it, since it might be treated like Oracle
 bug, but it looks like it can be fixed by using WKB instead of WKT in
 queries on Oracle.

-- 
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/053.3d205c1b3b5da2b1b672e275a3fa336d%40djangoproject.com.

Re: [Django] #31010: Add subdomains of localhost to ALLOWED_HOSTS in DEBUG mode

2019-11-21 Thread Django

#31010: Add subdomains of localhost to ALLOWED_HOSTS in DEBUG mode
---+--
 Reporter:  thenewguy  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  2.2
 Severity:  Normal |   Resolution:  needsinfo
 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 Carlton Gibson):

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


Comment:

 Interesting. Currently we have, in HttpRequest.get_host():

 {{{
 # Allow variants of localhost if ALLOWED_HOSTS is empty and
 DEBUG=True.
 allowed_hosts = settings.ALLOWED_HOSTS
 if settings.DEBUG and not allowed_hosts:
 allowed_hosts = ['localhost', '127.0.0.1', '[::1]']
 }}}

 Can I ask you to post to the DevelopersMailingList to canvas opinion?
 Assuming no blockers are raised it seems reasonable enough... (Reopen if
 accepted there.)

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

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

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
-+
 Reporter:  Kevin Brown  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 Severity:  Release blocker  |   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 Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 As per the PR, I'm minded to revert
 f038214d917c982613f5a15db8dfe325b1f7479b for 3.0 and allow a new ticket to
 add `required` handling as a New Feature.

-- 
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/069.56acfa8f3e593636d432d6bc1dcba33f%40djangoproject.com.

Re: [Django] #30484: Add conditional expression support to CheckConstraint.

2019-11-21 Thread Django

#30484: Add conditional expression support to CheckConstraint.
-+-
 Reporter:  David Sanders|Owner:  Simon
 |  Charette
 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):

 * 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/066.5036bbe54b9de5cc6a79ca8fa25b703a%40djangoproject.com.

Re: [Django] #29058: Adding 'null=True' to a PointField doesn't create working migration

2019-11-21 Thread Django

#29058: Adding 'null=True' to a PointField doesn't create working migration
-+-
 Reporter:  Yaman Ozakin |Owner:  Victor
 |  Munene
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango,   | Triage Stage:  Accepted
  pointfield |
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
 * version:  1.11 => 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.580a883b3d26e29e0d78f6c51f088eae%40djangoproject.com.

Re: [Django] #30625: DatabaseCache backend raises TypeError if get/delete received key as integer.

2019-11-21 Thread Django

#30625: DatabaseCache backend raises TypeError if get/delete received key as
integer.
-+-
 Reporter:  Hiroki Kiyohara  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  2.2
 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:"8a8ea93b98f927d198d713b7367925f82b4d70e8" 8a8ea93]:
 {{{
 #!CommitTicketReference repository=""
 revision="8a8ea93b98f927d198d713b7367925f82b4d70e8"
 [2.2.x] Fixed #30625 -- Doc'd cache.get()/delete() behavior change in
 Django 2.2.

 Backport of f69b32782e21642c6184162d888fcc17dd1dd85e 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/066.83d472d4c53f93e5413b33a3ee2fb82d%40djangoproject.com.

Re: [Django] #30625: DatabaseCache backend raises TypeError if get/delete received key as integer.

2019-11-21 Thread Django

#30625: DatabaseCache backend raises TypeError if get/delete received key as
integer.
-+-
 Reporter:  Hiroki Kiyohara  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  2.2
 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:"6e3ef9841313efa7ace79cde519c89965206cd4b" 6e3ef984]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e3ef9841313efa7ace79cde519c89965206cd4b"
 [3.0.x] Fixed #30625 -- Doc'd cache.get()/delete() behavior change in
 Django 2.2.

 Backport of f69b32782e21642c6184162d888fcc17dd1dd85e 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/066.e291d8caeab5fb2945e6e6d762913f3f%40djangoproject.com.

Re: [Django] #30625: DatabaseCache backend raises TypeError if get/delete received key as integer.

2019-11-21 Thread Django

#30625: DatabaseCache backend raises TypeError if get/delete received key as
integer.
-+-
 Reporter:  Hiroki Kiyohara  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  2.2
 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:"f69b32782e21642c6184162d888fcc17dd1dd85e" f69b3278]:
 {{{
 #!CommitTicketReference repository=""
 revision="f69b32782e21642c6184162d888fcc17dd1dd85e"
 Fixed #30625 -- Doc'd cache.get()/delete() behavior change in Django 2.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.85d91e2451600395bb594912c8a4e466%40djangoproject.com.

Re: [Django] #28535: Message on conflicting migrations is misleading for rebase workflows

2019-11-21 Thread Django

#28535: Message on conflicting migrations is misleading for rebase workflows
-+---
 Reporter:  karyon   |Owner:  Masashi SHIBATA
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 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
-+---
Changes (by Masashi SHIBATA):

 * type:  Cleanup/optimization => New feature
 * needs_tests:  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/064.8b48254774fa2626c541d330cda393fa%40djangoproject.com.

Re: [Django] #30996: Add AsWKB and AsWKT GIS functions. (was: add AsBinary and AsText GIS functions)

2019-11-21 Thread Django

#30996: Add AsWKB and AsWKT GIS functions.
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

-- 
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.caeb46fffb4c747e3ee2746e9aab5268%40djangoproject.com.

Re: [Django] #30916: Added support for functional constraints.

2019-11-21 Thread Django

#30916: Added support for functional constraints.
-+-
 Reporter:  Safwan Rahman|Owner:
 |  saadalsaad
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  constraint   | Triage Stage:  Accepted
  functional |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 saadalsaad, no. This ticket is about adding support for functional
 constraints not only about case insensitive check constraints. It's more
 generic.

-- 
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/070.135b8a2c1788fe67fdef5d5ee03baedb%40djangoproject.com.

Re: [Django] #30916: Added support for functional constraints.

2019-11-21 Thread Django

#30916: Added support for functional constraints.
-+-
 Reporter:  Safwan Rahman|Owner:
 |  saadalsaad
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  constraint   | Triage Stage:  Accepted
  functional |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by saadalsaad):

 from my understanding, we need to support for functional constraints by
 adding case_insensitive option to UniqueConstraint ?
 https://github.com/django/django/pull/12115

-- 
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/070.f28f21935eed5d9f724592b39023ad63%40djangoproject.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

2019-11-21 Thread Django

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  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):

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

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
-+
 Reporter:  Kevin Brown  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 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
-+
Changes (by Hasan Ramezani):

 * cc: Hasan Ramezani (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/069.f75ce694d4e364cc3abba0e1b1cd87e3%40djangoproject.com.

Re: [Django] #29056: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#29056: Required SelectDateWidget renders invalid HTML
+--
 Reporter:  Vlastimil Zíma  |Owner:  Hasan Ramezani
 Type:  Bug |   Status:  closed
Component:  Forms   |  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 Carlton Gibson):

 Worth noting for future reference from #31012:

 > It's also important to note that the HTML generated for the
 SelectDateWidget in previous versions of Django was valid per the HTML
 standard. They did not contain a placeholder label option, but because
 they were not a  they always contained an option with a
 selectedness set to true (usually the first option). This meant that the
 required attribute generated for them was useless, since it would never
 not have a value or be empty, but it did mean it was still valid HTML.

-- 
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.92934a6994583f4f80350559723e8325%40djangoproject.com.

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
-+
 Reporter:  Kevin Brown  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 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 Carlton Gibson):

 Update: good analysis Kevin, thank you, exactly on mark. To the 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/069.3207105b59a6075f380883c3121c9174%40djangoproject.com.

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
-+
 Reporter:  Kevin Brown  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 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
-+
Changes (by Carlton Gibson):

 * status:  closed => new
 * severity:  Normal => Release blocker
 * resolution:  duplicate =>
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 This isn't quite a duplicate: a regression was introduced in #31012. We'll
 track resolving that here.

 I'm reviewing this now, but will Accept and mark as RB, since Baptiste is
 on the case already.

 [https://github.com/django/django/pull/12116 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/069.5b461ae5ce442705a15adc7bf53d350a%40djangoproject.com.

Re: [Django] #29056: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#29056: Required SelectDateWidget renders invalid HTML
+--
 Reporter:  Vlastimil Zíma  |Owner:  Hasan Ramezani
 Type:  Bug |   Status:  closed
Component:  Forms   |  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 Carlton Gibson):

 * status:  new => closed
 * version:  3.0 => master
 * resolution:   => fixed
 * severity:  Release blocker => Normal


Comment:

 HI Baptiste. The new ticket is highlighting a regression introduced here.
 It's not a duplicate. But it will be a Release Blocker, yes. (I'm just
 Reviewing it now...)

-- 
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.b67ba58cc82abb554788d297cec3c1d5%40djangoproject.com.

Re: [Django] #31012: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#31012: Required SelectDateWidget renders invalid HTML
---+--
 Reporter:  Kevin Brown|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  3.0
 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 Baptiste Mispelon):

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


Comment:

 Hi,

 Thanks for the report.

 I've reopened the original ticket and updated its severity to "release
 blocker" so I will close this one as a duplicate and the discussion can
 continue over there.

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

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

Re: [Django] #29056: Required SelectDateWidget renders invalid HTML

2019-11-21 Thread Django

#29056: Required SelectDateWidget renders invalid HTML
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 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
-+-
Changes (by Baptiste Mispelon):

 * status:  closed => new
 * version:  master => 3.0
 * resolution:  fixed =>
 * severity:  Normal => Release blocker


Comment:

 According to #31012 (which I just closed as a duplicated), the fix for
 this ticket is not correct (and should probably be reverted).

 There's more detail in the duplicate ticket but if I understand correctly,
 the term "placeholder" in the spec does not refer to the "placeholder"
 attribute that other tags can have.
 A "placeholder" option is an `` tag with an empty value that has
 to be the first direct element of the ``.

 The duplicate ticket has a pull request at
 https://github.com/django/django/pull/12116.

-- 
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.ab03b0a0b0d2bdfec95811edabf63c5d%40djangoproject.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

2019-11-21 Thread Django

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  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
-+-
Changes (by Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


-- 
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.cadecaed44a01128b7cbea1b0333f7b4%40djangoproject.com.

[Django] #31014: add FromWKB and FromWKT GIS functions

2019-11-21 Thread Django

#31014: add FromWKB and FromWKT GIS functions
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  GIS  |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|
---+


-- 
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/053.df2e8912e44a8ea395c674ad64ca4d17%40djangoproject.com.

Re: [Django] #31013: Remove jQuery dependency from SelectBox.js

2019-11-21 Thread Django

#31013: Remove jQuery dependency from SelectBox.js
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 Type:   |  Hoppe
  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:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Carlton Gibson):

 * 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.7eeff9004c4adcde60f2ed11c8cf3cdb%40djangoproject.com.

69 matches

Mail list logo