Re: [Django] #32211: Add Codespaces Configuration

[Django]

#32211: Add Codespaces Configuration
---+--
 Reporter:  David Smith|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Uncategorized  |  Version:  3.1
 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 Mariusz Felisiak):

 * status:  new => closed
 * type:  Uncategorized => New feature
 * resolution:   => wontfix


Comment:

 I'm not sure about this idea. It seems controversial that Django will
 provide and maintain configuration files for dev environments only for
 specific IDE (Visual Studio). Moreover [https://docs.github.com/en/free-
 pro-team@latest/github/developing-online-with-codespaces/about-billing-
 for-codespaces users will be billed for storage and compute usage]. Feel-
 free to start a discussion on DevelopersMailingList if you don't agree.

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

[Django] #32211: Add Codespaces Configuration

[Django]

#32211: Add Codespaces Configuration
-+
   Reporter:  David Smith|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  3.1
   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  |
-+
 GitHub Codespaces is currently in Beta but should become generally
 available soon. It's been brought forward to Q4 on their
 [https://github.com/github/roadmap/issues/55 roadmap].

 You can setup a [https://docs.github.com/en/free-pro-team@latest/github
 /developing-online-with-codespaces/configuring-codespaces-for-your-
 project#creating-a-custom-codespace-configuration custom configuration]
 for each project.

 I was thinking it would be great to set this up. The aim would be to be
 able to click the `code` button on the repositry, let the environment open
 and right away be able to run the tests without any further setup. Further
 we can explore other databases as well, microsoft have a
 [https://github.com/microsoft/vscode-dev-
 containers/tree/master/containers/python-3-postgres container] with
 postgres already configured.

 I'm happy to investigate further if you think this would be a nice
 addition?

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

Re: [Django] #32200: Aggregating when grouping on an ExpressionWrapper omits the expression from the group by

[Django]

#32200: Aggregating when grouping on an ExpressionWrapper omits the expression 
from
the group by
-+-
 Reporter:  Gordon Wrigley   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   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:"166c0d2474a3b5e09e1dd96ec93bdbf08f0c65c2" 166c0d24]:
 {{{
 #!CommitTicketReference repository=""
 revision="166c0d2474a3b5e09e1dd96ec93bdbf08f0c65c2"
 [3.1.x] Fixed #32200 -- Fixed grouping by ExpressionWrapper() with Q
 objects.

 Thanks Gordon Wrigley for the report.

 Regression in df32fd42b84cc6dbba173201f244491b0d154a63.

 Backport of fe9c7ded2996364f853c524b4421274717d89d5f from master
 }}}

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

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

Re: [Django] #32200: Aggregating when grouping on an ExpressionWrapper omits the expression from the group by

[Django]

#32200: Aggregating when grouping on an ExpressionWrapper omits the expression 
from
the group by
-+-
 Reporter:  Gordon Wrigley   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   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:"fe9c7ded2996364f853c524b4421274717d89d5f" fe9c7ded]:
 {{{
 #!CommitTicketReference repository=""
 revision="fe9c7ded2996364f853c524b4421274717d89d5f"
 Fixed #32200 -- Fixed grouping by ExpressionWrapper() with Q objects.

 Thanks Gordon Wrigley for the report.

 Regression in df32fd42b84cc6dbba173201f244491b0d154a63.
 }}}

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

Re: [Django] #32208: add filter is unable to concatenate strings with lazy string

[Django]

#32208: add filter is unable to concatenate strings with lazy string
-+
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks. I attached a test.

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

Re: [Django] #32208: add filter is unable to concatenate strings with lazy string

[Django]

#32208: add filter is unable to concatenate strings with lazy string
-+--
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by Mariusz Felisiak):

 * Attachment "32208-tests.diff" added.

 Tests.

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

Re: [Django] #470: Add Field.db_default for defining database defaults

[Django]

#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:  sql schema   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Doug Harris):

 * cc: Doug Harris (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/061.bfa5a4bd4deef286ccd111db0a18314d%40djangoproject.com.

Re: [Django] #32210: Django Admin with Inlines not using UUIDField default value

[Django]

#32210: Django Admin with Inlines not using UUIDField default value
---+--
 Reporter:  joetheone  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.1
 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 joetheone:

Old description:

> Hello,
>
> I am a long time django user, first time bug reporter, so please let me
> know if I need to do anything else to help get this bug fixed :)
>
> I am using Django 3.1.3 and python 3.8.5 and have cerated a toy project
> to illustrate the bug. I have the following models:
>

> {{{
> class UUIDModel(models.Model):
> pkid = models.BigAutoField(primary_key=True, editable=False)
> id = models.UUIDField(default=uuid.uuid4, editable=False,
> unique=True)
>
> class Meta:
> abstract = True
>
> class Thing(UUIDModel):
> name = models.CharField(max_length=191)
>
> class SubThing(models.Model):
> name = models.CharField(max_length=191)
> thing = models.ForeignKey(
> 'bugapp.Thing',
> to_field='id',
> on_delete = models.CASCADE,
> related_name='subthings',
> )
> }}}
>
> And the following admin.py file:
>

> {{{
> class SubThingInline(admin.StackedInline):
> model = SubThing
>
> @admin.register(Thing)
> class ThingAdmin(admin.ModelAdmin):
> list_display = ('name',)
> ordering = ('pkid',)
> #search_fields = ('name',)
> inlines = (SubThingInline,)
> }}}
>
> When logging into the admin, if you delete all of the entries for
> "subthings", add a name, and save the model, it will work. As soon as you
> try to add a subthing alongside the main Thing, it fails with the
> following exception:
>
> https://dpaste.com/8EU4FF6RW
>
> It shows that the value of "id" in the Thing model is being set to null.
>
> I believe this is a bug in django.
>
> Thanks!

New description:

 Hello,

 I am a long time django user, first time bug reporter, so please let me
 know if I need to do anything else to help get this bug fixed :)

 I am using Django 3.1.3 and python 3.8.5 and have cerated a toy project to
 illustrate the bug. I have the following models:


 {{{
 class UUIDModel(models.Model):
 pkid = models.BigAutoField(primary_key=True, editable=False)
 id = models.UUIDField(default=uuid.uuid4, editable=False, unique=True)

 class Meta:
 abstract = True

 class Thing(UUIDModel):
 name = models.CharField(max_length=191)

 class SubThing(models.Model):
 name = models.CharField(max_length=191)
 thing = models.ForeignKey(
 'bugapp.Thing',
 to_field='id',
 on_delete = models.CASCADE,
 related_name='subthings',
 )
 }}}

 And the following admin.py file:


 {{{
 class SubThingInline(admin.StackedInline):
 model = SubThing

 @admin.register(Thing)
 class ThingAdmin(admin.ModelAdmin):
 list_display = ('name',)
 ordering = ('pkid',)
 inlines = (SubThingInline,)
 }}}

 When logging into the admin, if you delete all of the entries for
 "subthings", add a name, and save the model, it will work. As soon as you
 try to add a subthing alongside the main Thing, it fails with the
 following exception:

 https://dpaste.com/8EU4FF6RW

 It shows that the value of "id" in the Thing model is being set to null.

 I believe this is a bug in django.

 Thanks!

--

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

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

Re: [Django] #32210: Django Admin with Inlines not using UUIDField default value

[Django]

#32210: Django Admin with Inlines not using UUIDField default value
---+--
 Reporter:  joetheone  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.1
 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 joetheone):

 * Attachment "bugdemo.tbz" added.

 I made a toy project containing all the code to reproduce the error and
 zipped 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/067.e5f3e95a1a1eeef1faa8434cbde7d617%40djangoproject.com.

[Django] #32210: Django Admin with Inlines not using UUIDField default value

[Django]

#32210: Django Admin with Inlines not using UUIDField default value
-+
   Reporter:  joetheone  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.1
   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  |
-+
 Hello,

 I am a long time django user, first time bug reporter, so please let me
 know if I need to do anything else to help get this bug fixed :)

 I am using Django 3.1.3 and python 3.8.5 and have cerated a toy project to
 illustrate the bug. I have the following models:


 {{{
 class UUIDModel(models.Model):
 pkid = models.BigAutoField(primary_key=True, editable=False)
 id = models.UUIDField(default=uuid.uuid4, editable=False, unique=True)

 class Meta:
 abstract = True

 class Thing(UUIDModel):
 name = models.CharField(max_length=191)

 class SubThing(models.Model):
 name = models.CharField(max_length=191)
 thing = models.ForeignKey(
 'bugapp.Thing',
 to_field='id',
 on_delete = models.CASCADE,
 related_name='subthings',
 )
 }}}

 And the following admin.py file:


 {{{
 class SubThingInline(admin.StackedInline):
 model = SubThing

 @admin.register(Thing)
 class ThingAdmin(admin.ModelAdmin):
 list_display = ('name',)
 ordering = ('pkid',)
 #search_fields = ('name',)
 inlines = (SubThingInline,)
 }}}

 When logging into the admin, if you delete all of the entries for
 "subthings", add a name, and save the model, it will work. As soon as you
 try to add a subthing alongside the main Thing, it fails with the
 following exception:

 https://dpaste.com/8EU4FF6RW

 It shows that the value of "id" in the Thing model is being set to null.

 I believe this is a bug in django.

 Thanks!

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

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

Re: [Django] #32209: Prepend project name to default admin url

[Django]

#32209: Prepend project name to default admin url
-+--
 Reporter:  Collin Anderson  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+--
Changes (by Carlton Gibson):

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


Comment:

 Hi. This exact topic is currently under discussion on the
 DevelopersMailingList here https://groups.google.com/g/django-
 developers/c/a4_VY4YzB2I
 Given that, I think we need to see how the discussion resolves before
 moving forward.
 I'll post there linking here.
 Thanks

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

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

Re: [Django] #32204: Quick Filter for the Admin Sidebar

[Django]

#32204: Quick Filter for the Admin Sidebar
-+--
 Reporter:  Maxim Milovanov  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 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:  1
-+--
Changes (by Ryan Hiebert):

 * cc: Ryan Hiebert (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/068.1ad00b3360861ad3f75e1a653e598d98%40djangoproject.com.

Re: [Django] #32172: Adapt signals to allow async handlers

[Django]

#32172: Adapt signals to allow async handlers
-+-
 Reporter:  Carlton Gibson   |Owner:
 |  Konstantin Volkov
 Type:  New feature  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  async| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


Comment:

 I'm going to mark this RFC — I don't think it's far away.

 We want to do a small amount of profiling before we say the final OK, but
 it can live off the review list for a while during that.

-- 
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/071.bf018aa2fa59bfa238859d692ab22ff9%40djangoproject.com.

Re: [Django] #32209: Prepend project name to default admin url

[Django]

#32209: Prepend project name to default admin url
-+--
 Reporter:  Collin Anderson  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+--
Changes (by Collin Anderson):

 * cc: Collin Anderson (added)
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


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

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

[Django] #32209: Prepend project name to default admin url

[Django]

#32209: Prepend project name to default admin url
---+
   Reporter:  Collin Anderson  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  contrib.admin|Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+
 Makes it harder for automated bots and scanners to try to login to admin
 website.

 Like so:
 https://github.com/django/django/compare/master...collinanderson:patch-14

-- 
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/057.f8c46e6d03ced9ba271adfabfc8fc345%40djangoproject.com.

[Django] #32208: add filter is unable to concatenate strings with lazy string

[Django]

#32208: add filter is unable to concatenate strings with lazy string
---+
   Reporter:  Claude Paroz |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Template system  |Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+
 If you try to concatenate a string with a lazy string with the `add`
 template filter, the result is always the empty string  because the `add`
 filter generates an exception (`TypeError: can only concatenate str (not
 "__proxy__") to str`).

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

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

Re: [Django] #32200: Aggregating when grouping on an ExpressionWrapper omits the expression from the group by

[Django]

#32200: Aggregating when grouping on an ExpressionWrapper omits the expression 
from
the group by
-+-
 Reporter:  Gordon Wrigley   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * needs_docs:  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/065.c0c781bf38e93532ae9245ab7ba017ba%40djangoproject.com.

Re: [Django] #32202: django-admin runserver and get_child_arguments() crashes on Windows and Python < 3.8.

[Django]

#32202: django-admin runserver and get_child_arguments() crashes on Windows and
Python < 3.8.
-+-
 Reporter:  andrey-zotov |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  3.1
  commands)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson ):

 In [changeset:"012822c7f9eb2be2f44cb3235eb66ca207d37133" 012822c7]:
 {{{
 #!CommitTicketReference repository=""
 revision="012822c7f9eb2be2f44cb3235eb66ca207d37133"
 [3.1.x] Fixed #32202 -- Fixed autoreloader argument generation for Windows
 with Python 3.7-.

 Backport of ead37dfb580136cc27dbd487a1f1ad90c9235d15 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/070.991bc42b5771c19034d1ffc2c2002158%40djangoproject.com.

Re: [Django] #32202: django-admin runserver and get_child_arguments() crashes on Windows and Python < 3.8.

[Django]

#32202: django-admin runserver and get_child_arguments() crashes on Windows and
Python < 3.8.
-+-
 Reporter:  andrey-zotov |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  3.1
  commands)  |
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"ead37dfb580136cc27dbd487a1f1ad90c9235d15" ead37dfb]:
 {{{
 #!CommitTicketReference repository=""
 revision="ead37dfb580136cc27dbd487a1f1ad90c9235d15"
 Fixed #32202 -- Fixed autoreloader argument generation for Windows with
 Python 3.7-.
 }}}

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

Re: [Django] #25534: Allow using lookups in aggregates.

[Django]

#25534: Allow using lookups in aggregates.
-+-
 Reporter:  Raúl Pedro Santos|Owner:  Ian Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Mariusz Felisiak):

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

Re: [Django] #31639: Allow using lookup and transforms in F() and OuterRef().

[Django]

#31639: Allow using lookup and transforms in F() and OuterRef().
-+-
 Reporter:  Baptiste Mispelon|Owner:  Ian Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Mariusz Felisiak):

 * owner:  Srinivas Reddy Thatiparthy => Ian Foote


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

Re: [Django] #31639: Allow using lookup and transforms in F() and OuterRef().

[Django]

#31639: Allow using lookup and transforms in F() and OuterRef().
-+-
 Reporter:  Baptiste Mispelon|Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Mariusz Felisiak):

 * needs_docs:  0 => 1
 * has_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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5486578112b1cc0250d19dbb981c75a0%40djangoproject.com.

Re: [Django] #31639: Allow using lookup and transforms in F() and OuterRef(). (was: F() and OuterRef() objects do not error when referencing transforms.)

[Django]

#31639: Allow using lookup and transforms in F() and OuterRef().
-+-
 Reporter:  Baptiste Mispelon|Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  1 => 0
 * type:  Bug => 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/067.b19a6705bc8c06cc5f6145566f29180c%40djangoproject.com.

Re: [Django] #32206: Incorrect migration generated if field has been renamed when it has verbose_name set

[Django]

#32206: Incorrect migration generated if field has been renamed when it has
verbose_name set
-+-
 Reporter:  Peter Inglesby   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  3.1
 Severity:  Normal   |   Resolution:  duplicate
 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:  assigned => closed
 * resolution:   => duplicate


Comment:

 OK, given Simon ans Mariusz' comments lets take this as a duplicate of
 #31700 and aim to provide a better warning for this kind of case.

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

Re: [Django] #31700: Highlight destructive operations in makemigrations output

[Django]

#31700: Highlight destructive operations in makemigrations output
-+
 Reporter:  Tom Forbes   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  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 Carlton Gibson):

 * status:  closed => new
 * resolution:  needsinfo =>
 * stage:  Unreviewed => Accepted


Comment:

 A similar example of a dangerous migration with a rename involving
 `verbose_name` has come up in #32206. That looks like a case where a
 warning would come in handy.

 [https://groups.google.com/g/django-
 developers/c/A0m8YkPKpZo/m/elJVb9JCAgAJ Tobias McNulty had a suggestion on
 the mailing list thread]:

 > I'm +1 to doing *something.* Absent a louder reminder, I think it's
 unrealistic to expect everyone to read the output of makemigrations all
 the time.
 >
 > As others have said, I'm not sure `manage.py migrate` is the right time.
 I think it's too late. The code may have already been committed, who knows
 what machine the migrations are being run on, etc.
 >
 > During makemigrations, on the other hand, I don't see anything wrong
 with formatted text or +/-, but I might go a step further. We already
 prompt for things like renames and merges. Why not forcibly gain user
 acceptance before creating a migration that deletes something? ...

 Let's take this as an opportunity to give users better warnings to check
 twice 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/061.690363eb3ce1735a92efb0ab54ef6bfd%40djangoproject.com.

Re: [Django] #32206: Incorrect migration generated if field has been renamed when it has verbose_name set

[Django]

#32206: Incorrect migration generated if field has been renamed when it has
verbose_name set
-+-
 Reporter:  Peter Inglesby   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.1
 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
-+-

Comment (by Carlton Gibson):

 Hi All — thanks for the input.

 Can I ask, can we **warn** in these kind of cases somehow?

 So, a user **should** do it in two steps, and users **should** review
 generated migrations to make sure the operations are what's required, but
 I think this probably counts as a loaded foot-gun.

 Perhaps we should re-open #31700 which suggested adding additional output
 for destructive operations? (Mailing list summary there was "Yes, maybe
 something at the `makemigrations` stage...) — What do we think? (Thanks!)

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

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

Re: [Django] #31885: Update SMTP Email Backend to use an SSLContext.

[Django]

#31885: Update SMTP Email Backend to use an SSLContext.
---+-
 Reporter:  Luis Saavedra  |Owner:  Luis Saavedra
 Type:  Bug|   Status:  assigned
Component:  Core (Mail)|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  SSL| 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):

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


Comment:

 Updating flags to put back in the review queue

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

Re: [Django] #26583: Add an option to silence collectstatic clashing files warnings

[Django]

#26583: Add an option to silence collectstatic clashing files warnings
-+-
 Reporter:  Justin McCammon  |Owner:  Ryan
 Type:   |  Hunter
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  2.1
 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 Mariusz Felisiak):

 * 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/068.aee00ae1793465517de7ce8299a72418%40djangoproject.com.