[Django] #25649: document that all GEOSGeometries take `srid` kwarg

#25649: document that all GEOSGeometries take `srid` kwarg --+ Reporter: sir-sigurd| Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |Version: 1.8 S

[Django] #25648: Unable to modify or delete unique_together Model constraint (PostgreSQL)

#25648: Unable to modify or delete unique_together Model constraint (PostgreSQL) ---+ Reporter: MasterKale | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.8 Severit

Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

#25550: Deprecate direct assignment to the reverse side of a related set -+- Reporter: timgraham|Owner: nobody Type: | Status: closed Cl

Re: [Django] #25619: Since Django ~1.6.4 the dev runserver uses http_version 1.0, before it was 1.1

#25619: Since Django ~1.6.4 the dev runserver uses http_version 1.0, before it was 1.1 ---+ Reporter: gabn88 |Owner: nobody Type: Bug| Status: new Compone

Re: [Django] #25647: Regression with TEST MIRROR database migrations

#25647: Regression with TEST MIRROR database migrations ---+-- Reporter: gavinwahl |Owner: nobody Type: Bug| Status: new Component: Testing frame

Re: [Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+--- Reporter: rollokb|Owner: raphaelmerx Type: Bug| Status: assigned Compon

Re: [Django] #25647: Regression with TEST MIRROR database migrations

#25647: Regression with TEST MIRROR database migrations ---+-- Reporter: gavinwahl |Owner: nobody Type: Bug| Status: new Component: Testing frame

[Django] #25647: Regression with TEST MIRROR database migrations

#25647: Regression with TEST MIRROR database migrations ---+ Reporter: gavinwahl | Owner: nobody Type: Bug| Status: new Component: Testing framework |Version: 1.8 Severity: Norma

Re: [Django] #25169: Document "stacking" of login_required and permission_required

#25169: Document "stacking" of login_required and permission_required --+ Reporter: aithusa |Owner: bxm156 Type: Cleanup/optimization | Status: assigned

Re: [Django] #23751: Code snippets display without formatting in PDF version of the docs

#23751: Code snippets display without formatting in PDF version of the docs + Reporter: adam-glodowski |Owner: nobody Type: Bug | Status: new Component: Docu

Re: [Django] #25646: Sort the `local vars` in the rich exception reporter

#25646: Sort the `local vars` in the rich exception reporter -+-- Reporter: kezabelle|Owner: Type: New feature | Status: new Component: Error reporting |

[Django] #25646: Sort the `local vars` in the rich exception reporter

#25646: Sort the `local vars` in the rich exception reporter -+ Reporter: kezabelle| Owner: Type: New feature | Status: new Component: Error reporting |Version: master Severity: Normal

Re: [Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+ Reporter: rollokb|Owner: nobody Type: Bug| Status: new Component: HTTP ha

Re: [Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+ Reporter: rollokb|Owner: nobody Type: Bug| Status: new Component: HTTP ha

Re: [Django] #18937: Use modern Python packaging metadata standard (1.2, PEP 345)

#18937: Use modern Python packaging metadata standard (1.2, PEP 345) -+ Reporter: mjtamlyn |Owner: nobody Type: New feature | Status: new Component: Packaging|

Re: [Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+ Reporter: rollokb|Owner: nobody Type: Bug| Status: new Component: HTTP ha

Re: [Django] #23918: Built in functions override custom functions in related manager

#23918: Built in functions override custom functions in related manager --+ Reporter: dracos|Owner: nobody Type: Cleanup/optimization | Status: closed

Re: [Django] #25636: drop support for SpatiaLite < 3.0

#25636: drop support for SpatiaLite < 3.0 -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status

[Django] #25645: Drop support for SpatiaLite < 4.0

#25645: Drop support for SpatiaLite < 4.0 + Reporter: timgraham | Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS

Re: [Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+ Reporter: rollokb|Owner: nobody Type: Bug| Status: new Component: HTTP ha

Re: [Django] #25638: update using Concat with Value causes error-encoding in SQLite

#25638: update using Concat with Value causes error-encoding in SQLite -+- Reporter: bearxu83 |Owner: nobody Type: Bug | Status: new Compo

Re: [Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+-- Reporter: rollokb|Owner: nobody Type: Bug| Status: new Component: HTTP

Re: [Django] #25638: update using Concat with Value causes error-encoding in SQLite

#25638: update using Concat with Value causes error-encoding in SQLite -+- Reporter: bearxu83 |Owner: nobody Type: Bug | Status: new Compo

[Django] #25644: Setting a cookie after deletion should not keep 1970 as expiry date

#25644: Setting a cookie after deletion should not keep 1970 as expiry date ---+-- Reporter: rollokb| Owner: nobody Type: Uncategorized | Status: new Component: HTTP handling |Version: 1.8 Severi

Re: [Django] #25642: creating a model named "order" cause sqlite database to crash

#25642: creating a model named "order" cause sqlite database to crash +-- Reporter: spoutnik16 |Owner: nobody Type: Bug | Status: closed Component: Migrations |

Re: [Django] #25638: update using Concat with Value causes error-encoding in SQLite

#25638: update using Concat with Value causes error-encoding in SQLite -+- Reporter: bearxu83 |Owner: nobody Type: Bug | Status: new Compo

Re: [Django] #24212: Documentation for pylibmc cache backend needs additional info

#24212: Documentation for pylibmc cache backend needs additional info ---+ Reporter: jb0t |Owner: bxm156 Type: Bug| Status: closed Component: Documentat

Re: [Django] #24212: Documentation for pylibmc cache backend needs additional info

#24212: Documentation for pylibmc cache backend needs additional info ---+ Reporter: jb0t |Owner: bxm156 Type: Bug| Status: closed Component: Documentat

Re: [Django] #24212: Documentation for pylibmc cache backend needs additional info

#24212: Documentation for pylibmc cache backend needs additional info ---+ Reporter: jb0t |Owner: bxm156 Type: Bug| Status: closed Component: Documentat

Re: [Django] #25636: drop support for SpatiaLite < 3.0

#25636: drop support for SpatiaLite < 3.0 -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status

Re: [Django] #25169: Document "stacking" of login_required and permission_required

#25169: Document "stacking" of login_required and permission_required --+ Reporter: aithusa |Owner: bxm156 Type: Cleanup/optimization | Status: assigned

Re: [Django] #25639: Cascade deleting cause deadlock

#25639: Cascade deleting cause deadlock -+- Reporter: shellfly |Owner: shellfly Type: Bug | Status: assigned Component: Database layer

Re: [Django] #25634: runserver reloader masks exceptions (was: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9)

#25634: runserver reloader masks exceptions -+- Reporter: wide-awake |Owner: nobody Type: Bug | Status: new Component: Core (Management

Re: [Django] #24499: Drop support for PostGIS 1.5

#24499: Drop support for PostGIS 1.5 -+- Reporter: timgraham|Owner: timgraham Type: | Status: closed Cleanup/optimization

Re: [Django] #24499: Drop support for PostGIS 1.5

#24499: Drop support for PostGIS 1.5 -+- Reporter: timgraham|Owner: timgraham Type: | Status: closed Cleanup/optimization

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9 -+- Reporter: wide-awake |Owner: nobody Type: Bug | Status: new Component

[Django] #25643: Extend expressions API to update()

#25643: Extend expressions API to update() --+ Reporter: jorgecarleitao| Owner: nobody Type: New feature | Status: new Component: Database layer (models, ORM) |Vers

Re: [Django] #10870: Aggregates with joins ignore extra filters provided by setup_joins

#10870: Aggregates with joins ignore extra filters provided by setup_joins -+- Reporter: fas |Owner: fas Type: Bug | Status: closed C

Re: [Django] #10870: Aggregates with joins ignore extra filters provided by setup_joins

#10870: Aggregates with joins ignore extra filters provided by setup_joins -+- Reporter: fas |Owner: fas Type: Bug | Status: closed C

Re: [Django] #10870: Aggregates with joins ignore extra filters provided by setup_joins

#10870: Aggregates with joins ignore extra filters provided by setup_joins -+- Reporter: fas |Owner: fas Type: Bug | Status: closed C

Re: [Django] #24019: Docs inaccurately claim aggregation doesn't work with GenericRelation

#24019: Docs inaccurately claim aggregation doesn't work with GenericRelation ---+ Reporter: shaib |Owner: nobody Type: Bug| Status: closed Component: Do

Re: [Django] #24019: Docs inaccurately claim aggregation doesn't work with GenericRelation

#24019: Docs inaccurately claim aggregation doesn't work with GenericRelation ---+ Reporter: shaib |Owner: nobody Type: Bug| Status: closed Component: Do

Re: [Django] #24019: Docs inaccurately claim aggregation doesn't work with GenericRelation

#24019: Docs inaccurately claim aggregation doesn't work with GenericRelation ---+ Reporter: shaib |Owner: nobody Type: Bug| Status: closed Component: Do

Re: [Django] #25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7)

#25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7) -+- Reporter: sachinvettithanam|Owner: nobody Type:

Re: [Django] #25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7)

#25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7) -+- Reporter: sachinvettithanam|Owner: nobody Type:

Re: [Django] #25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7)

#25100: Document how to avoid ""RuntimeError: Error creating new content types." when upgrading to 1.8 (skipping 1.7) -+- Reporter: sachinvettithanam|Owner: nobody Type:

Re: [Django] #21422: prefetch_related does not document restriction of requiring homogeneous results

#21422: prefetch_related does not document restriction of requiring homogeneous results -+- Reporter: pab@…|Owner: Tim Type: | Graham Cleanup/optimiz

Re: [Django] #21422: prefetch_related does not document restriction of requiring homogeneous results

#21422: prefetch_related does not document restriction of requiring homogeneous results -+- Reporter: pab@…|Owner: Tim Type: | Graham Cleanup/optimiz

Re: [Django] #21422: prefetch_related does not document restriction of requiring homogeneous results

#21422: prefetch_related does not document restriction of requiring homogeneous results -+- Reporter: pab@…|Owner: Tim Type: | Graham Cleanup/optimiz

Re: [Django] #21422: prefetch_related does not document restriction of requiring homogeneous results (was: prefetch_related does not document restriction)

#21422: prefetch_related does not document restriction of requiring homogeneous results -+- Reporter: pab@…|Owner: Type: | Status: new

Re: [Django] #25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9

#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9 -+- Reporter: wide-awake |Owner: nobody Type: Bug | Status: new Component

Re: [Django] #25636: drop support for SpatiaLite < 3.0

#25636: drop support for SpatiaLite < 3.0 -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status

[Django] #25642: creating a model named "order" cause sqlite database to crash

#25642: creating a model named "order" cause sqlite database to crash + Reporter: spoutnik16 | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.8 Severity: Normal | Key

Re: [Django] #25642: creating a model named "order" cause sqlite database to crash

#25642: creating a model named "order" cause sqlite database to crash +-- Reporter: spoutnik16 |Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #25641: section about adding Google projection to spatial_ref_sys table should be removed

#25641: section about adding Google projection to spatial_ref_sys table should be removed --+ Reporter: sir-sigurd|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25641: section about adding Google projection to spatial_ref_sys table should be removed

#25641: section about adding Google projection to spatial_ref_sys table should be removed --+ Reporter: sir-sigurd|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25641: section about adding Google projection to spatial_ref_sys table should be removed

#25641: section about adding Google projection to spatial_ref_sys table should be removed --+ Reporter: sir-sigurd|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25641: section about adding Google projection to spatial_ref_sys table should be removed

#25641: section about adding Google projection to spatial_ref_sys table should be removed --+ Reporter: sir-sigurd|Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25641: section about adding Google projection to spatial_ref_sys table should be removed

#25641: section about adding Google projection to spatial_ref_sys table should be removed -+- Reporter: sir-sigurd |Owner: nobody Type: | St

[Django] #25641: section about adding Google projection to spatial_ref_sys table should be removed

#25641: section about adding Google projection to spatial_ref_sys table should be removed --+ Reporter: sir-sigurd| Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation

Re: [Django] #25636: drop support for SpatiaLite < 3.0

#25636: drop support for SpatiaLite < 3.0 -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status

Re: [Django] #25640: language error [IMPORTANT: cannot render templates]-- fixed -- please patch Django 1.8

#25640: language error [IMPORTANT: cannot render templates]-- fixed -- please patch Django 1.8 -+- Reporter: literati |Owner: Dan Type: Bug |

Re: [Django] #21422: prefetch_related does not document restriction

#21422: prefetch_related does not document restriction -+- Reporter: pab@…|Owner: Type: | Status: new Cleanup/optimization

Re: [Django] #24212: Documentation for pylibmc cache backend needs additional info

#24212: Documentation for pylibmc cache backend needs additional info ---+ Reporter: jb0t |Owner: bxm156 Type: Bug| Status: assigned Component: Document

Re: [Django] #25636: drop support for SpatiaLite < 3.0

#25636: drop support for SpatiaLite < 3.0 -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status

Re: [Django] #24212: Documentation for pylibmc cache backend needs additional info

#24212: Documentation for pylibmc cache backend needs additional info ---+ Reporter: jb0t |Owner: bxm156 Type: Bug| Status: assigned Component: Document