[Django] #30275: Autofocus the first field in contrib.admin add form

[Django]

#30275: Autofocus the first field in contrib.admin add form
-+-
   Reporter:  Remoddy|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  2.1
  contrib.admin  |
   Severity:  Normal |   Keywords:  focus, autofocus
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The contrib.admin pages to add new instance of a model used to be
 autofocused in 1.9 (so just after visiting /model/add admin URL you could
 type in value for the first model field from keyboard). That changed in
 1.10 (you need to click the first widget with mouse or press [Tab] a few
 times). I guess, [d638cdc42acec608c1] was the relevant commit. Still no
 autofocus in 2.1.

 I believe, the old behavior (first item focused) is by design, see #15987,
 so it is a regression.

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

Re: [Django] #30274: Segfault on iteration of GEOS Polygons/LinearRings

[Django]

#30274: Segfault on iteration of GEOS Polygons/LinearRings
-+-
 Reporter:  Murray   |Owner:  nobody
  Christopherson |
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  geos gis | 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):

 Hello Murray, in order to identify the origin of segfault I suggest you
 enable [https://docs.python.org/3/library/faulthandler.html faulthandler]
 and rely on `catchsegv`.

 That would be `catchsegv python -X faulthandler script.py`.

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

Re: [Django] #30273: ModelAdmin for proxy model with InlineModelAdmin for superclass reference results in admin.E202

[Django]

#30273: ModelAdmin for proxy model with InlineModelAdmin for superclass 
reference
results in admin.E202
-+-
 Reporter:  jwindhager   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  proxy,   | Triage Stage:  Accepted
  InlineModelAdmin, E202 |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #30274: Segfault on iteration of GEOS Polygons/LinearRings

[Django]

#30274: Segfault on iteration of GEOS Polygons/LinearRings
-+-
 Reporter:  Murray   |Owner:  nobody
  Christopherson |
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  geos gis | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Generally a segmentation fault suggests an issue outside of Django's
 control as none of Django is written in C. If you identify that Django is
 at fault, please reopen and give the fix.

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

[Django] #30274: Segfault on iteration of GEOS Polygons/LinearRings

[Django]

#30274: Segfault on iteration of GEOS Polygons/LinearRings
-+-
   Reporter:  Murray |  Owner:  nobody
  Christopherson |
   Type:  Bug| Status:  new
  Component:  GIS|Version:  2.1
   Severity:  Normal |   Keywords:  geos gis
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 **Environment Details**
 Ubuntu 14.04 (trusty)
 Python 3.6.8 (via package manager, unofficial repo: ppa:deadsnakes/ppa)
 Django 2.1.7 (via pip)
 libgeos (both 3.4.2 via apt-get, and 3.7.1 via source distribution)

 First and foremost, I am aware that the OS is a bit older (hence the
 unofficial installation routes of some newer dependencies), but I was
 unable to find any reason these components shouldn't play nice.

 **Steps to reproduce**
 I have a minimal script showcasing the issue:

 {{{
 from django.contrib.gis.geos import Polygon

 def main():
 polygon = Polygon( ((0.0, 0.0), (0.0, 50.0), (50.0, 50.0), (50.0,
 0.0), (0.0, 0.0)) )

 for p in polygon[0]:
 print('Longitude:', p[0])
 print('Latitude:', p[1])

 if __name__ == '__main__':
 main()
 }}}

 **Expected Behaviour**
 Output to stdout, something like:

 {{{
 Latitude: 0.0
 Longitude: 0.0
 Latitude: 0.0
 Longitude: 50.0
 ...
 }}}

 **Observed Behaviour**
 Output to stderr:

 {{{
 Segmentation fault (core dumped)
 }}}

 **Notes**
 It should be noted, when originally observed, there was a stacktrace
 (which I won't post in full, as it's mostly uWSGI functions), but the
 relevant section suggested the segfault is in `GEOSCoordSeq_getSize` in
 `libgeos.so`, which leads me to believe the issue may be in
 
https://github.com/django/django/blob/master/django/contrib/gis/geos/prototypes/coordseq.py.

 Furthermore, this issue was uncovered during a Python 2 to 3 migration
 attempt. The issue did not manifest in this environment:
 Ubuntu 14.04 (trusty)
 Python 2.7.12 (via package manager, unofficial repo: ppa:deadsnakes/ppa)
 Django 1.11.18 (via pip)
 libgeos 3.4.2 (via apt-get)

 Lastly, I was able to find a workaround (in case anyone else encounters
 this). This un-Pythonic variation seems to work:

 {{{
 from django.contrib.gis.geos import Polygon

 def main():
 polygon = Polygon( ((0.0, 0.0), (0.0, 50.0), (50.0, 50.0), (50.0,
 0.0), (0.0, 0.0)) )

 for i in range(len(polygon[0])):
 p = polygon[0][i]
 print('Longitude:', p[0])
 print('Latitude:', p[1])

 if __name__ == '__main__':
 main()
 }}}

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

Re: [Django] #30240: Add support for SHA database functions.

[Django]

#30240: Add support for SHA database functions.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sha1, sha224,| Triage Stage:  Ready for
  sha256, sha384, sha512 |  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:"0b70985f42da7a8eb2e206e6780681b7849564ef" 0b70985]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b70985f42da7a8eb2e206e6780681b7849564ef"
 Fixed #30240 -- Added SHA1, SHA224, SHA256, SHA384, and SHA512 database
 functions.

 Thanks Mariusz Felisiak and Tim Graham for reviews.
 }}}

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

Re: [Django] #28738: Add support for PostGIS <-> operator

[Django]

#28738: Add support for PostGIS <-> operator
-+-
 Reporter:  Matthew Somerville   |Owner:  Francisco
 |  Couzo
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  1.11
 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 Tim Graham ):

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


Comment:

 In [changeset:"0193bf874f08f21cdec628b8d80d261471bfe5fc" 0193bf8]:
 {{{
 #!CommitTicketReference repository=""
 revision="0193bf874f08f21cdec628b8d80d261471bfe5fc"
 Fixed #28738 -- Added the GeometryDistance function.
 }}}

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

Re: [Django] #10227: Support a related_default on OneToOne fields

[Django]

#10227: Support a related_default on OneToOne fields
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  onetoone related | Triage Stage:  Accepted
  expection null |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
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 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.9eb085f80cf978ae06d1bf475f408c2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28738: Add support for PostGIS <-> operator

[Django]

#28738: Add support for PostGIS <-> operator
-+-
 Reporter:  Matthew Somerville   |Owner:  Francisco
 |  Couzo
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  1.11
 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 Tim Graham):

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


Comment:

 [https://github.com/django/django/pull/11091 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/064.d617100d0a1660be159050843295b782%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30250: Due to iOS Safari 12 issue, SameSite flag on session and CSRF cookies should NOT be Lax by default

[Django]

#30250: Due to iOS Safari 12 issue, SameSite flag on session and CSRF cookies
should NOT be Lax by default
-+-
 Reporter:  Flávio Juvenal   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  2.1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
  samesite,csrf,session,cookies  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Duplicate of #29975.

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

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

Re: [Django] #30266: Migrating a model's default primary key to a BigAutoField causes Postgres sequence to lose owner

[Django]

#30266: Migrating a model's default primary key to a BigAutoField causes 
Postgres
sequence to lose owner
-+-
 Reporter:  Dolan Antenucci  |Owner:  Dolan
 |  Antenucci
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  postgres migration   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * easy:  1 => 0


Old description:

> Note: I'm marking this as easy pickings, but feel free to change.
>
> == Summary of Issue ==
> Start with the following models (below assumes application name is
> "sandbox"):
>
> {{{#!python
> class Test1(models.Model):
> id = models.BigAutoField(primary_key=True)
> name = models.CharField(max_length=100)
>
> class Test2(models.Model):
> name = models.CharField(max_length=100)
> }}}
>
> After migrating, go the the `dbshell` and run `\d sandbox_test1_id_seq`
> and `\d sandbox_test2_id_seq`.  The results will include "Owned by:
> public.sandbox_test1.id" and "Owned by: public.sandbox_test2.id"
> respectively.
>
> Next, change Test2 to a `BigIntField`:
>
> {{{#!python
> class Test2(models.Model):
> id = models.BigAutoField(primary_key=True)
> name = models.CharField(max_length=100)
> }}}
>
> Make a new migration, migrate, and then go back to `dbshell` and run `\d
> sandbox_test2_id_seq`.  There will no longer be an owner listed for this
> sequence.
>
> == Result of this issue ==
> When using `loaddata` with fixtures on the `Test2` model, the sequence
> will not be incremented because the command Django uses to reset the
> sequence for the primary key fails.  Specifically, in the
> [https://github.com/django/django/blob/master/django/db/backends/postgresql/operations.py#L157
> postgres backend], Django calls the postgres function
> `pg_get_serial_sequence(, )`, which returns nothing when
> the sequence is missing an owner.
>
> This can be verified in postgres shell via `select
> pg_get_serial_sequence('sandbox_test1', 'id');` and `select
> pg_get_serial_sequence('sandbox_test2', 'id');`
>
> The result is that after the fixture is loaded, any other inserts will
> fail because their primary keys will conflict with those in the fixture.
>
> == Potential fixes ==
> 1. It seems like `makemigrations` should be setting the sequence owner,
> or using a different command to migrate so that the sequence owner
> information is not lost.  For example, the
> [https://www.postgresql.org/docs/10/datatype-numeric.html#DATATYPE-SERIAL
> postgres docs on serial columns] show that this can be done with `ALTER
> SEQUENCE tablename_colname_seq OWNED BY tablename.colname;`
> 2. For tables already migrated and missing the owner information, perhaps
> the `makemigrations` command needs to confirm that the owner information
> is set correctly.
> 3. Not a fan of this solution myself, but one could also change the
> sequence is reset the
> [https://github.com/django/django/blob/master/django/db/backends/postgresql/operations.py#L157
> postgres backend] (i.e., not use `pg_get_serial_sequence`)
>
> Long-term, maybe `makemigrations` should be using postgres's SERIAL and
> BIGSERIAL field types, which automatically create the sequence and set
> the sequence owner.

New description:

 == Summary of Issue ==
 Start with the following models (below assumes application name is
 "sandbox"):

 {{{#!python
 class Test1(models.Model):
 id = models.BigAutoField(primary_key=True)
 name = models.CharField(max_length=100)

 class Test2(models.Model):
 name = models.CharField(max_length=100)
 }}}

 After migrating, go the the `dbshell` and run `\d sandbox_test1_id_seq`
 and `\d sandbox_test2_id_seq`.  The results will include "Owned by:
 public.sandbox_test1.id" and "Owned by: public.sandbox_test2.id"
 respectively.

 Next, change Test2 to a `BigIntField`:

 {{{#!python
 class Test2(models.Model):
 id = models.BigAutoField(primary_key=True)
 name = models.CharField(max_length=100)
 }}}

 Make a new migration, migrate, and then go back to `dbshell` and run `\d
 sandbox_test2_id_seq`.  There will no longer be an owner listed for this
 sequence.

 == Result of this issue ==
 When using `loaddata` with fixtures on the `Test2` model, the sequence
 will not be incremented because the command Django uses to reset the
 sequence for the primary key fails.  Specifically, in the
 
[https://github.com/django/django/blob/master/django/db/backends/postgresql/operations.py#L157
 postgres backend], Django calls 

[Django] #30273: ModelAdmin for proxy model with InlineModelAdmin for superclass reference results in admin.E202

[Django]

#30273: ModelAdmin for proxy model with InlineModelAdmin for superclass 
reference
results in admin.E202
-+-
   Reporter: |  Owner:  nobody
  jwindhager |
   Type:  Bug| Status:  new
  Component: |Version:  2.1
  contrib.admin  |   Keywords:  proxy,
   Severity:  Normal |  InlineModelAdmin, E202
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Assume the following Django models:

 {{{#!python

 class Reporter(models.Model):
 ...


 class Journalist(Reporter):
 ...

 class Meta:
 proxy = True


 class Article(models.Model):
 reporter = models.ForeignKey(Reporter)
 ...

 }}}

 Register model admins as follows (exemplary):
 {{{#!python

 class ArticleInline(admin.TabularInline):
 model = Article
 fk_name = 'reporter'
 ...


 @admin.register(Journalist)
 class JournalistAdmin(admin.ModelAdmin):
 inlines = [ArticleInline]
 ...

 }}}

 This will result in the following error:
 {{{
 : (admin.E202) fk_name 'reporter' is not a
 ForeignKey to 'Journalist'.
 }}}

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

Re: [Django] #28780: Allow customizing PasswordResetConfirmView's INTERNAL_RESET_URL_TOKEN

[Django]

#28780: Allow customizing PasswordResetConfirmView's INTERNAL_RESET_URL_TOKEN
--+
 Reporter:  Meiyer|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by Tim Graham):

 * status:  assigned => new
 * owner:  Tim G. => (none)


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

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

Re: [Django] #30257: UsernameValidator allows trailing newline in usernames

[Django]

#30257: UsernameValidator allows trailing newline in usernames
---+---
 Reporter:  Robert Grosse  |Owner:  Ryan Schave
 Type:  Bug|   Status:  assigned
Component:  contrib.auth   |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+---
Changes (by Simon Charette):

 * needs_better_patch:  0 => 1


Comment:

 Tim reported that the tests are not covering the leading newline case on
 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 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.9edfe993b885125783ff5011ed58d50c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30266: Migrating a model's default primary key to a BigAutoField causes Postgres sequence to lose owner

[Django]

#30266: Migrating a model's default primary key to a BigAutoField causes 
Postgres
sequence to lose owner
-+-
 Reporter:  Dolan Antenucci  |Owner:  Dolan
 |  Antenucci
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  postgres migration   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * component:  Database layer (models, ORM) => Migrations
 * stage:  Unreviewed => Accepted


Comment:

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

 Please uncheck "Patch needs improvement" if you're able to rewrite the
 test as suggested on 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 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.81e7515f7c1c848bb2dad352b26a158c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30264: "OverflowError: timestamp out of range for platform time_t" test failure on 32-bit platforms

[Django]

#30264: "OverflowError: timestamp out of range for platform time_t" test 
failure on
32-bit platforms
-+-
 Reporter:  Chris Lamb   |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  2.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  overflow | 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:"505785a71ddcc66f0dbf2b9b903881e894a17a17" 505785a]:
 {{{
 #!CommitTicketReference repository=""
 revision="505785a71ddcc66f0dbf2b9b903881e894a17a17"
 [2.2.x] Fixed #30264 -- Fixed crash of test_parsing_year_less_than_70() on
 32-bit systems.

 Thanks Andreas Beckmann and Chris Lamb for the report.
 Backport of c9888bc8ecb8943ef08090e3325dcbdac825eafc 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/063.9f1a896d20b47b02c39b6d866abfb1fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30264: "OverflowError: timestamp out of range for platform time_t" test failure on 32-bit platforms

[Django]

#30264: "OverflowError: timestamp out of range for platform time_t" test 
failure on
32-bit platforms
-+-
 Reporter:  Chris Lamb   |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  2.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  overflow | 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:"c9888bc8ecb8943ef08090e3325dcbdac825eafc" c9888bc8]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9888bc8ecb8943ef08090e3325dcbdac825eafc"
 Fixed #30264 -- Fixed crash of test_parsing_year_less_than_70() on 32-bit
 systems.

 Thanks Andreas Beckmann and Chris Lamb for the report.
 }}}

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

[Django] #30272: get_language_from_path not respecting i18n_patterns prefix_default_language=False

[Django]

#30272: get_language_from_path not respecting i18n_patterns
prefix_default_language=False
+
   Reporter:  Stefan Wehrmeyer  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  2.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 |
+
 Starting in Django 1.10 `django.conf.urls.i18n.i18n_patterns` accepts an
 option `prefix_default_language` that can be set to `False`. This adds no
 language prefix for the the default language when reversing URLs.

 `django.utils.translation.get_language_from_path` is supposed to detect
 the language from the URL path. At the moment it returns `None` when no
 language URL prefix is found. I would argue that if the path is resolved
 by `i18n_patterns` with `prefix_default_language=False`
 `get_language_from_path` should return the default language
 (`settings.LANGUAGE_CODE`)

 I believe the intention of using `i18n_patterns` and setting
 `prefix_default_language=False` is two-fold:
 - construct URLs in the default language without a language prefix (this
 works now)
 - detect non-prefixed URLs as using the default language (currently *not*
 working, falls back to session, cookie, HTTP headers)

 Let me know if you consider this a bug.

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

Re: [Django] #15727: Add support for Content-Security-Policy (CSP) to core

[Django]

#15727: Add support for Content-Security-Policy (CSP) to core
---+--
 Reporter:  db.pub.mail@…  |Owner:  Tom Forbes
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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
---+--

Comment (by Sebastien Dubois):

 Any news about this feature request?

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

Re: [Django] #30129: Allow creating models with fields values as a Subquery() with F() expressions

[Django]

#30129: Allow creating models with fields values as a Subquery() with F()
expressions
-+-
 Reporter:  Charlie McBride  |Owner:
 |  birthdaysgift
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Subquery, F, Query   | Triage Stage:  Accepted
  Expressions|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by birthdaysgift):

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


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

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

[Django]

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
 Reporter:  Tetsuya Morimoto |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-db | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlos Palol):

 * cc: Carlos Palol (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 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/061.e7d9c87b730897031396ef86fea09e23%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7623: Multi-table inheritance: Add the ability create child instance from existing parent

[Django]

#7623: Multi-table inheritance: Add the ability create child instance from
existing parent
-+-
 Reporter:  brooks.travis@…  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  model-inheritance,   | Triage Stage:  Accepted
  multi-table-inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlos Palol):

 * cc: Carlos Palol (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 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/081.d319290028529805f43bc236a633d861%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30271: Add support for the Sign database function.

[Django]

#30271: Add support for the Sign database function.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sign, database,  | Triage Stage:  Accepted
  function   |
Has patch:  1|  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 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.a8eda1f965b8724f87a42216e8f15d10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30271: Add support for the Sign database function.

[Django]

#30271: Add support for the Sign database function.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sign, database,  | Triage Stage:
  function   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11100 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.55a1a9272abbc0b8fe971d92afd5cb64%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30271: Add support for the Sign database function.

[Django]

#30271: Add support for the Sign database function.
-+-
   Reporter:  Nick Pope  |  Owner:  Nick Pope
   Type:  New| Status:  assigned
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:  sign, database,
   Severity:  Normal |  function
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Add support for the {{{Sign()}}} database function.

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

Re: [Django] #30265: Fixed reference to a tutorial number in "Advanced tutorial: How to write reusable app". (was: Django Documentation - Advanced tutorial: How to write reusable app)

[Django]

#30265: Fixed reference to a tutorial number in "Advanced tutorial: How to write
reusable app".
-+-
 Reporter:  Abhishek Bera|Owner:  Abhishek
 Type:   |  Bera
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by felixxm):

 Agreed, it should point to the 1st tutorial.

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

Re: [Django] #30265: Fix reference to a tutorial number in "Advanced tutorial: How to write reusable app". (was: Fixed reference to a tutorial number in "Advanced tutorial: How to write reusable app".

[Django]

#30265: Fix reference to a tutorial number in "Advanced tutorial: How to write
reusable app".
-+-
 Reporter:  Abhishek Bera|Owner:  Abhishek
 Type:   |  Bera
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  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/069.00a0ad3a83d1fba605a05e3a0bd731b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30265: Django Documentation - Advanced tutorial: How to write reusable app

[Django]

#30265: Django Documentation - Advanced tutorial: How to write reusable app
-+-
 Reporter:  Abhishek Bera|Owner:  Abhishek
 Type:   |  Bera
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Abhishek Bera):

 * owner:  nobody => Abhishek Bera
 * status:  new => assigned


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

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

Re: [Django] #30265: Django Documentation - Advanced tutorial: How to write reusable app

[Django]

#30265: Django Documentation - Advanced tutorial: How to write reusable app
--+
 Reporter:  Abhishek Bera |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by felixxm):

 * version:  2.1 => master
 * type:  Uncategorized => Cleanup/optimization
 * 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 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.7e0843a64891b47b135aee6df9ea4c89%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.