Re: [Django] #13091: admin list_editable with unique_together raises Integrity Error

[Django]

#13091: admin list_editable with unique_together raises Integrity Error
-+-
 Reporter:  Sławek Ehlert|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  list_editable| Triage Stage:  Accepted
  unique_together IntegrityError |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
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/063.67a6398b752e43a3ae6209e3ea7652f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16508: Provide real support for virtual fields

[Django]

#16508: Provide real support for virtual fields
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Asif
 |  Saifuddin Auvi
 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 Asif Saifuddin Auvi):

 * owner:  (none) => Asif Saifuddin Auvi
 * 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/063.2d9c51ac904bf65dda618519eac41c1d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
-+-
 Reporter:  Jacob|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Asif Saifuddin Auvi):

 * owner:  Michal Petrucha => (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/063.5035297acfa1e5e3377b8a959c7ee0c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30242: Double spaces before limit/offset clause in as_sql() of SQLCompiler

[Django]

#30242: Double spaces before limit/offset clause in as_sql() of SQLCompiler
-+-
 Reporter:  hangpark |Owner:  hangpark
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sql  | Triage Stage:
  databaseoperations sqlcompiler |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by hangpark):

 * has_patch:  0 => 1


Comment:

 PR open at https://github.com/django/django/pull/11061

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

Re: [Django] #30242: Double spaces before limit/offset clause in as_sql() of SQLCompiler

[Django]

#30242: Double spaces before limit/offset clause in as_sql() of SQLCompiler
-+-
 Reporter:  hangpark |Owner:  hangpark
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sql  | Triage Stage:
  databaseoperations sqlcompiler |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by hangpark):

 * owner:  nobody => hangpark
 * 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/066.db20bd264deacc0cd569081a5c1bd049%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30242: Double spaces before limit/offset clause in as_sql() of SQLCompiler

[Django]

#30242: Double spaces before limit/offset clause in as_sql() of SQLCompiler
-+-
   Reporter:  hangpark   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:  sql
   Severity:  Normal |  databaseoperations sqlcompiler
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 `SQLCompiler` has `as_sql()` method to create the SQL for a given query.
 Specifically, end-users can get the SQL string of their `QuerySet` by this
 method like:

 {{{
 User.objects.values('id').query.__str__()
 }}}

 where `User` is a basic user model.

 Absolutely, this returns a SQL string `SELECT "auth_user"."id" FROM
 "auth_user"`, and note that every separator between tokens is all single
 space.

 However, any query which has limit/offset clause produces double spaces
 before limit/offset clause. For example:

 {{{
 User.objects.values('id')[1:2].query.__str__()
 }}}

 returns
 {{{
 SELECT "auth_user"."id" FROM "auth_user"  LIMIT 1 OFFSET 1
 }}}
 not
 {{{
 SELECT "auth_user"."id" FROM "auth_user" LIMIT 1 OFFSET 1
 }}}

 These queries are executed as well as expected but seem not a good
 practice for formatting SQL as a string.

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

Re: [Django] #30236: UsernameField should use autocapitalize="none"

[Django]

#30236: UsernameField should use autocapitalize="none"
-+-
 Reporter:  Clayton Daley|Owner:
 Type:   |  pmisteliac
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Clayton Daley):

 They all apply to inputs but are different e.g. see
 https://uxcellence.com/2014/tweaking-automatic-form-input

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

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

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |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 Rich Rauenzahn):

 * cc: Rich Rauenzahn (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/073.993a24b09cf3ff9874cd67fb59014103%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30186: Show applied datetime in showmigrations

[Django]

#30186: Show applied datetime in showmigrations
-+-
 Reporter:  Timothy Schilling|Owner:  Timothy
 |  Schilling
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Ready for
  showmigrations |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"371ddade1e4e28827fd45e041c9410f8b4f01067" 371ddade]:
 {{{
 #!CommitTicketReference repository=""
 revision="371ddade1e4e28827fd45e041c9410f8b4f01067"
 Refs #30186 -- Changed MigrationRecorder.applied_migrations() to return a
 dict.
 }}}

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

Re: [Django] #30241: Add system checks to ensure correct configuration of translation settings.

[Django]

#30241: Add system checks to ensure correct configuration of translation 
settings.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  translations,| Triage Stage:  Accepted
  system checks, language tags   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
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/065.1689c58fa88289963004a6aa61026bd6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30236: UsernameField should use autocapitalize="none"

[Django]

#30236: UsernameField should use autocapitalize="none"
-+-
 Reporter:  Clayton Daley|Owner:
 Type:   |  pmisteliac
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nick Pope):

 Out of curiosity, is the problem solved by using
 {{{autocomplete="username"}}}? There is already #29379 open for that.

 Also see a past
 [https://github.com/django/django/pull/9245#issuecomment-356712601
 comment] regarding setting these attributes on the widgets from the form.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.c7f9bb95ea7a15bc6a748d9922988c66%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:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sha1, sha224,| Triage Stage:  Accepted
  sha256, sha384, sha512 |
Has patch:  1|  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/065.3ca73a4712e14c63a1cb18a48004c3f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29713: Add a django check to ensure the LANGUAGE_CODE setting uses the standard language ID format

[Django]

#29713: Add a django check to ensure the LANGUAGE_CODE setting uses the standard
language ID format
-+-
 Reporter:  Ian Foote|Owner:  David
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nick Pope):

 See #30241 for a follow up to add additional checks for language-related
 settings.

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

Re: [Django] #30189: sqlmigrate wraps it's outpout in BEGIN/COMMIT even if the database doesn't support transactional DDL

[Django]

#30189: sqlmigrate wraps it's outpout in BEGIN/COMMIT even if the database 
doesn't
support transactional DDL
+---
 Reporter:  Simon Charette  |Owner:  Parth Patil
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+---
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"acc041984fac1e79d9a1258c94479dd3ffc7f186" acc04198]:
 {{{
 #!CommitTicketReference repository=""
 revision="acc041984fac1e79d9a1258c94479dd3ffc7f186"
 Fixed #30189 -- Removed transaction from sqlmigrate output if database
 doesn't use one.
 }}}

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

Re: [Django] #30241: Add system checks to ensure correct configuration of translation settings.

[Django]

#30241: Add system checks to ensure correct configuration of translation 
settings.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  translations,| Triage Stage:
  system checks, language tags   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Old description:

> Following on from #29713 which added `translation.E001` to check
> `LANGUAGE_CODE`, I proposed the following:;
>
> - `translation.E002`: `'You have provided an invalid language code in the
> LANGUAGES setting: {}.'`
> - `translation.E003`: `'You have provided an invalid language code in the
> LANGUAGES_BIDI setting: {}.'`
> - `translation.E004`: `'You have provided a value for the LANGUAGE_CODE
> setting that is not in the LANGUAGES setting.'`
> - `translation.W005`: `'You have provided values in the LANGUAGE_BIDI
> setting that are not in the LANGUAGES setting.'`
>
> Note `W005` instead of `E005` - this case can simply be a warning because
> it will not cause things to go wrong, but highlights a potential
> configuration issue.

New description:

 Following on from #29713 which added `translation.E001` to check
 `LANGUAGE_CODE`, I proposed the following:;

 - `translation.E002`: `'You have provided an invalid language code in the
 LANGUAGES setting: {}.'`
 - `translation.E003`: `'You have provided an invalid language code in the
 LANGUAGES_BIDI setting: {}.'`
 - `translation.E004`: `'You have provided a value for the LANGUAGE_CODE
 setting that is not in the LANGUAGES setting.'`
 - `translation.W005`: `'You have provided values in the LANGUAGES_BIDI
 setting that are not in the LANGUAGES setting.'`

 Note `W005` instead of `E005` - this case can simply be a warning because
 it will not cause things to go wrong, but highlights a potential
 configuration issue.

--

Comment:

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

[Django] #30241: Add system checks to ensure correct configuration of translation settings.

[Django]

#30241: Add system checks to ensure correct configuration of translation 
settings.
-+-
   Reporter:  Nick Pope  |  Owner:  Nick Pope
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Core   |Version:  master
  (System checks)|   Keywords:  translations,
   Severity:  Normal |  system checks, language tags
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Following on from #29713 which added `translation.E001` to check
 `LANGUAGE_CODE`, I proposed the following:;

 - `translation.E002`: `'You have provided an invalid language code in the
 LANGUAGES setting: {}.'`
 - `translation.E003`: `'You have provided an invalid language code in the
 LANGUAGES_BIDI setting: {}.'`
 - `translation.E004`: `'You have provided a value for the LANGUAGE_CODE
 setting that is not in the LANGUAGES setting.'`
 - `translation.W005`: `'You have provided values in the LANGUAGE_BIDI
 setting that are not in the LANGUAGES setting.'`

 Note `W005` instead of `E005` - this case can simply be a warning because
 it will not cause things to go wrong, but highlights a potential
 configuration issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.0efe668dcf6d145d645e2eb07156f098%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:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sha1, sha224,| Triage Stage:
  sha256, sha384, sha512 |  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/11059 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.ca240b051d777c869184e10379b3432a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

#30240: Add support for SHA database functions.
-+-
   Reporter:  Nick Pope  |  Owner:  Nick Pope
   Type:  New| Status:  assigned
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:  sha1, sha224,
   Severity:  Normal |  sha256, sha384, sha512
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Following on from `MD5()` defined in #28643, we can add support for
 `SHA1()`, `SHA224()`, `SHA256()`, `SHA384()` and `SHA512()`.

 There are two caveats:

 - `SHA224()` is not supported by `STANDARD_HASH` in Oracle.
 - PostgreSQL requires the use of the `pgcrypto` extension.

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

Re: [Django] #30239: TIME_ZONE (settings.py) TZ database name is incorrect for Kyiv: it should be Kyiv instead of Kiev

[Django]

#30239: TIME_ZONE (settings.py) TZ database name is incorrect for Kyiv: it 
should
be Kyiv instead of Kiev
-+-
 Reporter:  Znakharenko Bogdan   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  2.1
  Internationalization   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  settings, timezone   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 The accepts values are dictated by
 
[https://github.com/newvem/pytz/blob/f137ff00112a9682bc4e4945067b3b88f158d010/pytz/__init__.py#L668
 pytz], not Django.

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

Re: [Django] #7835: Provide the ability for model definitions that are only availably during testing

[Django]

#7835: Provide the ability for model definitions that are only availably during
testing
-+
 Reporter:  Russell Keith-Magee  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feature test models  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Simon Charette):

 * cc: Simon Charette (added)


Comment:

 While working on a workaround for this I came up with a non-invasive
 solution that might be acceptable to resolving the ticket.

 The idea is similar to Ashley's solution but is more explicit as it
 require a function call in the `app/tests/__init__.py` module. It does
 however isolate each app into their own app, which prevent name
 collisions, and doesn't require the `app_label = 'test'` assignment on
 each test model.

 The solutions boils down to this function

 {{{#!python
 def setup_test_app(package, label=None):
 """
 Setup a Django test app for the provided package to allow test models
 tables to be created if the containing app has migrations.

 This function should be called from app.tests __init__ module and pass
 along __package__.
 """
 app_config = AppConfig.create(package)
 app_config.apps = apps
 if label is None:
 containing_app_config = apps.get_containing_app_config(package)
 label = f'{containing_app_config.label}_tests'
 if label in apps.app_configs:
 raise ValueError(f"There's already an app registered with the
 '{label}' label.')
 app_config.label = label
 apps.app_configs[app_config.label] = app_config
 app_config.import_models()
 apps.clear_cache()
 }}}

 Which when called from `app/tests/__init__.py` as
 `setup_test_app(__package__)` will create an `app_tests` appconfig entry
 and auto-discover the models automatically. Since the `*.tests` modules
 should only be loaded on test discovery the app and its models will only
 be available during tests. Keep in mind that if your test models reference
 models from an application with migrations you'll also need to manually
 create migrations for these tests models but once that's done you should
 be good to go.

 It does feel less magic and convention based than Ashley's solution as it
 prevents conflicts between models and allows multiple test apps per app
 from any test package structure. Thoughts?

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

[Django] #30239: TIME_ZONE (settings.py) TZ database name is incorrect for Kyiv: it should be Kyiv instead of Kiev

[Django]

#30239: TIME_ZONE (settings.py) TZ database name is incorrect for Kyiv: it 
should
be Kyiv instead of Kiev
-+-
   Reporter:  bodyazn|  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  2.1
  Internationalization   |
   Severity:  Normal |   Keywords:  settings, timezone
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Actual accepted by django value for Ukraine is Europe/Kiev, but it should
 be Europe/Kyiv

 Kyiv is NOT Kiev
 https://medium.com/@postinformation/kyiv-not-kiev-61d18237228

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

Re: [Django] #29754: Trunc() should allow passing is_dst resolution to avoid NonExistentTimeError/AmbiguousTimeError

[Django]

#29754: Trunc() should allow passing is_dst resolution to avoid
NonExistentTimeError/AmbiguousTimeError
-+-
 Reporter:  Alexander Holmbäck   |Owner:  Alexander
 |  Holmbäck
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  pytz, Trunc, is_dst  | 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:"d5276398046ce4a102776a1e67dcac2884d80dfe" d527639]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5276398046ce4a102776a1e67dcac2884d80dfe"
 Fixed #29754 -- Added is_dst parameter to Trunc database functions.
 }}}

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

Re: [Django] #30238: Exception when saving model created with string for DateField

[Django]

#30238: Exception when saving model created with string for DateField
-+-
 Reporter:  Mitchell Harvey  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 Looking at the traceback in the ticket description, the crash comes from a
 signal handler, `create_launch_list`.

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

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

Re: [Django] #29471: Set-Cookie response is cached for deleting invalid session cookies

[Django]

#29471: Set-Cookie response is cached for deleting invalid session cookies
-+-
 Reporter:  Duane Hutchins   |Owner:
 |  birthdaysgift
 Type:  Bug  |   Status:  assigned
Component:  contrib.sessions |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  empty session cache  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by birthdaysgift):

 * owner:  nobody => birthdaysgift
 * 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/071.e7ff77e45e6f315264dd4a87eee8e725%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30186: Show applied datetime in showmigrations

[Django]

#30186: Show applied datetime in showmigrations
-+-
 Reporter:  Timothy Schilling|Owner:  Timothy
 |  Schilling
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Ready for
  showmigrations |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Just needs a squash and a rebase.

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

Re: [Django] #30186: Show applied datetime in showmigrations

[Django]

#30186: Show applied datetime in showmigrations
-+-
 Reporter:  Timothy Schilling|Owner:  Timothy
 |  Schilling
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Ready for
  showmigrations |  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


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

Re: [Django] #30238: Exception when saving model created with string for DateField

[Django]

#30238: Exception when saving model created with string for DateField
-+-
 Reporter:  Mitchell Harvey  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 Carlton Gibson):

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


Comment:

 The `AttributeError` is not raised. This test fails as the
 `assertRaisesMessage()` call:

 {{{
 class Tests(TestCase):

 def test_attribute_error_stops_save(self):

 my_model_args = { 'worthless_field' : '2019-02-07'}
 myExceptionalModel = MyModel( **my_model_args)

 msg = "'str' object has no attribute 'isoformat'"
 with self.assertRaisesMessage(AttributeError, msg):
 myExceptionalModel.save()

 self.assertEqual(0, MyModel.objects.count())
 }}}

 Behaviour is as expected:


 {{{
 >>> myExceptionalModel.save()
 >>> myExceptionalModel.refresh_from_db()
 >>> myExceptionalModel.worthless_field
 datetime.date(2019, 2, 7)
 }}}

 Sample app with model and test case attached.

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

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

Re: [Django] #30238: Exception when saving model created with string for DateField

[Django]

#30238: Exception when saving model created with string for DateField
-+-
 Reporter:  Mitchell Harvey  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 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 Carlton Gibson):

 * Attachment "ticket_30238.zip" added.

 Sample app with provided model and test 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.7c51f079dd20b05ba3f1efeab6827e48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.