Re: [Django] #30511: AutoField with postgres10/11 as generated identity. (was: AutoField with postgres10/11 as generated identity)

[Django]

#30511: AutoField with postgres10/11 as generated identity.
-+-
 Reporter:  Michael Kany |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres generated   | Triage Stage:
  identity   |  Unreviewed
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


Old description:

> We are currently working on a Django / Postgresql 11 project. We needed
> an adjustment for the postgres module because of its compatibility with
> .NET Framework and dataset generation.
> In postgres 10/11 there is the new feature identity column called
> GENERATED AS IDENTITY instead of serial.
> column_name type GENERATED {ALWAYS | BY DEFAULT} AS IDENTITY
> [(sequence_option)]
> We have created a module based on db.backends.postgres that adds 2 new
> django model fields. I would like implement the new feature into pyodbc
> module or new module for postgres 10/11 useful for later versions of
> django.
>
> Adjustments only in base.py (line 70ff):
> data_types = {
> 'IdentityAutoField': 'integer',
> 'IdentityBigAutoField': 'bigint',
>
> and schema.py, def column_sql () (line 178ff):
> # Primary key / unique outputs
> if field.primary_key:
> sql + = "PRIMARY KEY"
> if field.get_internal_type () in ("IdentityAutoField",
> "IdentityBigAutoField"):
> sql + = "GENERATED ALWAYS AS IDENTITY"
> elif field.unique:
> sql + = "UNIQUE"
>
> I can also send our code
>
> best regards
> Michael Kany

New description:

 We are currently working on a Django / Postgresql 11 project. We needed an
 adjustment for the postgres module because of its compatibility with .NET
 Framework and dataset generation.
 In postgres 10/11 there is the new feature identity column called
 GENERATED AS IDENTITY instead of serial.
 column_name type GENERATED {ALWAYS | BY DEFAULT} AS IDENTITY
 [(sequence_option)]
 We have created a module based on db.backends.postgres that adds 2 new
 django model fields. I would like implement the new feature into pyodbc
 module or new module for postgres 10/11 useful for later versions of
 django.

 Adjustments only in base.py (line 70ff):
 {{{
 data_types = {
 'IdentityAutoField': 'integer',
 'IdentityBigAutoField': 'bigint',
 }}}
 and schema.py, def column_sql () (line 178ff):
 {{{
 # Primary key / unique outputs
 if field.primary_key:
 sql + = "PRIMARY KEY"
 if field.get_internal_type () in ("IdentityAutoField",
 "IdentityBigAutoField"):
 sql + = "GENERATED ALWAYS AS IDENTITY"
 elif field.unique:
 sql + = "UNIQUE"
 }}}
 I can also send our code

 best regards
 Michael Kany

--

Comment:

 Thanks for the report. Can you provide more details about your use case?
 Can you also clarify what are you proposing? e.g.
 - using `GENERATED AS IDENTITY` instead of `serial` on PostgreSQL (I don't
 see much value in this),
 - adding extra fields to the PostgreSQL backends.

 In Oracle we used `GENERATED AS IDENTITY` because there is no other way to
 create `serial`-like columns on Oracle which is not the case on
 PostgreSQL.

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

Re: [Django] #30475: Use of i18n_patterns and a buggy 404 template trigger internal server error without a backtrace. (was: Use of i18n_patterns and a buggy 404 template trigger internal server error

[Django]

#30475: Use of i18n_patterns and a buggy 404 template trigger internal server 
error
without a backtrace.
-+--
 Reporter:  Erik Stein   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by felixxm):

 * status:  new => closed
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 Thanks for the sample project. IMO everything works properly. In `DEBUG`
 mode Django doesn't use your custom `404.html` page that's why it also
 doesn't propagate any errors in this page (you've already described this
 as a correct behavior). When `DEBUG=False` Django handles exception by
 [https://docs.djangoproject.com/en/stable/ref/urls/#handler500 handler500]
 view and logges them in
 [https://docs.djangoproject.com/en/stable/topics/logging/#django-request-
 logger django.request] logger. If you want to skip this and propagate
 exceptions upwards when `DEBUG=False` you can use
 [https://docs.djangoproject.com/en/2.2/ref/settings/#debug-propagate-
 exceptions DEBUG_PROPAGATE_EXCEPTIONS] setting.

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

Re: [Django] #30352: Error al ejecutar python manage.py sin sealizar cambios

[Django]

#30352: Error al ejecutar python manage.py sin sealizar cambios
-+-
 Reporter:  irv-ro-j |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (System |  Version:  2.2
  checks)|
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  Reload Django| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

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


Comment:

 Please [https://docs.djangoproject.com/en/stable/internals/contributing
 /triaging-tickets/#closing-tickets follow triaging guidelines with regards
 to needsinfo tickets.] To reopen this ticket you should provide a test
 project.

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

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

[Django]

#30512: Update mail backend to use modern standard library parsing approach.
-+-
 Reporter:  Joachim Jablon   |Owner:  Joachim
 Type:   |  Jablon
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
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/067.e9b4304231a6e66d1d16668135a0a1db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30510: bulk_create() crashes with mixed length arguments on LOB fields on Oracle. (was: Bulk creates with Oracle backend fail with mixed length arguments on LOB field)

[Django]

#30510: bulk_create() crashes with mixed length arguments on LOB fields on 
Oracle.
-+-
 Reporter:  Mark Gordon  |Owner:  Mark
 |  Gordon
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle bulk_create   | 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):

 * version:  2.1 => master
 * keywords:   => oracle bulk_create
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. Reproduced at
 1d25354fb5f87d35968cd78b53d9560fd75f5b1a.


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

Re: [Django] #30508: Add Password Reset Via Email to documentation. (was: Password Reset Via Email)

[Django]

#30508: Add Password Reset Via Email to documentation.
-+-
 Reporter:  MrAli|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Documentation
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 Thanks for the report, however it is already described in (or referenced
 by) multiple places in docs e.g.
  - [https://docs.djangoproject.com/en/2.2/ref/contrib/admin/#adding-a
 -password-reset-feature adding-a-password-reset-feature],
  - [https://docs.djangoproject.com/en/2.2/topics/auth/default/#module-
 django.contrib.auth.views django.contrib.auth.views],
  -
 
[https://docs.djangoproject.com/en/2.2/topics/auth/default/#django.contrib.auth.views.PasswordResetView
 django.contrib.auth.views.PasswordResetView].

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

Re: [Django] #28822: Add DBCalculatedField to model to annotate models automatically

[Django]

#28822: Add DBCalculatedField to model to annotate models automatically
-+-
 Reporter:  Ilya |Owner:  nobody
 Type:  New feature  |   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 Roberto Maurizzi):

 * cc: Roberto Maurizzi (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/071.2c93e2b1a317ea1404ab54683e9b63f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30507: Update admin's jQuery to 3.4.X.

[Django]

#30507: Update admin's jQuery to 3.4.X.
-+-
 Reporter:  felixxm  |Owner:
 Type:   |  dulmandakh
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dulmandakh):

 * status:  new => assigned
 * owner:  nobody => dulmandakh
 * has_patch:  0 => 1


Comment:

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

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

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

[Django]

#30512: Update mail backend to use modern standard library parsing approach
-+-
 Reporter:  Joachim Jablon   |Owner:  Joachim
 Type:   |  Jablon
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Joachim Jablon):

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

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

[Django]

#30512: Update mail backend to use modern standard library parsing approach
-+-
   Reporter:  Joachim|  Owner:  Joachim Jablon
  Jablon |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Core   |Version:  master
  (Mail) |
   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  |
-+-
 {{{ django.core.mail.message.sanitize_address }}} uses {{{
 email.utils.parseaddr }}} from the standard lib. On Python 3, {{{
 email.headerregistry.parser.get_mailbox() }}} does the same, and is less
 error-prone.

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

Re: [Django] #30511: AutoField with postgres10/11 as generated identity

[Django]

#30511: AutoField with postgres10/11 as generated identity
-+-
 Reporter:  Michael Kany |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres generated   | Triage Stage:
  identity   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Michael Kany):

 * cc: Michael Kany (added)


Comment:

 the new Fields 'IdentityAutoField': 'integer',  'IdentityBigAutoField':
 'bigint', the new fields could also be implemented as AutoFiled or
 BigAutoField, similar to the oracle module

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

Re: [Django] #30511: AutoField with postgres10/11 as generated identity

[Django]

#30511: AutoField with postgres10/11 as generated identity
-+-
 Reporter:  Michael Kany |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres generated   | Triage Stage:
  identity   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Michael Kany):

 * Attachment "schema.py" 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/068.b3a4221f3e92413d4c5648c1635fde19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30511: AutoField with postgres10/11 as generated identity

[Django]

#30511: AutoField with postgres10/11 as generated identity
-+-
 Reporter:  Michael Kany |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres generated   | Triage Stage:
  identity   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Michael Kany):

 * Attachment "base.py" 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/068.8b3a6d952ac741a1c11d2278eaa167d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30511: AutoField with postgres10/11 as generated identity

[Django]

#30511: AutoField with postgres10/11 as generated identity
-+-
   Reporter:  Michael|  Owner:  nobody
  Kany   |
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  2.2
  layer (models, ORM)|   Keywords:  postgres generated
   Severity:  Normal |  identity
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 We are currently working on a Django / Postgresql 11 project. We needed an
 adjustment for the postgres module because of its compatibility with .NET
 Framework and dataset generation.
 In postgres 10/11 there is the new feature identity column called
 GENERATED AS IDENTITY instead of serial.
 column_name type GENERATED {ALWAYS | BY DEFAULT} AS IDENTITY
 [(sequence_option)]
 We have created a module based on db.backends.postgres that adds 2 new
 django model fields. I would like implement the new feature into pyodbc
 module or new module for postgres 10/11 useful for later versions of
 django.

 Adjustments only in base.py (line 70ff):
 data_types = {
 'IdentityAutoField': 'integer',
 'IdentityBigAutoField': 'bigint',

 and schema.py, def column_sql () (line 178ff):
 # Primary key / unique outputs
 if field.primary_key:
 sql + = "PRIMARY KEY"
 if field.get_internal_type () in ("IdentityAutoField",
 "IdentityBigAutoField"):
 sql + = "GENERATED ALWAYS AS IDENTITY"
 elif field.unique:
 sql + = "UNIQUE"

 I can also send our code

 best regards
 Michael Kany

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

Re: [Django] #25946: Negated clauses' "isnull" added term does not take field transforms into account

[Django]

#25946: Negated clauses' "isnull" added term does not take field transforms into
account
-+-
 Reporter:  ris  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  transform negated| Triage Stage:  Accepted
  null   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by robinh00d):

 * owner:  robinh00d => (none)
 * status:  assigned => new


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

Re: [Django] #30475: Use of i18n_patterns and a buggy 404 template trigger internal server error without a backtrace

[Django]

#30475: Use of i18n_patterns and a buggy 404 template trigger internal server 
error
without a backtrace
-+--
 Reporter:  Erik Stein   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Erik Stein):

 * status:  closed => new
 * cc: Erik Stein (added)
 * resolution:  needsinfo =>


Old description:

> – Using i18n_patterns with prefix_default_language=True,
> – trying to get the frontpage URL without a language given in the URL
>
> works in debug mode, but gives an internal server error without any
> backtrace in production mode.
>
> This was caused by a buggy 404.html template, but probably buggy 404
> templates should give a backtrace, too, and i18n_patterns shouldn't be
> concerned by this anyway.
>
> [draft bug report, I'll try to provide more details later or on request]

New description:

 – Using i18n_patterns with prefix_default_language=True,
 – trying to get the frontpage URL without a language given in the URL

 works in debug mode, but gives an internal server error without any
 backtrace in production mode.

 This was caused by a buggy 404.html template, but probably buggy 404
 templates should give a backtrace, too, and i18n_patterns shouldn't be
 concerned by this anyway.

 Sample project: https://github.com/sha-red/bugs-django-30475

--

Comment:

 I asked about adding a ticket for later reference before posting the issue
 and I would consider closing it after two days a bit unfortunate, but I
 don't really know your triaging policy, so please forgive me :-).

 Today I've added a simple sample project. In a first check it seems that
 the Django test client actually deals correctly with the buggy 404
 template (delivering a backtrace) making it somehow unuseful in testing
 the issue. I added some notes in the README instead.

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