Re: [Django] #33002: Make DebugLexer.tokenize() more similar to Lexer.tokenize()

[Django]

#33002: Make DebugLexer.tokenize() more similar to Lexer.tokenize()
-+-
 Reporter:  Chris Jerdonek   |Owner:  Chris
 Type:   |  Jerdonek
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  dev
 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 Chris Jerdonek):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/14753

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

[Django] #33002: Make DebugLexer.tokenize() more similar to Lexer.tokenize()

[Django]

#33002: Make DebugLexer.tokenize() more similar to Lexer.tokenize()
-+-
   Reporter:  Chris  |  Owner:  Chris Jerdonek
  Jerdonek   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Template   |Version:  dev
  system |
   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  |
-+-
 Currently,
 
[https://github.com/django/django/blob/8208381ba6a3d1613bb746617062ccf1a6a28591/django/template/base.py#L396-L418
 DebugLexer.tokenize()] looks somewhat dissimilar to
 
[https://github.com/django/django/blob/8208381ba6a3d1613bb746617062ccf1a6a28591/django/template/base.py#L352-L364
 Lexer.tokenize()], even though they do more or less the same thing. For
 example, the `Lexer` class's implementation contains just one call to
 `self.create_token()`, whereas `DebugLexer` contains three calls to it.

 This ticket is to make `DebugLexer.tokenize()` look visibly much more the
 same as `Lexer.tokenize()`, and in particular simpler. One advantage is
 that it will be more obvious on inspection that `DebugLexer` acts the same
 as `Lexer`. Another advantage is that it will be easier to keep the two
 implementations in step when applying optimizations to `Lexer`. It will be
 more maintainable and less likely to introduce bugs if the implementations
 for the two lexers don't diverge too much.

 The idea will become more clear once the PR is posted.

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

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

Re: [Django] #32995: Incorrect GROUP BY in ORM query with Function

[Django]

#32995: Incorrect GROUP BY in ORM query with Function
-+-
 Reporter:  Joshua "jag" |Owner:  nobody
  Ginsberg   |
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.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:  0|UI/UX:  0
-+-
Changes (by Joshua "jag" Ginsberg):

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


Comment:

 I think I found the issue/discrepancy between the model snippet and my
 actual one: the default ordering for queries included `called_at` -- which
 seems to have affected the GROUP BY, even though `called_at` wasn't in the
 query and the resulting SQL didn't have an ORDER BY clause.

 This feels like a bug, though not the one I originally believed. 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ed67f004ca5b028d03e56c8bedb74c6e%40djangoproject.com.

Re: [Django] #32997: Errors in 404 templates are hard to debug

[Django]

#32997: Errors in 404 templates are hard to debug
-+--
 Reporter:  jooadam  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Error reporting  |  Version:  3.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 jooadam):

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


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

Re: [Django] #32997: Errors in 404 templates are hard to debug

[Django]

#32997: Errors in 404 templates are hard to debug
-+--
 Reporter:  jooadam  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  3.2
 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
-+--

Comment (by jooadam):

 Replying to [comment:4 Mariusz Felisiak]:
 > I cannot because you have not explained the issue in enough detail to
 confirm a bug in Django. Please reopen the ticket if you can debug your
 issue and provide details about why and where Django is at fault.

 I explained the issue in the exact detail you would have needed to
 reproduce it: a 404.html with an error in production mode. See the
 attachment.

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

Re: [Django] #32997: Errors in 404 templates are hard to debug

[Django]

#32997: Errors in 404 templates are hard to debug
-+--
 Reporter:  jooadam  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  3.2
 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 jooadam):

 * Attachment "404-error.zip" added.


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

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

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

[Django]

#32210: Django Admin with Inlines not using UUIDField default value
--+
 Reporter:  Joseph Metzinger  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  3.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 kamilturek):

 Looks like it's not directly related to formsets' validation but
 instantiating formset's forms.


 {{{
 (Pdb) new_object.id
 UUID('06048350-3ad9-45f5-bca3-d08d795d7231')
 (Pdb) formsets[0].forms
 []
 (Pdb) new_object.id
 (Pdb)
 }}}

 {{{
 (Pdb) new_object.id
 UUID('652863a7-ccc8-4a18-9390-6fb77aa4bafa')
 (Pdb) formsets[0]._construct_form(0)
 
 (Pdb) new_object.id
 (Pdb)
 }}}

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

Re: [Django] #32997: Errors in 404 templates are hard to debug

[Django]

#32997: Errors in 404 templates are hard to debug
-+--
 Reporter:  jooadam  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  3.2
 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
-+--

Comment (by Mariusz Felisiak):

 > Mariusz, can you please explain to me how is an error in a template
 resulting in an 500 error not having a stack trace included in the email
 report not a bug?

 I cannot because you have not explained the issue in enough detail to
 confirm a bug in Django. Please reopen the ticket if you can debug your
 issue and provide details about why and where Django is at fault.

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

Re: [Django] #32997: Errors in 404 templates are hard to debug

[Django]

#32997: Errors in 404 templates are hard to debug
-+--
 Reporter:  jooadam  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  3.2
 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
-+--

Comment (by jooadam):

 Replying to [comment:2 Mariusz Felisiak]:
 > It looks like you're asking for help with debugging. Trac is not a
 support channel. Please see TicketClosingReasons/UseSupportChannels for
 ways to get help.

 Mariusz, can you please explain to me how is an error in a template
 resulting in an 500 error not having a stack trace included in the email
 report not a bug? I have already found the issue in my code, so at this
 point I’m solely trying to make Django better by making the effort
 reporting it. I would expect you to take it a little more seriously.

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

Re: [Django] #32993: Refactor AutocompleteJsonView to support extra fields in autocomplete response

[Django]

#32993: Refactor AutocompleteJsonView to support extra fields in autocomplete
response
---+
 Reporter:  mrts   |Owner:  mrts
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Jacob Walls):

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


Comment:

 Just a small note for future: you can keep the ticket assigned to yourself
 while you're actively maintaining a PR for it.

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

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

Re: [Django] #32998: process_view() is not called on 404

[Django]

#32998: process_view() is not called on 404
---+--
 Reporter:  jooadam|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  3.2
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => needsinfo
 * component:  Uncategorized => HTTP handling


Comment:

 It works for me. Please reopen the ticket if you can debug your issue and
 provide more details or a sample project. If you're having trouble
 understanding how Django works, see
 TicketClosingReasons/UseSupportChannels for ways to get help.

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

Re: [Django] #32997: Errors in 404 templates are hard to debug

[Django]

#32997: Errors in 404 templates are hard to debug
-+--
 Reporter:  jooadam  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  3.2
 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 Mariusz Felisiak):

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


Comment:

 It looks like you're asking for help with debugging. Trac is not a support
 channel. Please see TicketClosingReasons/UseSupportChannels for ways to
 get help.

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

[Django] #33001: ManifestStaticFilesStorage is problematic - need changes here

[Django]

#33001: ManifestStaticFilesStorage is problematic - need changes here
+
   Reporter:  Man Python|  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  File uploads/storage  |Version:  3.2
   Severity:  Normal|   Keywords:  Static
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 
https://docs.djangoproject.com/en/3.2/ref/contrib/staticfiles/#manifeststaticfilesstorage
 ''A subclass of the StaticFilesStorage storage backend which stores the
 file names it handles by appending the MD5 hash of the file’s content to
 the filename. For example, the file css/styles.css would also be saved as
 css/styles.55e7cbb9ba48.css.''

 I think we should have something like **'css/styles.css?55e7cbb9ba48'** as
 ManifestStaticFilesHashRequest, without file changes.
 For browser this changed hash creating request ouside cache.

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

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

Re: [Django] #29299: Add type hints (PEP 484) and variable annotations (PEP 526)

[Django]

#29299: Add type hints (PEP 484) and variable annotations (PEP 526)
-+-
 Reporter:  Andreas Galazis  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andreas Galazis):

 Adding them in the framework would make changes to the framework more
 smooth since typings would be updated within the codebase and there will
 be no need for a new stub release (or waiting for the stub release).
 I understand that it might involve a bit of donkey work to merge the stubs
 in the framework.
 If we find a tool to merge it automatically, would it be acceptable?
 As a side note I stumbled on this:
 https://pythonrepo.com/repo/ambv-retype-python-code-refactoring

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

Re: [Django] #29026: Make makemigrations scriptable / script-friendly

[Django]

#29026: Make makemigrations scriptable / script-friendly
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  makemigrations,scripting,stderr,stdout|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

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


Comment:

 I'm going to take a look at implementing Chris's suggested `log()` method.
 (See 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/067.0da5a5bc7c53bcfb35fe45c3db90b8ac%40djangoproject.com.

Re: [Django] #32993: Refactor AutocompleteJsonView to support extra fields in autocomplete response

[Django]

#32993: Refactor AutocompleteJsonView to support extra fields in autocomplete
response
---+
 Reporter:  mrts   |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by mrts):

 * owner:  mrts => (none)
 * status:  assigned => new
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/14752/files 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/062.cf089a7191f0fa3b2ba196e5b7ec9f5c%40djangoproject.com.

Re: [Django] #29026: Make makemigrations scriptable / script-friendly

[Django]

#29026: Make makemigrations scriptable / script-friendly
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  makemigrations,scripting,stderr,stdout|
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * needs_tests:  0 => 1


Comment:

 Until I remedy the test failure on Windows.

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

Re: [Django] #32993: Refactor AutocompleteJsonView to support extra fields in autocomplete response

[Django]

#32993: Refactor AutocompleteJsonView to support extra fields in autocomplete
response
---+
 Reporter:  mrts   |Owner:  mrts
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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 mrts):

 * owner:  nobody => mrts
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.cc09ae5881b8f6435c1803c814594eb9%40djangoproject.com.

Re: [Django] #29026: Make makemigrations scriptable / script-friendly

[Django]

#29026: Make makemigrations scriptable / script-friendly
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  makemigrations,scripting,stderr,stdout|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * 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/067.6e7228809a54e5cd9e759772e0ba9dbc%40djangoproject.com.

Re: [Django] #32992: Reverse time zone conversion in Trunc()/Extract() database functions.

[Django]

#32992: Reverse time zone conversion in Trunc()/Extract() database functions.
-+-
 Reporter:  James Beith  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 tigicion):

 * owner:  tigicion => (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.56daa273833a784c85d34ee7deed6248%40djangoproject.com.

Re: [Django] #33000: Form does not render html input of RadioSelect

[Django]

#33000: Form does not render html input of RadioSelect
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  3.2
 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 Michael):

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


Comment:

 If an input is marked as hidden it is not submitted with 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.dce3acfbcdb36ff20d3ba19d4e22c1fb%40djangoproject.com.

Re: [Django] #33000: Form does not render html input of RadioSelect

[Django]

#33000: Form does not render html input of RadioSelect
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.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
---+--
Description changed by Michael:

Old description:

> A form with the following field:
> {{
> send = forms.BooleanField(label=False,
> widget=forms.RadioSelect(attrs={'hidden':True}))
> }}
>
> when rendered as:
> {{ form.as_table }}
>
> will be rendered as:
> {{
> 
> 
> 
> 
> 
> 
> 
> }}
>
> Note the lack of input widget. I am trying to create a hidden radio
> button, to store a boolean value that gets sent to the server. A
> `CheckboxInput` however does work, and is argueably better in this
> situation, but this may point to some underlying bug.

New description:

 A form with the following field:
 {{{
 send = forms.BooleanField(label=False,
 widget=forms.RadioSelect(attrs={'hidden':True}))
 }}}

 when rendered as:
 {{{
 {{ form.as_table }}
 }}}

 will be rendered as:
 {{{
 
 
 
 
 
 
 
 }}}

 Note the lack of input widget. I am trying to create a hidden radio
 button, to store a boolean value that gets sent to the server. A
 **CheckboxInput** however does work, and is argueably better in this
 situation, but this may point to some underlying 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.ceb82935f5b5080dc6f51c05e3cdaec0%40djangoproject.com.

[Django] #33000: Form does not render html input of RadioSelect

[Django]

#33000: Form does not render html input of RadioSelect
-+
   Reporter:  Michael|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Forms  |Version:  3.2
   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  |
-+
 A form with the following field:
 {{
 send = forms.BooleanField(label=False,
 widget=forms.RadioSelect(attrs={'hidden':True}))
 }}

 when rendered as:
 {{ form.as_table }}

 will be rendered as:
 {{
 
 
 
 
 
 
 
 }}

 Note the lack of input widget. I am trying to create a hidden radio
 button, to store a boolean value that gets sent to the server. A
 `CheckboxInput` however does work, and is argueably better in this
 situation, but this may point to some underlying 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.8154291b68bcac5ca783bd4eedcb590e%40djangoproject.com.

Re: [Django] #32999: Admin Tabular Stacked Inline widget headings are not aligned headings

[Django]

#32999: Admin Tabular Stacked Inline widget headings are not aligned headings
-+-
 Reporter:  Michael  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  tabularinline css| Triage Stage:
  style styling  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Michael:

Old description:

> See the attached pic.
>
> With the following model:
>
> {{{
> class ApplicantAdmin(admin.TabularInline):
> model = Application.applicant_set.through
>
> @admin.register(Application)
> class ApplicationAdmin(admin.ModelAdmin):
> exclude = ('applicant_set', )
> inlines = (ApplicantAdmin, )
>
> }}}
>
> The heading `Delete?` is on the left, however the delete button is on the
> right, making it confusing for some people.

New description:

 
[[Image(https://code.djangoproject.com/attachment/ticket/32999/notaligned.png)]]

 With the following model:

 {{{
 class ApplicantAdmin(admin.TabularInline):
 model = Application.applicant_set.through

 @admin.register(Application)
 class ApplicationAdmin(admin.ModelAdmin):
 exclude = ('applicant_set', )
 inlines = (ApplicantAdmin, )

 }}}

 The heading `Delete?` is on the left, however the delete button is on the
 right, making it confusing for some people.

--

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

Re: [Django] #32999: Admin Tabular Stacked Inline widget headings are not aligned headings

[Django]

#32999: Admin Tabular Stacked Inline widget headings are not aligned headings
-+-
 Reporter:  Michael  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  tabularinline css| Triage Stage:
  style styling  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Michael:

Old description:

> With the following model:
> ```
> class ApplicantAdmin(admin.TabularInline):
> model = Application.applicant_set.through
>
> @admin.register(Application)
> class ApplicationAdmin(admin.ModelAdmin):
> exclude = ('applicant_set', )
> inlines = (ApplicantAdmin, )
> ```
> The heading `Delete?` is on the left, however the delete button is on the
> right, making it confusing for some people.

New description:

 See the attached pic.

 With the following model:

 {{{
 class ApplicantAdmin(admin.TabularInline):
 model = Application.applicant_set.through

 @admin.register(Application)
 class ApplicationAdmin(admin.ModelAdmin):
 exclude = ('applicant_set', )
 inlines = (ApplicantAdmin, )

 }}}

 The heading `Delete?` is on the left, however the delete button is on the
 right, making it confusing for some people.

--

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

Re: [Django] #32999: Admin Tabular Stacked Inline widget headings are not aligned headings

[Django]

#32999: Admin Tabular Stacked Inline widget headings are not aligned headings
-+-
 Reporter:  Michael  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  tabularinline css| Triage Stage:
  style styling  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Michael):

 * Attachment "notaligned.png" added.


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

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

[Django] #32999: Admin Tabular Stacked Inline widget headings are not aligned headings

[Django]

#32999: Admin Tabular Stacked Inline widget headings are not aligned headings
-+-
   Reporter:  Michael|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  3.2
  contrib.admin  |   Keywords:  tabularinline css
   Severity:  Normal |  style styling
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 With the following model:
 ```
 class ApplicantAdmin(admin.TabularInline):
 model = Application.applicant_set.through

 @admin.register(Application)
 class ApplicationAdmin(admin.ModelAdmin):
 exclude = ('applicant_set', )
 inlines = (ApplicantAdmin, )
 ```
 The heading `Delete?` is on the left, however the delete button is on the
 right, making it confusing for some people.

-- 
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/053.c4e10c13c7955bf3d22da3648b9e7021%40djangoproject.com.

Re: [Django] #32996: Cache PathInfos on ForeignObject/ForeignObjectRel (et al)

[Django]

#32996: Cache PathInfos on ForeignObject/ForeignObjectRel (et al)
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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 Keryn Knight):

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


Comment:

 Yes, it does rather sound like the last line of the ticket is me holding
 the implementation hostage until it's triaged. Wasn't the intent, just
 forgot to come back and update it once CI had run :) Feel free to put it
 back to untriaged if that was a deciding factor :)

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

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

Re: [Django] #32996: Cache PathInfos on ForeignObject/ForeignObjectRel (et al)

[Django]

#32996: Cache PathInfos on ForeignObject/ForeignObjectRel (et al)
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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 David Smith):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting so discussion can continue with the code in front of us.

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