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:  zimnyx   |Owner:  czpython
 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 czpython):

 Removed the has patch set flag as PR 6721 is only the base for this.
 The fix will be in a separate PR.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.f6d4e7d47b171e5027591959304bb429%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:  zimnyx   |Owner:  czpython
 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 czpython):

 * has_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/064.0952301dce8063ae9ae5cd11f6a122f1%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:  zimnyx   |Owner:  czpython
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by phildini):

 I believe the PR czpython made for this ticket is
 https://github.com/django/django/pull/6721.

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

Re: [Django] #12810: Add validation for clashing ManyToManyField.db_table names

[Django]

#12810: Add validation for clashing ManyToManyField.db_table names
-+-
 Reporter:  strelnikovdmitrij|Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berkerpeksag):

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

Re: [Django] #26708: Update the contributing tutorial to use GitHub workflow (was: Updates to the "Writing your first patch for Django" Documentation Page)

[Django]

#26708: Update the contributing tutorial to use GitHub workflow
--+
 Reporter:  nnja  |Owner:  nnja
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 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 timgraham):

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

Re: [Django] #26708: Updates to the "Writing your first patch for Django" Documentation Page

[Django]

#26708: Updates to the "Writing your first patch for Django" Documentation Page
--+
 Reporter:  nnja  |Owner:  nnja
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by MarkusH):

 * cc: MarkusH (added)
 * needs_better_patch:  0 => 1
 * 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/062.565b41f5a3e43cd01d7003d8a8758f8b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26708: Updates to the "Writing your first patch for Django" Documentation Page

[Django]

#26708: Updates to the "Writing your first patch for Django" Documentation Page
-+-
 Reporter:  nnja |Owner:  nnja
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by nnja):

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

Re: [Django] #26708: Updates to the "Writing your first patch for Django" Documentation Page

[Django]

#26708: Updates to the "Writing your first patch for Django" Documentation Page
-+-
 Reporter:  nnja |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by nnja):

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


Old description:

> While this section is helpful, it should be updated to reflect a git-
> oriented and not patch-based workflow. Once these changes are made, it
> can also be featured as a 'Quick Start' to contributing section, and
> featured in the 'First Steps' portion of the contribution guide.
>
> The following workflow should be represented in the document:
> 1. Fork the project, Then Clone your fork
> 2. Running Tests (Link To
> https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
> /unit-tests/)
> 3. Create a Branch
> 4. Modify the Code / Documentation
> 5. Diff your changes with Upstream
> 6. Commit - (Link to Coding Style / Commit Guidelines Here)
> 7. Push to your branch
> 8. Create a Pull Request
>
> ** Links to more detailed documentation for the steps above should be
> provided where needed.
>
> Additionally, the following needs to be done:
> - Prominently Link to the Git Workflow, near the top.
> (https://docs.djangoproject.com/en/dev/internals/contributing/writing-
> code/working-with-git/)
> - Change the title to 'Quick Start Guide to Contributing'
> - Remove all References to 'Patch', including in links to this document
> from other places
> - Rewrite the 'So What do I do next Section?'
> -Remove the `Since we never committed our changes locally` section, since
> in the new workflow we *did* commit our changes locally.
> - Add a link to the document under the 'First Steps' section of the
> Contribution Guide

New description:

 While this section is helpful, it should be updated to reflect a git-
 oriented and not patch-based workflow. Once these changes are made, it can
 also be featured as a 'Quick Start' to contributing section, and featured
 in the 'First Steps' portion of the contribution guide.

 The following workflow should be represented in the document:
 1. Fork the project, Then Clone your fork
 2. Running Tests (Link To
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /unit-tests/)
 3. Create a Branch
 4. Modify the Code / Documentation
 5. Diff your changes with Upstream
 6. Commit - (Link to Coding Style / Commit Guidelines Here)
 7. Push to your branch
 8. Create a Pull Request

 ** Links to more detailed documentation for the steps above should be
 provided where needed.

 Additionally, the following needs to be done:
 - Prominently Link to the Git Workflow, near the top.
 (https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /working-with-git/)
 - Change the title to 'Quick Start Guide to Contributing'
 - Remove all References to 'Patch', including in links to this document
 from other places
 - Rewrite the 'So What do I do next Section?'
 -Remove the 'Since we never committed our changes locally' section, since
 in the new workflow we *did* commit our changes locally.
 - Add a link to the document under the 'First Steps' section of the
 Contribution Guide

--

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

Re: [Django] #26708: Updates to the "Writing your first patch for Django" Documentation Page

[Django]

#26708: Updates to the "Writing your first patch for Django" Documentation Page
-+-
 Reporter:  nnja |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by nnja:

Old description:

> While this section is helpful, it should be updated to reflect a git-
> oriented and not patch-based workflow. Once these changes are made, it
> can also be featured as a 'Quick Start' to contributing section, and
> featured in the 'First Steps' portion of the contribution guide.
>
> The following workflow should be represented in the document:
> 1. Fork the project, Then Clone your fork
> 2. Running Tests (Link To
> https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
> /unit-tests/)
> 3. Create a Branch
> 4. Modify the Code / Documentation
> 5. Diff your changes with Upstream
> 6. Commit - (Link to Coding Style / Commit Guidelines Here)
> 7. Push to your branch
> 8. Create a Pull Request
>
> ** Links to more detailed documentation for the steps above should be
> provided where needed.
>
> Additionally, the following needs to be done:
> - Prominently Link to the Git Workflow, near the top.
> (https://docs.djangoproject.com/en/dev/internals/contributing/writing-
> code/working-with-git/)
> - Change the title to 'Quick Start Guide to Contributing'
> - Remove all References to 'Patch', including in links to this document
> from other places
> - Rewrite the 'So What do I do next Section?'
> -Remove the 'Since we never committed our changes locally' section, since
> in the new workflow we *did* commit our changes locally.
> - Add a link to the document under the 'First Steps' section of the
> Contribution Guide

New description:

 While this section is helpful, it should be updated to reflect a git-
 oriented and not patch-based workflow. Once these changes are made, it can
 also be featured as a 'Quick Start' to contributing section, and featured
 in the 'First Steps' portion of the contribution guide.

 The following workflow should be represented in the document:
 1. Fork the project, Then Clone your fork
 2. Running Tests (Link To
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /unit-tests/)
 3. Create a Branch
 4. Modify the Code / Documentation
 5. Diff your changes with Upstream
 6. Commit - (Link to Coding Style / Commit Guidelines Here)
 7. Push to your branch
 8. Create a Pull Request

 ** Links to more detailed documentation for the steps above should be
 provided where needed.

 Additionally, the following needs to be done:
 - Prominently Link to the Git Workflow, near the top.
 (https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /working-with-git/)
 - Change the title to 'Quick Start Guide to Contributing'
 - Remove all References to 'Patch', including in links to this document
 from other places
 - Rewrite the 'So What do I do next Section?'
 - Remove the 'Since we never committed our changes locally' section, since
 in the new workflow we *did* commit our changes locally.
 - Add a link to the document under the 'First Steps' section of the
 Contribution Guide

--

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

[Django] #26708: Updates to the "Writing your first patch for Django" Documentation Page

[Django]

#26708: Updates to the "Writing your first patch for Django" Documentation Page
--+
 Reporter:  nnja  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 While this section is helpful, it should be updated to reflect a git-
 oriented and not patch-based workflow. Once these changes are made, it can
 also be featured as a 'Quick Start' to contributing section, and featured
 in the 'First Steps' portion of the contribution guide.

 The following workflow should be represented in the document:
 1. Fork the project, Then Clone your fork
 2. Running Tests (Link To
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /unit-tests/)
 3. Create a Branch
 4. Modify the Code / Documentation
 5. Diff your changes with Upstream
 6. Commit - (Link to Coding Style / Commit Guidelines Here)
 7. Push to your branch
 8. Create a Pull Request

 ** Links to more detailed documentation for the steps above should be
 provided where needed.

 Additionally, the following needs to be done:
 - Prominently Link to the Git Workflow, near the top.
 (https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /working-with-git/)
 - Change the title to 'Quick Start Guide to Contributing'
 - Remove all References to 'Patch', including in links to this document
 from other places
 - Rewrite the 'So What do I do next Section?'
 -Remove the `Since we never committed our changes locally` section, since
 in the new workflow we *did* commit our changes locally.
 - Add a link to the document under the 'First Steps' section of the
 Contribution Guide

--
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/047.119a64108ecc4cabb3bf379bc964103b%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:  zimnyx   |Owner:  czpython
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by czpython):

 * has_patch:  0 => 1


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

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

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

[Django]

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Yes, a new ticket is more appropriate. #9982 may be related.

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

Re: [Django] #21588: "Modifying upload handlers on the fly" documentation doesn't replicate internal magic

[Django]

#21588: "Modifying upload handlers on the fly" documentation doesn't replicate
internal magic
-+-
 Reporter:  Keryn Knight |Owner:
   |  berkerpeksag
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  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 berkerpeksag):

 * cc: berker.peksag@… (added)
 * owner:  nobody => berkerpeksag
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

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

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

Re: [Django] #24781: lazy() may need a __repr__ for Python 2

[Django]

#24781: lazy() may need a __repr__ for Python 2
---+-
 Reporter:  jdh13  |Owner:  chescales
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:  fixed
 Keywords:  py2| Triage Stage:  Ready for checkin
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ffd18732f3ee9e6f0374aff9ccf350d85187fac2" ffd1873]:
 {{{
 #!CommitTicketReference repository=""
 revision="ffd18732f3ee9e6f0374aff9ccf350d85187fac2"
 Fixed #24781 -- Fixed repr() for lazy objects.
 }}}

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

Re: [Django] #24781: lazy() may need a __repr__ for Python 2

[Django]

#24781: lazy() may need a __repr__ for Python 2
---+-
 Reporter:  jdh13  |Owner:  chescales
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  py2| Triage Stage:  Ready for checkin
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by carljm):

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

Re: [Django] #26028: Improve instructions for overriding Django templates

[Django]

#26028: Improve instructions for overriding Django templates
---+
 Reporter:  pydanny|Owner:  phildini
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.9
 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 phildini):

 * has_patch:  0 => 1


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

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

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

[Django]

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by nbremond):

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


Comment:

 I don't know if I have to reply here, on #26320 or on a new ticket, but
 the solution given by charette on comment:2 does not really work.

 The problem on fields is solved but I think there is still a bug during
 objects instanciation.


 {{{#!python
 #models.py
 from django.db import models

 class Base(models.Model):
 def __str__(self):#indicate if the object is a member of a subclass
 try:
 a=self.a
 return "a A pk="+str(self.pk)+" (other="+str(a.other.pk)+")"
 except A.DoesNotExist:
 pass
 try:
 z=self.z
 return "not a A but a Z pk="+str(self.pk)
 except Z.DoesNotExist:
 pass
 return "not a A neither a Z pk="+str(self.pk)

 class A(Base):
 base_ptr = models.OneToOneField(Base, parent_link=True,
 primary_key=True)
 other = models.OneToOneField(Base, related_name='other_base') #I do
 not have null=True

 class Z(Base):
 pass
 }}}

 I can manipulate the `Z` objects :
 adding a new `Z` :
 {{{#!python
 >>> z=Z()
 >>> z.save()
 >>> Base.objects.all()
 []
 }}}

 if I try to do the same thing with a `A` (with a new database):

 {{{#!python
 >>> other=Base()
 >>> other.save()
 >>> a=A(other=other)
 >>> a.save()
 >>> a
  #a is supposed to have a pk which is not
 None
 >>> a.other
 #other is supposed to be a base and not a A
 >>> Base.objects.all()
 []#I was expecting two objects
 }}}

 It seems to be possible to change a `Base` to a `A`:
 {{{#!python
 >>> other=Base()
 >>> other.save()
 >>> b=Base()
 >>> b.save()
 >>> Base.objects.all()
 [, ]
 >>> a=A(other=other,base_ptr=b)
 >>> a.save()
 >>> a
 #str(a) should return "a A" but this work if
 we reload the object
 >>> a.other
 
 >>> Base.objects.all()
 , ]
 }}}

 This is maybe also deprecated but it can be a bug in the next version and
 I didn't see a fix in [https://github.com/django/django/pull/6490 PR] (I
 quickly look the pull request, maybe I'm wrong)

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

Re: [Django] #18468: Add the ability to define comments in table / columns (was: Define COMMENT in table / colomns)

[Django]

#18468: Add the ability to define comments in table / columns
-+-
 Reporter:  mrechte  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 timgraham):

 * status:  new => closed
 * type:  Uncategorized => New feature
 * resolution:   => duplicate


Comment:

 The correct way to reopen a ticket closed as "wontfix" is to start a
 discussion on the DevelopersMailingList. If there is consensus there to
 add the feature, then we reopen the ticket.

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

Re: [Django] #19963: Add support for date_hierarchy across relations

[Django]

#19963: Add support for date_hierarchy across relations
---+
 Reporter:  jbg@…  |Owner:  vytisb
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  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:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2f9c4e2b6fab3ce08cfbebff79d758196250790c" 2f9c4e2b]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f9c4e2b6fab3ce08cfbebff79d758196250790c"
 Fixed #19963 -- Added support for date_hierarchy across relations.
 }}}

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

Re: [Django] #18468: Define COMMENT in table / colomns

[Django]

#18468: Define COMMENT in table / colomns
-+-
 Reporter:  mrechte  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 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 mrechte):

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


Comment:

 Now that migration is built in Django, which can be used to create and
 administer the database, I again request this feature to be added. Thanks.

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

Re: [Django] #25127: document how to define models in multiple modules

[Django]

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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:"101f99977688530d5821c8129f626da68025d211" 101f999]:
 {{{
 #!CommitTicketReference repository=""
 revision="101f99977688530d5821c8129f626da68025d211"
 [1.10.x] Fixed #25127 -- Documented how to organize models in a package.

 Backport of 84d8d1d7151a4ee70ae35037d37f76a40d18da64 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/064.57ca7230eabf18c671a10b0409a9f537%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25127: document how to define models in multiple modules

[Django]

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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:"aa1bdc07a9f048e8b7b0734b41f879b4027742d9" aa1bdc07]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa1bdc07a9f048e8b7b0734b41f879b4027742d9"
 [1.9.x] Fixed #25127 -- Documented how to organize models in a package.

 Backport of 84d8d1d7151a4ee70ae35037d37f76a40d18da64 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/064.647a3854c4a52f0983e2a7738025190f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25127: document how to define models in multiple modules

[Django]

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 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
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"84d8d1d7151a4ee70ae35037d37f76a40d18da64" 84d8d1d7]:
 {{{
 #!CommitTicketReference repository=""
 revision="84d8d1d7151a4ee70ae35037d37f76a40d18da64"
 Fixed #25127 -- Documented how to organize models in a package.
 }}}

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

Re: [Django] #26707: Add a QueryDict.fromkeys() method (was: QueryDict.fromkeys fails in mysterious ways)

[Django]

#26707: Add a QueryDict.fromkeys() method
-+-
 Reporter:  wimglenn |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  http querydict   | 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 timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, pending a few cosmetic updates noted on the PR.

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

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

Re: [Django] #26703: field automatically choosen as primary_key (primary_key=False do not work)

[Django]

#26703: field automatically choosen as primary_key (primary_key=False do not 
work)
-+-
 Reporter:  nbremond |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  multi-table  | Triage Stage:
  inheritance, primary_key,  |  Unreviewed
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by nbremond):

 Yes, this is a duplicate of #26320, sorry…
 Thanks for the 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 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.69d7b12bc07d5df31fee92ca977fa7b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26628: Log CSRF failures to django.security instead of django.request

[Django]

#26628: Log CSRF failures to django.security instead of django.request
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  closed
Component:  CSRF  |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"55fec16aafed30a9daa06d6ecdf8ca3ad361279e" 55fec16a]:
 {{{
 #!CommitTicketReference repository=""
 revision="55fec16aafed30a9daa06d6ecdf8ca3ad361279e"
 Fixed #26628 -- Changed CSRF logger to django.security.csrf.
 }}}

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

Re: [Django] #12666: Setting for sending email using localtime instead of UTC

[Django]

#12666: Setting for sending email using localtime instead of UTC
-+
 Reporter:  net147   |Owner:  aisipos
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:  1.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"c3495bb984a6f639e828e568fd333e36b46f270f" c3495bb9]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3495bb984a6f639e828e568fd333e36b46f270f"
 Fixed #12666 -- Added EMAIL_USE_LOCALTIME setting.

 When EMAIL_USE_LOCALTIME=True, send emails with a Date header
 in the local time zone.
 }}}

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

Re: [Django] #26643: AlterModelManagers migration is generated for all Models with custom Managers pointing to the default Django Manager

[Django]

#26643: AlterModelManagers migration is generated for all Models with custom
Managers pointing to the default Django Manager
-+-
 Reporter:  cybojenix|Owner:  schinckel
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  1.10 | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by schinckel):

 * owner:  nobody => schinckel
 * status:  new => assigned
 * needs_tests:  0 => 1


Comment:

 Okay, I have a patch, but no tests:
 
https://github.com/schinckel/django/commit/38a0cb2a9bfb4752b661905a2de6278fed9771dd

 Should I be creating a PR against 1.10.x, or 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/067.95ee09bb3cf58642b6acd11dae378363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26643: AlterModelManagers migration is generated for all Models with custom Managers pointing to the default Django Manager

[Django]

#26643: AlterModelManagers migration is generated for all Models with custom
Managers pointing to the default Django Manager
-+
 Reporter:  cybojenix|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  1.10 | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by schinckel):

 Replying to [comment:8 schinckel]:
 > I believe reinstating the code at
 
https://github.com/django/django/commit/ed0ff913c648b16c4471fc9a9441d1ee48cb5420
 #diff-c8a3e1d248f8f5b10af7ac5b1d8479f4L516 is sufficient to fix this bug.

 Ah, not quite. This causes a deprecation warning in the manager
 inheritance stuff.

 Perhaps the check could be included in the autodetector, instead of the
 ModelState.

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

Re: [Django] #26643: AlterModelManagers migration is generated for all Models with custom Managers pointing to the default Django Manager

[Django]

#26643: AlterModelManagers migration is generated for all Models with custom
Managers pointing to the default Django Manager
-+
 Reporter:  cybojenix|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  1.10 | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by schinckel):

 I believe reinstating the code at
 
https://github.com/django/django/commit/ed0ff913c648b16c4471fc9a9441d1ee48cb5420
 #diff-c8a3e1d248f8f5b10af7ac5b1d8479f4L516 is sufficient to fix this 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 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.54468fe9b0e92915233904dbd7aa75d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

[Django]

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  OneToOneField| Triage Stage:  Accepted
  to_field primary_key   |
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:"8996054cb4b3cfb88ee4d8896fa53424440a2564" 8996054]:
 {{{
 #!CommitTicketReference repository=""
 revision="8996054cb4b3cfb88ee4d8896fa53424440a2564"
 [1.10.x] Fixed #26667 -- Fixed a regression in queries on a OneToOneField
 that has to_field and primary_key=True.

 Thanks Simon Charette for review.

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

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

[Django]

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  OneToOneField| Triage Stage:  Accepted
  to_field primary_key   |
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:"d5d8d35e501ca72e1abf801620e321bc6972f639" d5d8d35e]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5d8d35e501ca72e1abf801620e321bc6972f639"
 [1.9.x] Fixed #26667 -- Fixed a regression in queries on a OneToOneField
 that has to_field and primary_key=True.

 Thanks Simon Charette for review.

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

Re: [Django] #26667: Invalid query for OneToOneField if 'to_field' specified and primary_key=True

[Django]

#26667: Invalid query for OneToOneField if 'to_field'  specified and
primary_key=True
-+-
 Reporter:  kwist|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  OneToOneField| Triage Stage:  Accepted
  to_field primary_key   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e2296e7f0acf9c50868ab997ba565c1f47beb45b" e2296e7f]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2296e7f0acf9c50868ab997ba565c1f47beb45b"
 Fixed #26667 -- Fixed a regression in queries on a OneToOneField that has
 to_field and primary_key=True.

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

Re: [Django] #26628: Log CSRF failures to django.security instead of django.request

[Django]

#26628: Log CSRF failures to django.security instead of django.request
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  CSRF  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #25127: document how to define models in multiple modules

[Django]

#25127: document how to define models in multiple modules
--+
 Reporter:  keturn|Owner:  palmerev
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 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 timgraham):

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

Re: [Django] #26705: DjangoTranslation instance has no attribute 'plural'

[Django]

#26705: DjangoTranslation instance has no attribute 'plural'
--+
 Reporter:  theju |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  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 theju):

 * has_patch:  0 => 1


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

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

Re: [Django] #26705: DjangoTranslation instance has no attribute 'plural'

[Django]

#26705: DjangoTranslation instance has no attribute 'plural'
--+
 Reporter:  theju |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  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 theju):

 A patch along with test is available at
 https://github.com/theju/django/tree/ticket_26705
 I have also attached a pull request at
 https://github.com/django/django/pull/6717

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

Re: [Django] #26707: QueryDict.fromkeys fails in mysterious ways

[Django]

#26707: QueryDict.fromkeys fails in mysterious ways
+
 Reporter:  wimglenn|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  HTTP handling   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  http querydict  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by phildini):

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