Re: [Django] #24109: Provide a way to mark a migration operation as elidable when squashing

2016-01-11 Thread Django
#24109: Provide a way to mark a migration operation as elidable when squashing -+- Reporter: carljm |Owner: charettes Type: New feature | Status: assigned Component: M

[Django] #26072: Errno 10053 occured when use login_required view with ajax

2016-01-11 Thread Django
#26072: Errno 10053 occured when use login_required view with ajax ---+ Reporter: JunLuo | Owner: nobody Type: Uncategorized | Status: new Component: contrib.auth |Version: 1.8 Severity: Normal

Re: [Django] #23868: dumpdata options documentation isn't correctly formatted for some options

2016-01-11 Thread Django
#23868: dumpdata options documentation isn't correctly formatted for some options -+- Reporter: kezabelle|Owner: timgraham Type: | Status:

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #25697: Default error views shouldn't silence TemplateDoesNotExist errors if a custom template name was specified

2016-01-11 Thread Django
#25697: Default error views shouldn't silence TemplateDoesNotExist errors if a custom template name was specified --+ Reporter: charettes |Owner: yakky Type: Cleanup/optimization

Re: [Django] #25788: Enable the cached template loader when DEBUG=False if no loaders are explicitly configured (was: Enabling the cached template loader should be easier)

2016-01-11 Thread Django
#25788: Enable the cached template loader when DEBUG=False if no loaders are explicitly configured -+ Reporter: jaap3|Owner: nobody Type: New feature | Status:

Re: [Django] #24116: Refactor AdminSite.check_dependencies with the checks framework

2016-01-11 Thread Django
#24116: Refactor AdminSite.check_dependencies with the checks framework -+- Reporter: aaugustin|Owner: Type: | vincepandolfo Cleanup/optimization

Re: [Django] #26068: Django 1.8: KEY constraint for parent model missing in m2m [regression]

2016-01-11 Thread Django
#26068: Django 1.8: KEY constraint for parent model missing in m2m [regression] -+- Reporter: direx|Owner: nobody Type: Bug | Status: clos

Re: [Django] #20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints

2016-01-11 Thread Django
#20581: Support DEFERRABLE INITIALLY DEFERRED for UNIQUE constraints -+- Reporter: dmadeley@… |Owner: nobody Type: New feature | Status: new Compone

Re: [Django] #25858: Deriving from abstract model with foreign key to model in same app broken on Django 1.9

2016-01-11 Thread Django
#25858: Deriving from abstract model with foreign key to model in same app broken on Django 1.9 -+- Reporter: kaedroho |Owner: charettes Type: Bug |

Re: [Django] #26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions.

2016-01-11 Thread Django
#26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions. -+- Reporter: timgraham|Owner: timgraham Type: | S

Re: [Django] #494: Collapse in admin interface for inline related objects

2016-01-11 Thread Django
#494: Collapse in admin interface for inline related objects -+- Reporter: jcstover@… |Owner: Tim | Graham Type: New feature |

Re: [Django] #26071: IN queries inside conditional case expressions crashes on django 1.8

2016-01-11 Thread Django
#26071: IN queries inside conditional case expressions crashes on django 1.8 -+- Reporter: albertein|Owner: Type: Bug | Status: new Compone

Re: [Django] #25858: Deriving from abstract model with foreign key to model in same app broken on Django 1.9

2016-01-11 Thread Django
#25858: Deriving from abstract model with foreign key to model in same app broken on Django 1.9 -+- Reporter: kaedroho |Owner: charettes Type: Bug |

Re: [Django] #26071: IN queries inside conditional case expressions crashes on django 1.8

2016-01-11 Thread Django
#26071: IN queries inside conditional case expressions crashes on django 1.8 -+- Reporter: albertein|Owner: timgraham Type: Bug | Status: assi

Re: [Django] #26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions.

2016-01-11 Thread Django
#26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions. -+- Reporter: timgraham|Owner: timgraham Type: | S

Re: [Django] #26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions.

2016-01-11 Thread Django
#26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions. -+- Reporter: timgraham|Owner: timgraham Type: | S

Re: [Django] #20869: Prevent repetitive output to counter BREACH-type attacks

2016-01-11 Thread Django
#20869: Prevent repetitive output to counter BREACH-type attacks -+ Reporter: patrys |Owner: shaib Type: New feature | Status: assigned Component: CSRF |

Re: [Django] #26071: IN queries inside conditional case expressions crashes on django 1.8

2016-01-11 Thread Django
#26071: IN queries inside conditional case expressions crashes on django 1.8 -+- Reporter: albertein|Owner: nobody Type: Bug | Status: new

Re: [Django] #26071: IN queries inside conditional case expressions crashes on django 1.8

2016-01-11 Thread Django
#26071: IN queries inside conditional case expressions crashes on django 1.8 -+- Reporter: albertein|Owner: nobody Type: Bug | Status: new

Re: [Django] #26071: IN queries inside conditional case expressions crashes on django 1.8

2016-01-11 Thread Django
#26071: IN queries inside conditional case expressions crashes on django 1.8 -+- Reporter: albertein|Owner: nobody Type: Bug | Status: new

[Django] #26071: IN queries inside conditional case expressions crashes on django 1.8

2016-01-11 Thread Django
#26071: IN queries inside conditional case expressions crashes on django 1.8 --+ Reporter: albertein | Owner: nobody Type: Bug | Status: new Component: Datab

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions.

2016-01-11 Thread Django
#26048: Switch selenium tests to use implicitly_wait() instead of custom wait functions. -+- Reporter: timgraham|Owner: timgraham Type: | S

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26066: Admin changelist could handle a table wider than the screen more elegantly

2016-01-11 Thread Django
#26066: Admin changelist could handle a table wider than the screen more elegantly -+- Reporter: chozabu |Owner: nobody Type: | Status:

Re: [Django] #26066: Admin changelist could handle a table wider than the screen more elegantly

2016-01-11 Thread Django
#26066: Admin changelist could handle a table wider than the screen more elegantly -+- Reporter: chozabu |Owner: nobody Type: | Status:

Re: [Django] #26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation'

2016-01-11 Thread Django
#26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation' --+ Reporter: srkunze |Owner: nobody Type: Cleanup/optimization | Sta

Re: [Django] #25385: Allow importing django.views.generic.View from django.views.View

2016-01-11 Thread Django
#25385: Allow importing django.views.generic.View from django.views.View --+ Reporter: jambonrose|Owner: auvipy Type: Cleanup/optimization | Status: closed

Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2016-01-11 Thread Django
#25684: Runserver doesn't use `LOGGING` configuration ---+ Reporter: fcurella |Owner: fcurella Type: New feature| Status: closed Component: Error report

Re: [Django] #24810: Reopen database connection automatically when no transaction is active

2016-01-11 Thread Django
#24810: Reopen database connection automatically when no transaction is active -+- Reporter: aaugustin|Owner: nobody Type: New feature | Status: new

Re: [Django] #24810: Reopen database connection automatically when no transaction is active

2016-01-11 Thread Django
#24810: Reopen database connection automatically when no transaction is active -+- Reporter: aaugustin|Owner: nobody Type: New feature | Status: new

Re: [Django] #26066: Admin changelist could handle a table wider than the screen more elegantly (was: Admin handles a table of models being wider than the screen badly)

2016-01-11 Thread Django
#26066: Admin changelist could handle a table wider than the screen more elegantly -+- Reporter: chozabu |Owner: nobody Type: | Status:

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation'

2016-01-11 Thread Django
#26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation' --+ Reporter: srkunze |Owner: nobody Type: Cleanup/optimization | Sta

Re: [Django] #26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation'

2016-01-11 Thread Django
#26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation' -+- Reporter: srkunze |Owner: nobody Type: | Statu

Re: [Django] #25476: bug in array handling hit in get_constraints() for psycopg2?

2016-01-11 Thread Django
#25476: bug in array handling hit in get_constraints() for psycopg2? -+- Reporter: heasus |Owner: nobody Type: Bug | Status: closed Comp

Re: [Django] #25858: Deriving from abstract model with foreign key to model in same app broken on Django 1.9

2016-01-11 Thread Django
#25858: Deriving from abstract model with foreign key to model in same app broken on Django 1.9 -+- Reporter: kaedroho |Owner: charettes Type: Bug |

[Django] #26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation'

2016-01-11 Thread Django
#26069: Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation' --+ Reporter: srkunze | Owner: nobody Type: Uncategorized | Status: new Compon

Re: [Django] #25755: Unify the spelling of the word "websites" in the documentation

2016-01-11 Thread Django
#25755: Unify the spelling of the word "websites" in the documentation -+- Reporter: RubyTheRedhead |Owner: Type: | RubyTheRedhead Cleanup/optimization

Re: [Django] #25755: Unify the spelling of the word "websites" in the documentation

2016-01-11 Thread Django
#25755: Unify the spelling of the word "websites" in the documentation -+- Reporter: RubyTheRedhead |Owner: Type: | RubyTheRedhead Cleanup/optimization

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26067: Orderable ArrayAgg and StringAgg

2016-01-11 Thread Django
#26067: Orderable ArrayAgg and StringAgg -+- Reporter: fdh |Owner: Type: New feature | Status: new Component: contrib.postgres |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

[Django] #26068: Django 1.8: KEY constraint for parent model missing in m2m [regression]

2016-01-11 Thread Django
#26068: Django 1.8: KEY constraint for parent model missing in m2m [regression] --+--- Reporter: direx | Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter

2016-01-11 Thread Django
#26063: Regression in Django 1.9: SQLite can no longer handle more than 2000 values in a "foo__in" filter -+- Reporter: rhertzog |Owner: aaugustin Type: Bug |

Re: [Django] #26067: Orderable ArrayAgg and StringAgg

2016-01-11 Thread Django
#26067: Orderable ArrayAgg and StringAgg -+- Reporter: fdh |Owner: Type: New feature | Status: new Component: contrib.postgres |

[Django] #26067: Orderable ArrayAgg and StringAgg

2016-01-11 Thread Django
#26067: Orderable ArrayAgg and StringAgg -+- Reporter: fdh | Owner: Type: New feature | Status: new Component: |Version: contrib.postgres |

Re: [Django] #25971: BrokenLinkEmailsMiddleware shouldn't report 404s when URL = Referer + "/"

2016-01-11 Thread Django
#25971: BrokenLinkEmailsMiddleware shouldn't report 404s when URL = Referer + "/" --+ Reporter: jribbens |Owner: nobody Type: Bug | Status: new Component: Cor