Re: [Django] #19126: Allow runserver to bypass model validation

2020-11-29 Thread Django 
#19126: Allow runserver to bypass model validation
-+-
 Reporter:  Brendan Jurd |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by boxed):

 This ticket was never fixed. The SILENCED_SYSTEM_CHECKS feature doesn't do
 what you would think it does based on this discussion, and even if it did
 work as the documentation says (it doesn't!) it would still be no good:

 1. This ticket asked for the runserver to not die when there are
 validation errors. This request was totally ignored, yet the ticket was
 set to "fixed".
 2. SILENCED_SYSTEM_CHECKS is a list of strings for what to disable. But
 what strings are valid? If you put something invalid here it's ignored.
 You have to step through the code I guess.
 3. Model validation checks aren't even in the SILENCED_SYSTEM_CHECKS list
 from what I can tell.
 4. SILENCED_SYSTEM_CHECKS only silences the OUTPUT of the checks. If they
 fail hard it still fails hard.

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

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

Re: [Django] #32233: Clean-up duplicate connection functionality.

2020-11-29 Thread Django 
#32233: Clean-up duplicate connection functionality.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Florian
 Type:   |  Apolloner
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 [https://github.com/django/django/pull/9272 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e8c20fd8f67afbca9bc431d998369b4d%40djangoproject.com.

[Django] #32233: Clean-up duplicate connection functionality.

2020-11-29 Thread Django 
#32233: Clean-up duplicate connection functionality.
-+-
   Reporter:  Mariusz|  Owner:  Florian Apolloner
  Felisiak   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Core   |Version:  3.1
  (Other)|
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Database and cache connections functionalities could share the same hooks.

 Proposed by Florian Apolloner.

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

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

Re: [Django] #27674: Deprecate GeoModelAdmin and OSMGeoAdmin

2020-11-29 Thread Django 
#27674: Deprecate GeoModelAdmin and OSMGeoAdmin
-+-
 Reporter:  Claude Paroz |Owner:  Giannis
 Type:   |  Adamopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


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

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

Re: [Django] #32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL

2020-11-29 Thread Django 
#32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL
-+-
 Reporter:  Adam (Chainz)|Owner:  kosc
  Johnson|
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (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
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:7 Adam (Chainz) Johnson]:
 > It could be something to do with JSONField changes?

 I can reproduce it at c1c163b42717ed5e051098ebf0e2f5c77810f20e, so it's
 not related with JSONField changes.

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

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

Re: [Django] #31978: Include hidden username field on password reset to help password managers

2020-11-29 Thread Django 
#31978: Include hidden username field on password reset to help password 
managers
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


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

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

Re: [Django] #22909: Fix camelCase test names

2020-11-29 Thread Django 
#22909: Fix camelCase test names
-+-
 Reporter:  Tim Graham   |Owner:  Brylie
 Type:   |  Christopher Oxley
  Cleanup/optimization   |   Status:  closed
Component:  Uncategorized|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"58740c0d7f441e7a12e5847fcd7409a78d9edd7b" 58740c0d]:
 {{{
 #!CommitTicketReference repository=""
 revision="58740c0d7f441e7a12e5847fcd7409a78d9edd7b"
 Refs #22909 -- Removed camelCasing in auth_tests.test_templates tests.
 }}}

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

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

Re: [Django] #31978: Include hidden username field on password reset to help password managers

2020-11-29 Thread Django 
#31978: Include hidden username field on password reset to help password 
managers
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"3828427f634e1880467689e4cf0f8ffee95f0d05" 3828427f]:
 {{{
 #!CommitTicketReference repository=""
 revision="3828427f634e1880467689e4cf0f8ffee95f0d05"
 Refs #31978 -- Fixed hint in admin's password reset confirmation form for
 custom username fields.

 Thanks Jaap Roes 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.843fc52d1f6a5b4a9b5103c3430fb4d0%40djangoproject.com.

Re: [Django] #32232: Typo in docs/ref/contrib/admin/actions.txt. (was: "a export function" should be "an export function" on Admin actions documentation)

2020-11-29 Thread Django 
#32232: Typo in docs/ref/contrib/admin/actions.txt.
--+
 Reporter:  Nat S Dunn|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  3.1
 Severity:  Normal|   Resolution:
 Keywords:  typo  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #27674: Deprecate GeoModelAdmin and OSMGeoAdmin

2020-11-29 Thread Django 
#27674: Deprecate GeoModelAdmin and OSMGeoAdmin
-+-
 Reporter:  Claude Paroz |Owner:  Giannis
 Type:   |  Adamopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  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 Mariusz Felisiak):

 * has_patch:  0 => 1


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

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

Re: [Django] #32219: Use Admin Inline verbose_name as default for Inline verbose_name_plural

2020-11-29 Thread Django 
#32219: Use Admin Inline verbose_name as default for Inline verbose_name_plural
-+-
 Reporter:  Siburg   |Owner:  Siburg
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  Admin Inline | Triage Stage:  Accepted
  verbose_name_plural|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Siburg):

 Updated documentation as well. Figured out where it should go.

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

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

Re: [Django] #32178: Allow database backends to skip tests and mark expected failures

2020-11-29 Thread Django 
#32178: Allow database backends to skip tests and mark expected failures
-+-
 Reporter:  Tim Graham   |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 I'll mark this as RFC when I'm done iterating with Hasan. (Meanwhile,
 let's leave "needs improvement" checked so it doesn't appear in the review
 queue for others.)

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

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

Re: [Django] #27674: Deprecate GeoModelAdmin and OSMGeoAdmin

2020-11-29 Thread Django 
#27674: Deprecate GeoModelAdmin and OSMGeoAdmin
-+-
 Reporter:  Claude Paroz |Owner:  Giannis
 Type:   |  Adamopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Giannis Adamopoulos):

 [https://github.com/django/django/pull/13733 Submitted 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.18b369f10eb933d1fe1151871e8e48e6%40djangoproject.com.

[Django] #32232: "a export function" should be "an export function" on Admin actions documentation

2020-11-29 Thread Django 
#32232: "a export function" should be "an export function" on Admin actions
documentation
+
   Reporter:  Nat S Dunn|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  3.1
   Severity:  Normal|   Keywords:  typo
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 Change "a export function" to "a**n** export function" on
 https://docs.djangoproject.com/en/3.1/ref/contrib/admin/actions/ under
 Actions that provide intermediate pages.

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

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

Re: [Django] #32191: Not RFC 6265 compliant cookies in contrib.messages.

2020-11-29 Thread Django 
#32191: Not RFC 6265 compliant cookies in contrib.messages.
--+---
 Reporter:  Nico Giefing  |Owner:  Craig Smith
 Type:  Bug   |   Status:  assigned
Component:  contrib.messages  |  Version:  3.1
 Severity:  Normal|   Resolution:
 Keywords:  Cookie malformed  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---

Comment (by Florian Apolloner):

 Hi Craig, I've looked through it and thought a bit about it:

 > I have opted to use latin-1 to encode internal to the new functions as
 we use latin-1 elsewhere. I was surprised when using utf-8 that a
 character was unrecognised

 That sounds like a bug to fix. latin-1 encoding will simply not work in
 the general case (Try calling `compress_b64` with u'€'). We run messages
 through `MessageEncoder` which will result in a JSON string which is
 __always__ encodable to `utf-8` (especially since `ensure_ascii` is true).

 > Going forward, I will add tests, in particular to confirm RFC6265
 compliant message cookies

 We also will need tests and a backwards compatibility for old existing
 messages.

 > and I will attempt integrating the new functions as methods of the
 signer base class.

 I'd hold off on that now till we figured out the str/bytes/encoding issues
 -- we might have fond another hornet nest here :)

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

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

Re: [Django] #32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL

2020-11-29 Thread Django 
#32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL
-+-
 Reporter:  Adam (Chainz)|Owner:  kosc
  Johnson|
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (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
-+-

Comment (by kosc):

 Replying to [comment:6 Tom Forbes]:
 > I wonder if this changed at some point, because when I was developing
 this feature I’m almost certain that it returned a string type with valid
 JSON rather than a list of dicts 樂. I can’t see anything in the psycopg2
 release notes to support that though, so maybe I’m misremembering.

 Hello! I see that query "EXPLAIN (FORMAT JSON) SELECT * FROM table_name;"
 returns valid JSON strings in double-quotes, but Django returns a string
 with single-quotes, and when I trying to json.loads string from django I
 getting an error: "JSONDecodeError: Expecting property name enclosed in
 double quotes: line 1 column 3 (char 2)".
 Also, when I trying to replace single quotes with double quotes, I getting
 another error: "JSONDecodeError: Expecting value: line 1 column 55 (char
 54)".

 Here is a string returning by Django ORM: "[{'Plan': {'Node Type': 'Seq
 Scan', 'Parallel Aware': False, 'Relation Name': 'main_testmodel',
 'Alias': 'main_testmodel', 'Startup Cost': 0.0, 'Total Cost': 11.4, 'Plan
 Rows': 140, 'Plan Width': 520}}]" (explain for simple
 TestModel.objects.all().explain(format='json')).

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

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