Re: [Django] #19323: Add django.contrib.redirects setting for turning redirect on/off.

#19323: Add django.contrib.redirects setting for turning redirect on/off. -+- Reporter: Melevir |Owner: Melevir Type: New feature | Status: new

Re: [Django] #18920: Regresssiontests.template tests fail on windows due to expected '\n'

#18920: Regresssiontests.template tests fail on windows due to expected '\n' ---+ Reporter: manfre |Owner: nobody Type: Bug| Status: closed

[django/django] 47a65a: [1.6.x] Force Unix-style line-endings for some hel...

Branch: refs/heads/stable/1.6.x Home: https://github.com/django/django Commit: 47a65ad40e6b6ee282a46473977b774837950961 https://github.com/django/django/commit/47a65ad40e6b6ee282a46473977b774837950961 Author: Ramiro Morales Date: 2013-09-30 (Mon, 30 Sep

[django/django] 437271: Force Unix-style line-endings for some helper file...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 4372718e839d15c707d50cc78274a355258cf36a https://github.com/django/django/commit/4372718e839d15c707d50cc78274a355258cf36a Author: Ramiro Morales Date: 2013-09-30 (Mon, 30 Sep 2013)

Re: [Django] #18920: Regresssiontests.template tests fail on windows due to expected '\n'

#18920: Regresssiontests.template tests fail on windows due to expected '\n' ---+ Reporter: manfre |Owner: nobody Type: Bug| Status: closed

Re: [Django] #21096: Allow setting of 'distance' attribute name

#21096: Allow setting of 'distance' attribute name -+ Reporter: simon29 |Owner: nobody Type: New feature | Status: closed Component: GIS |

Re: [Django] #21096: Allow setting of 'distance' attribute name

#21096: Allow setting of 'distance' attribute name -+ Reporter: simon29 |Owner: nobody Type: New feature | Status: new Component: GIS |

[django/django] d9bbda: * Fixing improper grammar

Branch: refs/heads/master Home: https://github.com/django/django Commit: d9bbda7149416ae72a6e5489d0095a3f25b97793 https://github.com/django/django/commit/d9bbda7149416ae72a6e5489d0095a3f25b97793 Author: Adam Haney Date: 2013-09-30 (Mon, 30 Sep 2013)

[Django] #21203: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment when using defer and select_related

#21203: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment when using defer and select_related --+ Reporter: manfre| Owner: nobody

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

#5793: Allow custom attributes in Meta classes -+ Reporter: eikke@… |Owner: nobody Type: New feature | Status: new Component: Metasystem | Version:

Re: [Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

#21202: Atomic masks fatal database errors and instead propagates "connection already closed" -+- Reporter: intgr|Owner: aaugustin Type: |

[Django] #21202: Atomic masks fatal database errors and instead propagates "connection already closed"

#21202: Atomic masks fatal database errors and instead propagates "connection already closed" --+ Reporter: intgr | Owner: nobody Type: Uncategorized | Status: new

[django/django] d847dd: Fixed #3871 -- Fixed regression introduced by 04a2...

Branch: refs/heads/master Home: https://github.com/django/django Commit: d847ddfe1d4475e768c547b17642d3ed0894d54e https://github.com/django/django/commit/d847ddfe1d4475e768c547b17642d3ed0894d54e Author: Loic Bistuer Date: 2013-09-30 (Mon, 30 Sep

Re: [Django] #3871: Use custom managers in reverse relations

#3871: Use custom managers in reverse relations -+- Reporter: EspenG |Owner: v1v3kn Type: New feature | Status: closed Component: Database

[django/django] 4745ea: Added hints argument to GeoQuerySet; refs #13724.

Branch: refs/heads/master Home: https://github.com/django/django Commit: 4745ea1d27a154a44ed2cacb66b01d5de1f9e3d3 https://github.com/django/django/commit/4745ea1d27a154a44ed2cacb66b01d5de1f9e3d3 Author: Tim Graham Date: 2013-09-30 (Mon, 30 Sep 2013)

Re: [Django] #13724: Calling QuerySet.delete() through a relation the DB router is ignored.

#13724: Calling QuerySet.delete() through a relation the DB router is ignored. -+- Reporter: Chris Targett|Owner: | paulcollins Type: Bug

Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors

#20752: Error signals are not reliable, especially when dealing with database errors -+- Reporter: tal@…|Owner: nobody Type: Bug | Status:

[django/django] 2004f8: Add myself to authors file

Branch: refs/heads/master Home: https://github.com/django/django Commit: 2004f86b858b809101c8cc442383ac90756e306e https://github.com/django/django/commit/2004f86b858b809101c8cc442383ac90756e306e Author: Dan Johnson Date: 2013-09-30 (Mon, 30 Sep 2013)

Re: [Django] #21096: Allow setting of 'distance' attribute name

#21096: Allow setting of 'distance' attribute name -+ Reporter: simon29 |Owner: nobody Type: New feature | Status: new Component: GIS |

[Django] #21201: Let ClearableFileInput work with other fields

#21201: Let ClearableFileInput work with other fields -+ Reporter: vzima| Owner: nobody Type: New feature | Status: new Component: Forms|Version: master Severity: Normal | Keywords:

Re: [Django] #21200: Inconsistent handling of "PickleError" between cache backends

#21200: Inconsistent handling of "PickleError" between cache backends -+ Reporter: t.chaumeny@… |Owner: nobody Type: Bug | Status: new

Re: [Django] #21200: Inconsistent handling of "PickleError" between cache backends

#21200: Inconsistent handling of "PickleError" between cache backends -+ Reporter: t.chaumeny@… |Owner: nobody Type: Bug | Status: new

[django/django] f93896: Fixed Python 3.2 syntax errors; refs #13724.

Branch: refs/heads/master Home: https://github.com/django/django Commit: f93896344abfdfd288e0d8249b37e2b799fd7d53 https://github.com/django/django/commit/f93896344abfdfd288e0d8249b37e2b799fd7d53 Author: Tim Graham Date: 2013-09-30 (Mon, 30 Sep 2013)

Re: [Django] #13724: Calling QuerySet.delete() through a relation the DB router is ignored.

#13724: Calling QuerySet.delete() through a relation the DB router is ignored. -+- Reporter: Chris Targett|Owner: | paulcollins Type: Bug

[django/django] 98773c: [1.6.x] Fixed #21154 -- Updated TemplateResponse d...

Branch: refs/heads/stable/1.6.x Home: https://github.com/django/django Commit: 98773c4bb53ff464c3782694f244e80158f975ee https://github.com/django/django/commit/98773c4bb53ff464c3782694f244e80158f975ee Author: Curtis Maloney Date: 2013-09-30 (Mon, 30 Sep

[django/django] 20f394: [1.5.x] Fixed #21154 -- Updated TemplateResponse d...

Branch: refs/heads/stable/1.5.x Home: https://github.com/django/django Commit: 20f394f4d5a5e0b4647aac2dd7b5ab8dc89d36fa https://github.com/django/django/commit/20f394f4d5a5e0b4647aac2dd7b5ab8dc89d36fa Author: Curtis Maloney Date: 2013-09-30 (Mon, 30 Sep

Re: [Django] #21154: `TemplateResponse` does not convert `Context` to `RequestContext`.

#21154: `TemplateResponse` does not convert `Context` to `RequestContext`. -+- Reporter: mrmachine|Owner: nobody Type: Bug | Status: closed

Re: [Django] #21154: `TemplateResponse` does not convert `Context` to `RequestContext`.

#21154: `TemplateResponse` does not convert `Context` to `RequestContext`. -+- Reporter: mrmachine|Owner: nobody Type: Bug | Status: closed

[Django] #21200: Inconsistent handling of "PickleError" between cache backends

#21200: Inconsistent handling of "PickleError" between cache backends -+ Reporter: t.chaumeny@… | Owner: nobody Type: Uncategorized| Status: new Component: Core (Cache system) |Version:

[django/django] c39c9f: Fixed #21154 -- Updated TemplateResponse docs to b...

Branch: refs/heads/master Home: https://github.com/django/django Commit: c39c9f2ad8b2670d53ef845face67c29f3f4be3b https://github.com/django/django/commit/c39c9f2ad8b2670d53ef845face67c29f3f4be3b Author: Curtis Maloney Date: 2013-09-30 (Mon, 30 Sep 2013)

Re: [Django] #21154: `TemplateResponse` does not convert `Context` to `RequestContext`.

#21154: `TemplateResponse` does not convert `Context` to `RequestContext`. -+- Reporter: mrmachine|Owner: nobody Type: Bug | Status: closed

Re: [Django] #21198: @python_2_unicode_compatible, abstract models, working on 1.4 but causing infinite loop on 1.5.

#21198: @python_2_unicode_compatible, abstract models, working on 1.4 but causing infinite loop on 1.5. ---+ Reporter: jpic |Owner: nobody Type: Bug| Status: new

Re: [Django] #21195: Clarify the usage of template_name in tutorial part 4 (was: Mis-typing in description of tutorial 04)

#21195: Clarify the usage of template_name in tutorial part 4 --+ Reporter: anonymous |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #21111: generic.View.__init__ should call super

#2: generic.View.__init__ should call super --+ Reporter: glin@…|Owner: gmeno Type: Cleanup/optimization | Status: assigned Component: Generic

Re: [Django] #21199: Backends tests trigger PendingDeprecationWarning

#21199: Backends tests trigger PendingDeprecationWarning -+- Reporter: erikr|Owner: nobody Type: | Status: closed

Re: [Django] #21154: `TemplateResponse` does not convert `Context` to `RequestContext`.

#21154: `TemplateResponse` does not convert `Context` to `RequestContext`. -+- Reporter: mrmachine|Owner: nobody Type: Bug | Status: new

Re: [Django] #21199: Backends tests trigger PendingDeprecationWarning

#21199: Backends tests trigger PendingDeprecationWarning -+- Reporter: erikr|Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #21199: Backends tests trigger PendingDeprecationWarning

#21199: Backends tests trigger PendingDeprecationWarning --+ Reporter: erikr | Owner: nobody Type: Cleanup/optimization | Status: new Component: Database layer (models,

Re: [Django] #21154: `TemplateResponse` does not convert `Context` to `RequestContext`.

#21154: `TemplateResponse` does not convert `Context` to `RequestContext`. -+- Reporter: mrmachine|Owner: nobody Type: Bug | Status: new

Re: [Django] #21198: @python_2_unicode_compatible, abstract models, working on 1.4 but causing infinite loop on 1.5.

#21198: @python_2_unicode_compatible, abstract models, working on 1.4 but causing infinite loop on 1.5. ---+ Reporter: jpic |Owner: nobody Type: Bug| Status: new

[Django] #21198: @python_2_unicode_compatible, abstract models, working on 1.4 but causing infinite loop on 1.5.

#21198: @python_2_unicode_compatible, abstract models, working on 1.4 but causing infinite loop on 1.5. ---+ Reporter: jpic | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

#21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER -+- Reporter: russellm |Owner: nobody Type: Bug | Status: new

Re: [Django] #19182: ModelAdmin.lookup_allowed should also check for ('fieldname', ClassName) syntax

#19182: ModelAdmin.lookup_allowed should also check for ('fieldname', ClassName) syntax -+- Reporter: gauss|Owner: nobody Type: Bug |

[Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

#21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER -+- Reporter: russellm | Owner: nobody Type: Bug| Status: new Component:

[django/django] 0d74bd: Fixed #21134 -- Prevented queries in broken transa...

Branch: refs/heads/stable/1.6.x Home: https://github.com/django/django Commit: 0d74bdaf0c39feb8ec303dbbdbcadba70e46eecb https://github.com/django/django/commit/0d74bdaf0c39feb8ec303dbbdbcadba70e46eecb Author: Aymeric Augustin Date: 2013-09-30 (Mon,

Re: [Django] #21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors

#21134: Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors -+- Reporter: RichardOfWard|Owner: aaugustin Type: |

[Django] #21196: Warning when running the test suite under MySQL

#21196: Warning when running the test suite under MySQL -+ Reporter: aaugustin | Owner: nobody Type: Bug| Status: new Component: contrib.admin |

[Django] #21195: Mis-typing in description of tutorial 04

#21195: Mis-typing in description of tutorial 04 ---+-- Reporter: anonymous | Owner: nobody Type: Uncategorized | Status: new Component: Documentation |Version: 1.5 Severity: Normal |

[django/django] 728548: Fixed #21134 -- Prevented queries in broken transa...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 728548e483a5a3486939b0c8e62520296587482e https://github.com/django/django/commit/728548e483a5a3486939b0c8e62520296587482e Author: Aymeric Augustin Date: 2013-09-30 (Mon, 30 Sep

Re: [Django] #21111: generic.View.__init__ should call super

#2: generic.View.__init__ should call super --+ Reporter: glin@…|Owner: gmeno Type: Cleanup/optimization | Status: assigned Component: Generic

Re: [Django] #21181: collation specific query results ordering

#21181: collation specific query results ordering -+- Reporter: alan.kesselmann@…|Owner: nobody Type: New feature | Status: new Component: Database

Re: [Django] #21164: get_user_model() does not handle custom user models for testing purposes

#21164: get_user_model() does not handle custom user models for testing purposes ---+--- Reporter: raymond.penners@… |Owner: nobody Type: Bug| Status: new