Re: [Django] #30387: Move more Windows-specific docs to use Pyhton official launcher

[Django]

#30387: Move more Windows-specific docs to use Pyhton official launcher
-+-
 Reporter:  Ramiro Morales   |Owner:  Ramiro
 Type:   |  Morales
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Ramiro Morales:

Old description:

> In #28343 / [changeset:37c17846ad] we:
>
> - Modified the documentation for new contributors to stop suggesting
> install Git Bash on Windows
> - Switched Windows command line  examples to use the offcial PEP397
> ''Python launcher'' shipped with Python >=  3.3
>
> But there is still room to expand this simplifcation to the
> `howto/windows.txt` document.

New description:

 In #28343 / [changeset:37c17846ad] we:

 - Modified the documentation for new contributors to stop suggesting
 install Git Bash on Windows
 - Switched Windows command line  examples to use the offcial PEP397
 ''Python launcher'' shipped with Python >=  3.3

 But there is still room to expand this simplifcation to the
 `howto/windows.txt` and `internals/contributing/writing-code/unit-
 tests.txt` documents.

--

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

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

Re: [Django] #30387: Move more Windows-specific docs to use Pyhton official launcher

[Django]

#30387: Move more Windows-specific docs to use Pyhton official launcher
-+-
 Reporter:  Ramiro Morales   |Owner:  Ramiro
 Type:   |  Morales
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ramiro Morales):

 * has_patch:  0 => 1


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

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

[Django] #30387: Move more Windows-specific docs to use Pyhton official launcher

[Django]

#30387: Move more Windows-specific docs to use Pyhton official launcher
-+-
   Reporter:  Ramiro |  Owner:  Ramiro Morales
  Morales|
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component: |Version:  master
  Documentation  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In #28343 / [changeset:37c17846ad] we:

 - Modified the documentation for new contributors to stop suggesting
 install Git Bash on Windows
 - Switched Windows command line  examples to use the offcial PEP397
 ''Python launcher'' shipped with Python >=  3.3

 But there is still room to expand this simplifcation to the
 `howto/windows.txt` document.

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

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

Re: [Django] #30380: Support mysql query objects as strings in addition to bytes, for PyMySQL support.

[Django]

#30380: Support mysql query objects as strings in addition to bytes, for PyMySQL
support.
-+-
 Reporter:  Nathan Klug  |Owner:  felixxm
 Type:  Bug  |   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 GitHub ):

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


Comment:

 In [changeset:"a41b09266dcdd01036d59d76fe926fe0386aaade" a41b092]:
 {{{
 #!CommitTicketReference repository=""
 revision="a41b09266dcdd01036d59d76fe926fe0386aaade"
 Fixed #30380 -- Handled bytes in MySQL backend for PyMySQL support.

 This commit partly reverts efd8a82e268a82b3ad0be77bd5b4548c30bcb4d7.
 }}}

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

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

Re: [Django] #30361: Watchman timing out when loading server

[Django]

#30361: Watchman timing out when loading server
---+
 Reporter:  Jacob Green|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Jacob Green):

 I tried out this change (increasing timeout to 5 seconds) and that fixed
 my issue:

 https://github.com/django/django/compare/stable/2.2.x...Jacobkg:Jacobkg-
 patch-1

 I'm happy to submit this as a patch if there is interest

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

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

[Django] #30386: Admin foreign key widgets don't quote keys

[Django]

#30386: Admin foreign key widgets don't quote keys
-+
   Reporter:  jclgoodwin |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |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  |
-+
 In django.contrib.admin.ModelAdmin, _changeform_view,  _delete_view and
 history_view and do unquote(object_id):

 
https://github.com/django/django/blob/917fd9d03fdd21538864af4b412ac30b36d99268/django/contrib/admin/options.py#L1537

 However, ForeignKeyRawIdWidget and RelatedFieldWidgetWrapper create links
 to this view without calling quote():

 
https://github.com/django/django/blob/89a2216486fa8a0513cbb1d49d2d587d4116c60b/django/contrib/admin/widgets.py#L191

 Steps to reproduce:

 1. Create two models: Topping with a CharField primary key, and Pizza with
 a ForeignKey to Topping. Register both models with the admin site.
 2. Create a Topping with the primary key '_40', and a Pizza with that
 topping
 3. In the admin site, go the the /change/ page for the Pizza, and click on
 the 'change' icon for the Topping foreign key, or (if using
 ForeignKeyRawIdWidget) the link to the Topping '_40'.
 4. See message 'Topping with ID "@" doesn't exist. Perhaps it was
 deleted?'.

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

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

Re: [Django] #30385: SearchVector's usage of CONCAT makes it impossible to index against.

[Django]

#30385: SearchVector's usage of CONCAT makes it impossible to index against.
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  2.2
 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 Simon Charette):

 * needs_better_patch:  1 => 0


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

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

[Django] #30385: SearchVector's usage of CONCAT makes it impossible to index against.

[Django]

#30385: SearchVector's usage of CONCAT makes it impossible to index against.
-+-
   Reporter:  Simon  |  Owner:  Simon Charette
  Charette   |
   Type:  Bug| Status:  assigned
  Component: |Version:  2.2
  contrib.postgres   |
   Severity:  Release|   Keywords:
  blocker|
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 `SearchVector` was changed in Django 2.2 to allow querying non-text fields
 (#29582) by using `CONCAT` which automatically cast such fields to text
 and deals with `NULL` value appropriately.

 This had the unintended side effect of making the generated SQL loose it's
 `IMMUTABLE` status as `CONCAT` can generate locale/TZ dependant output
 which makes the generated SQL expression impossible to index against.

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

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

Re: [Django] #29582: SearchVector doesn't support querying non-text fields

[Django]

#29582: SearchVector doesn't support querying non-text fields
-+-
 Reporter:  mickaelmarin |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Andrew, I went ahead and filed #30385 to track 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.c1d21f09f084896d5431c4407b0f57e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26658: "When Case" query generating rule in duplicate

[Django]

#26658: "When Case" query generating rule in duplicate
-+-
 Reporter:  imaia|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Could you try against the `master` branch? There was a few recent changes
 around grouping and aliasing that probably addressed this issue.

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

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

Re: [Django] #26658: "When Case" query generating rule in duplicate

[Django]

#26658: "When Case" query generating rule in duplicate
-+-
 Reporter:  imaia|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by artemnesterenko):

 * version:  1.9 => 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8ac98753e806b56d38cb764509acc831%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30373: "Save as new" with read-only fields. (was: "Save as new" with read-only fields)

[Django]

#30373: "Save as new" with read-only fields.
---+--
 Reporter:  Nicola Zilio   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by felixxm):

 * status:  new => closed
 * version:  1.11 => master
 * resolution:   => wontfix


Comment:

 Thanks for the report, however there is not much we can do. Read-only
 fields don't have form fields that's why submit doesn't take them into
 account. You can probably find some workaround (e.g. with hidden fields),
 please use one of
 [https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
 support channels].

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

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

Re: [Django] #30380: Support mysql query objects as strings in addition to bytes, for PyMySQL support.

[Django]

#30380: Support mysql query objects as strings in addition to bytes, for PyMySQL
support.
-+-
 Reporter:  Nathan Klug  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #29522: Make Serializers easier to modify. (was: Make Serializers easier to modify)

[Django]

#29522: Make Serializers easier to modify.
-+-
 Reporter:  Levi Cameron |Owner:  Emad
 Type:   |  Mokhtar
  Cleanup/optimization   |   Status:  assigned
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ee65fd9221d9106fcb3b670efd8d8329%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26658: "When Case" query generating rule in duplicate

[Django]

#26658: "When Case" query generating rule in duplicate
-+-
 Reporter:  imaia|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by artemnesterenko):

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


Comment:

 I confirm that this behavior is still taking place in Django 2.2.
 {{{#!python
   class CustomQuerySet(QuerySet):
 def annotate_statuses(self):
 moment = now()
 return self.annotate(
 status=Case(
 When(
 timestamp__lte=moment
 -
 timedelta(seconds=settings.OFFLINE_SECONDS_THRESHOLD),
 then=Value("OFFLINE"),
 ),
 When(
 idle__gte=settings.IDLE_SECONDS_THRESHOLD,
 then=Value("IDLE"),
 ),
 default=Value("ACTIVE"),
 output_field=CharField(),
 )
 )
 }}}
 Having this queryset the query:
 {{{#!python
 
Model.objects.annotate_statuses().values("status").annotate(count=Count("status"))
 }}}
 generates the following sql:
 {{{#!sql
 SELECT CASE
WHEN "my_table"."timestamp" <=
 '2019-04-19T09:23:04.681449+00:00'::timestamptz THEN 'OFFLINE'
WHEN "my_table"."idle" >= 300.0 THEN 'IDLE'
ELSE 'ACTIVE' ENDAS "status",
COUNT(CASE
  WHEN "my_table"."timestamp" <=
 '2019-04-19T09:23:04.681449+00:00'::timestamptz THEN 'OFFLINE'
  WHEN "my_table"."idle" >= 300.0 THEN 'IDLE'
  ELSE 'ACTIVE' END) AS "count"
 FROM "my_table"
 GROUP BY CASE
  WHEN "my_table"."timestamp" <=
 '2019-04-19T09:23:04.681449+00:00'::timestamptz THEN 'OFFLINE'
  WHEN "my_table"."idle" >= 300.0 THEN 'IDLE'
  ELSE 'ACTIVE' END;
 }}}
 I expect it to generate something similar to:
 {{{#!sql
 select count(*), status
 from (select CASE
  WHEN (timestamp <=
 '2019-04-19T09:23:04.681449+00:00'::timestamptz)
  THEN 'OFFLINE'
  WHEN (idle >= 300.0) THEN 'IDLE'
  ELSE 'ACTIVE' END as status
   from my_table
  )
 group by status;
 }}}

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

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

Re: [Django] #25507: count() crashes with a RawSQL annotation. (was: Can't count when using annotate(field=RawSQL(sql)) when sql is a constant)

[Django]

#25507: count() crashes with a RawSQL annotation.
-+-
 Reporter:  Antoine Catton   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  RawSQL filter ORM| Triage Stage:  Accepted
  sql|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * version:  1.8 => master
 * resolution:   => fixed


Comment:

 Fixed in 3f32154f40a855afa063095e3d091ce6be21f2c5.

 Can Thanks for checking that, it doesn't qualify for a backport.

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

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

Re: [Django] #25507: Can't count when using annotate(field=RawSQL(sql)) when sql is a constant

[Django]

#25507: Can't count when using annotate(field=RawSQL(sql)) when sql is a 
constant
-+-
 Reporter:  Antoine Catton   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  RawSQL filter ORM| Triage Stage:  Accepted
  sql|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"12b7956fc3735101fcad597047b80b57efb5048a" 12b7956f]:
 {{{
 #!CommitTicketReference repository=""
 revision="12b7956fc3735101fcad597047b80b57efb5048a"
 Refs #25507 -- Added tests for using QuerySet.count() with a RawSQL
 annotation.

 Fixed in 3f32154f40a855afa063095e3d091ce6be21f2c5
 }}}

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

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

Re: [Django] #30354: Filter not displayed when admin.RelatedOnlyFieldListFilter is used for auth.models.User

[Django]

#30354: Filter not displayed when admin.RelatedOnlyFieldListFilter is used for
auth.models.User
---+--
 Reporter:  rvernica   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by felixxm):

 * status:  new => closed
 * version:  2.1 => master
 * resolution:   => worksforme


Comment:

 Everything works for me on the current master (checked at
 49fb3f5f3ed8b37f2ae02d0fdc6980c4152c58e3). Maybe you have only one user
 related with `Foo`. List filter with only one value will not be displayed.

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

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

Re: [Django] #20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints

[Django]

#20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints
-+-
 Reporter:  dmadeley@…   |Owner:  Ian Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #30341: Add support for furlongs unit to Distance objects

[Django]

#30341: Add support for furlongs unit to Distance objects
+--
 Reporter:  Dustin Neighly  |Owner:  Dustin Neighly
 Type:  New feature |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  gis, distance   | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"49fb3f5f3ed8b37f2ae02d0fdc6980c4152c58e3" 49fb3f5f]:
 {{{
 #!CommitTicketReference repository=""
 revision="49fb3f5f3ed8b37f2ae02d0fdc6980c4152c58e3"
 Fixed #30341 -- Added support for the furlong unit in Distance.
 }}}

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

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

Re: [Django] #30371: sqlmigrate fails with string defaults on mysql

[Django]

#30371: sqlmigrate fails with string defaults on mysql
-+-
 Reporter:  Melvyn Sopacua   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  needsinfo
 Keywords:  regression   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Replying to [comment:6 Melvyn Sopacua]:
 > - compare mysql driver versions: pymysql 0.9.3

 Ah, ah... that is probably the explanation. It might be that pymysql
 doesn't return a bytestring from `quote()` which would explain the issue
 (to be confirmed). Django doesn't officially support pymysql (read also
 #30380). It's another issue where we might call `force_text` instead of
 `decode()`. However this section is a bit more performance-sensitive.

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

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

Re: [Django] #30382: force_insert flag is not passed when saving parents on inherited models. (was: force_insert not respected when saving parents)

[Django]

#30382: force_insert flag is not passed when saving parents on inherited models.
-+-
 Reporter:  Phill Tornroth   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

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


Comment:

 Sounds reasonable.

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

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

Re: [Django] #29582: SearchVector doesn't support querying non-text fields

[Django]

#29582: SearchVector doesn't support querying non-text fields
-+-
 Reporter:  mickaelmarin |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Andrew, I just [https://github.com/django/django/pull/11254 submitted a
 patch] that reverts the function to use the `||` operation and add a
 regression test to make sure the generated expression is usable for a
 functional GIN index if a `config` is generated. Please link to it when
 you create the 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.af0266f5387534eaaae7a4273cbc54f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30328: Integer field range validators crash when limit_value is callable.

[Django]

#30328: Integer field range validators crash when limit_value is callable.
-+-
 Reporter:  Harro|Owner:  Scott
 |  Fitsimones
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"95811c3de9334c313522982c3d125a8c2ff7ab72" 95811c3d]:
 {{{
 #!CommitTicketReference repository=""
 revision="95811c3de9334c313522982c3d125a8c2ff7ab72"
 [2.2.x] Fixed #30328 -- Fixed crash of IntegerField.validators when
 limit_value in a custom validator is callable.

 Backport of a14c0fda15db7e0eb982ac7b68d47b45fc95b4cb from master
 }}}

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

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

Re: [Django] #30328: Integer field range validators crash when limit_value is callable.

[Django]

#30328: Integer field range validators crash when limit_value is callable.
-+-
 Reporter:  Harro|Owner:  Scott
 |  Fitsimones
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"a14c0fda15db7e0eb982ac7b68d47b45fc95b4cb" a14c0fd]:
 {{{
 #!CommitTicketReference repository=""
 revision="a14c0fda15db7e0eb982ac7b68d47b45fc95b4cb"
 Fixed #30328 -- Fixed crash of IntegerField.validators when limit_value in
 a custom validator is callable.
 }}}

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

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