Re: [Django] #28483: Unclear language in Django 2.0 release notes regarding Python version support (was: Possible typo in Django 2.0 release notes regarding Python version support)

[Django]

#28483: Unclear language in Django 2.0 release notes regarding Python version
support
---+
 Reporter:  Vasili Korol   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham):

 * resolution:  invalid => fixed
 * stage:  Unreviewed => Accepted


Comment:

 I've changed the language in the
 [https://github.com/django/django/pull/8884 PR] to document Python 3.4
 support for Django 2.0.

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

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

Re: [Django] #28485: Make ExceptionReporter.get_traceback_frames() include frames without source code (was: Stack trace report silently drops frames without source code)

[Django]

#28485: Make ExceptionReporter.get_traceback_frames() include frames without 
source
code
---+
 Reporter:  Martin von Gagern  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Error reporting|  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 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/064.a68f25db043ec31eccc77e89762bafe0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28473: Consider SCRIPT_NAME for SECURE_REDIRECT_EXEMPT setting

[Django]

#28473: Consider SCRIPT_NAME for SECURE_REDIRECT_EXEMPT setting
---+--
 Reporter:  Jonas Haag |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.11
 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
---+--

Comment (by Jonas Haag):

 See #25598 for discussion of the use case (the setting should be
 independent from the subpath the application is mounted at). This breaks
 existing sites, yes. I haven't had a look into the implementation.

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

Re: [Django] #28486: Template FileLoader can't find widget templates

[Django]

#28486: Template FileLoader can't find widget templates
-+-
 Reporter:  Andrey   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  widgets, templates,  | Triage Stage:
  admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Do you have `FORM_RENDERER = 'django.forms.renderers.TemplatesSetting'` in
 your settings? The default `DjangoTemplates` renderer doesn't consult the
 `TEMPLATES` setting. Please read
 [https://docs.djangoproject.com/en/stable/ref/forms/renderers/ The form
 rendering API] documentation.

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

Re: [Django] #27855: Document Python 3.4 support for Django 2.0 (was: Django 2.0 Python version support)

[Django]

#27855: Document Python 3.4 support for Django 2.0
-+-
 Reporter:  Raffaele Salmaso |Owner:  Raffaele
 Type:   |  Salmaso
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Someday/Maybe => Accepted


Comment:

 The mailing list didn't reveal a consensus to drop Python 3.4 support for
 Django 2.0. [https://github.com/django/django/pull/8884 PR] to update the
 docs.

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

Re: [Django] #28477: Strip unused annotations from count queries

[Django]

#28477: Strip unused annotations from count queries
-+-
 Reporter:  Tom  |Owner:  Tom
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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
-+-

Comment (by Tom):

 Same can be done for `exists()`

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

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

[Django] #28486: Template FileLoader can't find widget templates

[Django]

#28486: Template FileLoader can't find widget templates
-+-
   Reporter:  Andrey |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Template   |Version:  1.11
  system |   Keywords:  widgets, templates,
   Severity:  Normal |  admin
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have both apps and file loaders in my project. I load custom directory
 called "templates" in the root of the project.

 In case I want to override template for field widget from Django Admin
 (perhaps it related to regular widgets as well) and I create a file under
 "templates/admin/widgets/clearable_file_input.html". Nothing happens. If I
 will move it somewhere under "/templates/widgets/clearable_file_input.html" it works fine. However,
 I can override "admin/base.html" and few other templates from admin by
 placing them in "templates/" folder.

 I played around and found that when looking for templates for widget
 Django loads all template directories for apps, but doesn't load anything
 from DIRS parameter. In the same time, it loads everything properly for
 other templates.

 If description is messy or unclear please ask, and I will clarify unclear
 parts.

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

Re: [Django] #28485: Stack trace report silently drops frames without source code

[Django]

#28485: Stack trace report silently drops frames without source code
---+--
 Reporter:  Martin von Gagern  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Error reporting|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Srinivas Reddy Thatiparthy):

 PR is here - https://github.com/django/django/pull/8880

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

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

Re: [Django] #18392: Use utf8mb4 encoding with MySQL 5.5

[Django]

#18392: Use utf8mb4 encoding with MySQL 5.5
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  utf8mb4 mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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


Comment:

 I provided a [https://github.com/django/django/pull/8886 more
 comprehensive patch].

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

Re: [Django] #28455: Create "inplace" QuerySets to speed up certain operations

[Django]

#28455: Create "inplace" QuerySets to speed up certain operations
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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
-+-

Comment (by Tim Graham):

 I
 
[https://github.com/django/django/compare/master...timgraham:28455-inplace?expand=1
 rebased work] from
 [https://github.com/akaariai/django/commits/splitted_clone Anssi's
 branch]. I guess the plan was to keep "inplace" as a private API initially
 (hence the underscore prefix) but I'm not sure. Someone else is welcome to
 continue this work. I'm not planning to continue it soon.

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

Re: [Django] #16043: Specialization cache should be filled/shared with parent object cache (multitable inheritance)

[Django]

#16043: Specialization cache should be filled/shared with parent object cache
(multitable inheritance)
-+-
 Reporter:  Piotr Czachur|Owner:  Paulo
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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
-+-

Comment (by Tim Graham ):

 In [changeset:"bfb746f983aa741afa3709794e70f1e0ab6040b5" bfb746f9]:
 {{{
 #!CommitTicketReference repository=""
 revision="bfb746f983aa741afa3709794e70f1e0ab6040b5"
 Refs #16043 -- Refactored internal fields value cache.

 * Removed all hardcoded logic for _{fieldname}_cache.
 * Added an internal API for interacting with the field values cache.

 Thanks carljm and MarkusH for support.
 }}}

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

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

Re: [Django] #23766: Documentation and tests for cursor.callproc()

[Django]

#23766: Documentation and tests for cursor.callproc()
-+-
 Reporter:  Shai Berger  |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 GitHub ):

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


Comment:

 In [changeset:"660d50805b6788d592b4f1fae706b725baf0195c" 660d5080]:
 {{{
 #!CommitTicketReference repository=""
 revision="660d50805b6788d592b4f1fae706b725baf0195c"
 Fixed #23766 -- Doc'd CursorWrapper.callproc().

 Thanks Tim Graham for the review.
 }}}

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

Re: [Django] #23766: Documentation and tests for cursor.callproc()

[Django]

#23766: Documentation and tests for cursor.callproc()
-+-
 Reporter:  Shai Berger  |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 ):

 In [changeset:"fe51017efdc3f26c94c83fe5930b14d71e1bb380" fe51017e]:
 {{{
 #!CommitTicketReference repository=""
 revision="fe51017efdc3f26c94c83fe5930b14d71e1bb380"
 [1.11.x] Fixed #23766 -- Doc'd CursorWrapper.callproc().

 Thanks Tim Graham for the review.
 Backport of 660d50805b6788d592b4f1fae706b725baf0195c from master
 }}}

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

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

Re: [Django] #18247: Filtering on aggregate annotations with a Decimal value doesn't work

[Django]

#18247: Filtering on aggregate annotations with a Decimal value doesn't work
-+-
 Reporter:  elmopl@… |Owner:  Michael
 |  Tänzer
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  decimal filter   | Triage Stage:  Ready for
  annotate having|  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:"c3c6c92d769d44a98299c462c48a9599c0172e91" c3c6c92d]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3c6c92d769d44a98299c462c48a9599c0172e91"
 Refs #18247 -- Fixed filtering on
 CombinedExpression(output_field=DecimalField()) annotation on SQLite.
 }}}

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

Re: [Django] #26488: migrate crashes when renaming a multi-table inheritance base model

[Django]

#26488: migrate crashes when renaming a multi-table inheritance base model
-+-
 Reporter:  Christopher  |Owner:  nobody
  Neugebauer |
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.9
 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 Christopher Neugebauer):

 So here's something fun. Here's how you *can* create a model with a base
 class whose name you can change, and Migrations will be happy.

 1. Create a model `SubModel`, it must derive from `models.Model`.
 2. Create a new base class, `BaseModel`, it must derive from
 `models.Model`
 3. Add: `basemodel_ptr = OneToOneField(BaseModel, null=True)` on
 `SubModel`. The field *must* be named like the class name of the new base
 class.
 4. Automatically create a migration
 5. Create a data migration that creates a new `BaseModel(id=submodel.id)`
 for each `SubModel` instance. This step is only necessary if you have
 created `SubModel` objects. Otherwise, just use an automatic default.
 6. Set the base model of `SubModel` to `BaseModel`
 7. Automatically create a migration
 8. Rename `BaseModel` to `RenamedBaseModel`
 9. Automatically create a migration, accepting the two automatic
 suggestions
 10. Migrate!

 At this point, you can see that `RenamedBaseModel` works as expected. It
 appears as though everything here works, as long as you aren't tracking
 the base class when migrations first creates the model.

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

Re: [Django] #28459: Improve performance of QuerySet

[Django]

#28459: Improve performance of QuerySet
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Tim Graham ):

 In [changeset:"22ff86ec52bb536ad9d1fa3ee0c9a3d5eb9925c1" 22ff86e]:
 {{{
 #!CommitTicketReference repository=""
 revision="22ff86ec52bb536ad9d1fa3ee0c9a3d5eb9925c1"
 Refs #28459 -- Made Oracle get_db_converters() return converter for empty
 strings only when it's needed.
 }}}

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

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

Re: [Django] #28477: Strip unused annotations from count queries

[Django]

#28477: Strip unused annotations from count queries
-+-
 Reporter:  Tom  |Owner:  Tom
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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 Tom):

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

Re: [Django] #28473: Consider SCRIPT_NAME for SECURE_REDIRECT_EXEMPT setting

[Django]

#28473: Consider SCRIPT_NAME for SECURE_REDIRECT_EXEMPT setting
---+--
 Reporter:  Jonas Haag |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.11
 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
---+--

Comment (by Tim Graham):

 I guess the idea would be to use `request.path_info` instead of
 `request.path` in the
 
[https://github.com/django/django/blob/5cb7619995bd8df2969d4e92984768a4f14af89b/django/middleware/security.py#L21
 SecurityMiddleware]?

 Can you elaborate on the use case and how the behavior will change? Could
 the change break existing working configurations?

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

Re: [Django] #28459: Improve performance of QuerySet

[Django]

#28459: Improve performance of QuerySet
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Sergey Fedoseev):

 [https://github.com/django/django/pull/8878 PR (Improved performance of
 loading DecimalField on SQLite)]
 Before:
 {{{
 In [5]: %timeit for x in Test.objects.values_list('decimal'): pass
 150 ms ± 1.76 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 In [6]: %timeit for x in Test.objects.values_list(models.F('decimal') +
 1): pass
 123 ms ± 1.08 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}
 After:
 {{{
 In [2]: %timeit for x in Test.objects.values_list('decimal'): pass
 28.8 ms ± 1.05 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
 In [3]: %timeit for x in Test.objects.values_list(models.F('decimal') +
 1): pass
 84.6 ms ± 541 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
 }}}

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

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

Re: [Django] #27855: Document Python 3.4 support for Django 2.0

[Django]

#27855: Document Python 3.4 support for Django 2.0
-+-
 Reporter:  Raffaele Salmaso |Owner:  Raffaele
 Type:   |  Salmaso
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  2.0  | 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 felixxm):

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

Re: [Django] #26488: migrate crashes when renaming a multi-table inheritance base model

[Django]

#26488: migrate crashes when renaming a multi-table inheritance base model
-+-
 Reporter:  Christopher  |Owner:  nobody
  Neugebauer |
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.9
 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 Christopher Neugebauer):

 So the previous example is a bit evil. Here's a reduced example that
 *works* in Django 1.11:

 **Step 0**
 {{{
 class BaseModel(models.Model):
 pass


 class SubModel(BaseModel):
 basemodel_ptr = models.OneToOneField(BaseModel, null=True)
 }}}
 Run `makemigrations`

 **Step 1**
 {{{
 class BaseModel(models.Model):
 pass


 class SubModel(BaseModel):
 pass
 }}}
 Run `makemigrations`


 **Step 2**
 {{{
 class RenamedBaseModel(models.Model):
 pass


 class SubModel(RenamedBaseModel):
 pass

 }}}
 Run `makemigrations`


 If you start with Step 0, you can successfully `migrate` at the end of
 step 2.
 If you start with Step 1, `migrate` breaks, but with a new error:

 `django.core.exceptions.FieldError: Auto-generated field 'basemodel_ptr'
 in class 'SubModel' for parent_link to base class 'BaseModel' clashes with
 declared field of the same name.`

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

Re: [Django] #28459: Improve performance of QuerySet

[Django]

#28459: Improve performance of QuerySet
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Tim Graham ):

 In [changeset:"a146b65628e702a9a3ed5be21542ca45366fbb29" a146b656]:
 {{{
 #!CommitTicketReference repository=""
 revision="a146b65628e702a9a3ed5be21542ca45366fbb29"
 Refs #28459 -- Improved performance of loading DecimalField on SQLite.
 }}}

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

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

[Django] #28487: Django1.11.4 Cannot run `manage.py runserver` on Windows (UnicodeDecodeError:)

[Django]

#28487: Django1.11.4 Cannot run `manage.py runserver` on Windows
(UnicodeDecodeError:)
-+-
   Reporter:  newerBkl   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Core   |Version:  1.11
  (Management commands)  |
   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  |
-+-
 My env is windows 7 x64 Python 2.7, after upgrade to 1.11.4 , i can't run
 manager.py runserver
 In 1.11.3 is ok,anything with "Fixed crash in runserver’s autoreload with
 Python 2 on Windows with non-str environment variables (#28174)."
 

 {{{
 (users) D:\django_test\>pip install --upgrade django
 Collecting django
   Using cached Django-1.11.4-py2.py3-none-any.whl
 Requirement already up-to-date: pytz in d:\env_python\users\lib\site-
 packages (from django)
 Installing collected packages: django
   Found existing installation: Django 1.11.3
 Uninstalling Django-1.11.3:
   Successfully uninstalled Django-1.11.3
 Successfully installed django-1.11.4

 (users) D:\django_test\>python manage.py runserver
 Traceback (most recent call last):
   File "manage.py", line 22, in 
 execute_from_command_line(sys.argv)
   File "D:\env_python\users\lib\site-
 packages\django\core\management\__init__.py", line 363, in
 execute_from_command_line
 utility.execute()
   File "D:\env_python\users\lib\site-
 packages\django\core\management\__init__.py", line 355, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "D:\env_python\users\lib\site-
 packages\django\core\management\base.py", line 283, in run_from_argv
 self.execute(*args, **cmd_options)
   File "D:\env_python\users\lib\site-
 packages\django\core\management\commands\runserver.py", line 62, in
 execute
 super(Command, self).execute(*args, **options)
   File "D:\env_python\users\lib\site-
 packages\django\core\management\base.py", line 330, in execute
 output = self.handle(*args, **options)
   File "D:\env_python\users\lib\site-
 packages\django\core\management\commands\runserver.py", line 101, in
 handle
 self.run(**options)
   File "D:\env_python\users\lib\site-
 packages\django\core\management\commands\runserver.py", line 110, in run
 autoreload.main(self.inner_run, None, options)
   File "D:\env_python\users\lib\site-packages\django\utils\autoreload.py",
 line 341, in main
 reloader(wrapped_main_func, args, kwargs)
   File "D:\env_python\users\lib\site-packages\django\utils\autoreload.py",
 line 312, in python_reloader
 exit_code = restart_with_reloader()
   File "D:\env_python\users\lib\site-packages\django\utils\autoreload.py",
 line 294, in restart_with_reloader
 str_value = force_bytes(new_environ[key], encoding=encoding)
   File "D:\env_python\users\lib\site-packages\django\utils\encoding.py",
 line 124, in force_bytes
 return s.decode('utf-8', errors).encode(encoding, errors)
   File "D:\env_python\users\lib\encodings\utf_8.py", line 16, in decode
 return codecs.utf_8_decode(input, errors, True)
 UnicodeDecodeError: 'utf8' codec can't decode byte 0xb8 in position 202:
 invalid start byte
 }}}

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

Re: [Django] #28386: Operations within non-atomic migrations don't honor the operation's `atomic` flag when migrating backwards

[Django]

#28386: Operations within non-atomic migrations don't honor the operation's
`atomic` flag when migrating backwards
+-
 Reporter:  Evan Grim   |Owner:  Evan Grim
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:  fixed
 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 ):

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


Comment:

 In [changeset:"7937cc16f5fafb33a53b9a9ff286229fcc5ba67f" 7937cc1]:
 {{{
 #!CommitTicketReference repository=""
 revision="7937cc16f5fafb33a53b9a9ff286229fcc5ba67f"
 Fixed #28386 -- Made operations within non-atomic migrations honor the
 operation's atomic flag when migrating backwards.
 }}}

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

Re: [Django] #28384: ModelAdmin.lookup_allowed() incorrectly raises DisallowedModelAdminLookup lookup with foreign key as primary key

[Django]

#28384: ModelAdmin.lookup_allowed() incorrectly raises 
DisallowedModelAdminLookup
lookup with foreign key as primary key
--+
 Reporter:  elliott-omosheye  |Owner:  Windson yang
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  1.11
 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 Windson yang):

 * status:  new => assigned
 * owner:  nobody => Windson yang


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

Re: [Django] #28483: Possible typo in Django 2.0 release notes regarding Python version support

[Django]

#28483: Possible typo in Django 2.0 release notes regarding Python version 
support
---+--
 Reporter:  Vasili Korol   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:
 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 Keryn Knight):

 * cc: Keryn Knight (added)


Comment:

 Not to bikeshed on it overly, but "correct as is" is subjective, because
 the phrasing is ambiguous (as may be apparent given the ticket being
 filed).

 "Since Django 1.11, support for Python 2.7 and 3.4 is removed." can be
 read in 2 ways:
 - Subsequent to 1.11 being released, support for ... has been removed"
 [Tim's reading, by my understanding]
 - As of release 1.11, support ... has been removed. [Vasili's reading, by
 my understanding]

 Whilst it is ''correct'' as it currently stands, it relies on parsing of
 English in a specific manner to know what it actually means, and for that
 reason I'd side with the suggestion of re-considering the wording.

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

Re: [Django] #8936: Add view (read-only) permission to admin

[Django]

#8936: Add view (read-only) permission to admin
---+
 Reporter:  simon  |Owner:  Olivier
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Olivier):

 * owner:  Petr Dlouhý => Olivier
 * needs_better_patch:  1 => 0


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

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

Re: [Django] #28483: Possible typo in Django 2.0 release notes regarding Python version support

[Django]

#28483: Possible typo in Django 2.0 release notes regarding Python version 
support
---+--
 Reporter:  Vasili Korol   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:
 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 Vasili Korol):

 Replying to [comment:2 Keryn Knight]:
 Yes, I understood it as'' "starting from 1.11, support has been
 removed''". I can see Tim's point, but I still think that the phrase can
 be misunderstood. It was confusing to me, though I was almost sure that
 1.11 still **does** support Python 2.7 and 3.4.

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