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

#25684: Runserver doesn't use `LOGGING` configuration ---+ Reporter: fcurella |Owner: fcurella Type: New feature| Status: assigned Component: Error

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

#25684: Runserver doesn't use `LOGGING` configuration ---+ Reporter: fcurella |Owner: fcurella Type: New feature| Status: assigned Component: Error

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

#25684: Runserver doesn't use `LOGGING` configuration ---+ Reporter: fcurella |Owner: fcurella Type: New feature| Status: assigned Component: Error

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

#25684: Runserver doesn't use `LOGGING` configuration ---+-- Reporter: fcurella |Owner: fcurella Type: New feature| Status: assigned Component: Error

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

#25684: Runserver doesn't use `LOGGING` configuration ---+-- Reporter: fcurella |Owner: Type: New feature| Status: new Component: Error reporting|

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

#25684: Runserver doesn't use `LOGGING` configuration -+-- Reporter: fcurella |Owner: Type: New feature | Status: new Component: Error reporting |

Re: [Django] #25685: Deferred model leak

#25685: Deferred model leak -+- Reporter: ppetrid |Owner: charettes Type: Bug | Status: assigned Component: Database layer |

Re: [Django] #25685: Deferred model leak

#25685: Deferred model leak -+- Reporter: ppetrid |Owner: nobody Type: Bug | Status: new Component: Database layer |

[Django] #25685: Deferred model leak

#25685: Deferred model leak --+ Reporter: ppetrid | Owner: nobody Type: Bug | Status: new Component: Database layer (models, ORM) |Version: 1.8

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

#25684: Runserver doesn't use `LOGGING` configuration -+-- Reporter: fcurella |Owner: Type: New feature | Status: new Component: Error reporting |

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

#25684: Runserver doesn't use `LOGGING` configuration -+-- Reporter: fcurella |Owner: Type: New feature | Status: new Component: Error reporting |

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

#25684: Runserver doesn't use `LOGGING` configuration -+- Reporter: fcurella | Owner: Type: New feature | Status: new Component: Error reporting |Version: 1.8 Severity: Normal |

Re: [Django] #25551: makemigrations when adding a ForeignKey to a newly created model along with a unique_together constraint must create fields before the unique_together constraint

#25551: makemigrations when adding a ForeignKey to a newly created model along with a unique_together constraint must create fields before the unique_together constraint +--- Reporter: mssnlayam |Owner:

Re: [Django] #25617: Disallow usernames that differ only in case in UserCreationForm

#25617: Disallow usernames that differ only in case in UserCreationForm --+ Reporter: timgraham |Owner: nmundar Type: Cleanup/optimization | Status: assigned

Re: [Django] #25496: ModelChoiceField generates extra queries by not respecting prefetch_related

#25496: ModelChoiceField generates extra queries by not respecting prefetch_related -+- Reporter: mdentremont |Owner: nobody Type: Bug | Status:

Re: [Django] #25683: 1.8.6 regression: ModelChoiceField no longer accepts Manager objects as queryset

#25683: 1.8.6 regression: ModelChoiceField no longer accepts Manager objects as queryset -+-- Reporter: intgr|Owner: nobody Type: Bug | Status: new

[Django] #25683: 1.8.6 regression: ModelChoiceField no longer accepts Manager objects as queryset

#25683: 1.8.6 regression: ModelChoiceField no longer accepts Manager objects as queryset -+ Reporter: intgr| Owner: nobody Type: Bug | Status: new Component: Forms|Version:

Re: [Django] #25682: Audit bare except clauses

#25682: Audit bare except clauses --+ Reporter: aaugustin |Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Other) |

Re: [Django] #2651: ForeignKey search/filter/autocomplete widget

#2651: ForeignKey search/filter/autocomplete widget -+- Reporter: zaur |Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #25670: `dictsort` does not work when `arg` parameter is numeric

#25670: `dictsort` does not work when `arg` parameter is numeric -+- Reporter: soon |Owner: soon Type: Bug | Status: assigned

Re: [Django] #25681: Possible minor contradiction in DATABASES setting depicted in multiple database/routing docs example.

#25681: Possible minor contradiction in DATABASES setting depicted in multiple database/routing docs example. ---+ Reporter: aleks |Owner: nobody Type: Bug|

Re: [Django] #25682: Audit bare except clauses (was: Bare except clauses)

#25682: Audit bare except clauses --+ Reporter: aaugustin |Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Other) |

Re: [Django] #25679: ModelForm.Meta.fields and exclude are not honoured for custom fields

#25679: ModelForm.Meta.fields and exclude are not honoured for custom fields ---+-- Reporter: tino |Owner: nobody Type: Bug| Status: closed Component: Forms |

[Django] #25682: Bare except clauses

#25682: Bare except clauses + Reporter: aaugustin | Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Other) |

Re: [Django] #25679: ModelForm.Meta.fields and exclude are not honoured for custom fields

#25679: ModelForm.Meta.fields and exclude are not honoured for custom fields ---+-- Reporter: tino |Owner: nobody Type: Bug| Status: new Component: Forms |

Re: [Django] #25679: ModelForm.Meta.fields and exclude are not honoured for custom fields

#25679: ModelForm.Meta.fields and exclude are not honoured for custom fields ---+ Reporter: tino | Owner: nobody Type: Bug| Status: new Component: Forms |Version: master Severity: Normal |

[Django] #25681: Possible minor contradiction in DATABASES setting depicted in multiple database/routing docs example.

#25681: Possible minor contradiction in DATABASES setting depicted in multiple database/routing docs example. ---+ Reporter: aleks | Owner: nobody Type: Uncategorized | Status: new Component: Documentation |

Re: [Django] #25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()'

#25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()' ---+-- Reporter: hakanw |Owner: nobody Type: New feature| Status: new

Re: [Django] #25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()'

#25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()' ---+-- Reporter: hakanw |Owner: nobody Type: New feature| Status: new

Re: [Django] #25678: migrate scalar to array field in PostrgreSQL fails

#25678: migrate scalar to array field in PostrgreSQL fails -+- Reporter: mikofski |Owner: nobody Type: Uncategorized| Status: new Component:

Re: [Django] #25665: deprecate public getters/setters for properties of `GEOSGeometry` and its subclasses

#25665: deprecate public getters/setters for properties of `GEOSGeometry` and its subclasses -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd

Re: [Django] #25670: `dictsort` does not work when `arg` parameter is numeric

#25670: `dictsort` does not work when `arg` parameter is numeric -+- Reporter: soon |Owner: soon Type: Bug | Status: assigned

Re: [Django] #25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()'

#25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()' ---+-- Reporter: hakanw |Owner: nobody Type: New feature| Status: new

[Django] #25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()'

#25680: Feature request: support python manage.py shell -e 'run_some_code_as_django()' ---+ Reporter: hakanw | Owner: nobody Type: New feature| Status: new Component: Uncategorized |Version: 1.8

Re: [Django] #25660: `GEOSGeomerty.dims` is not documented

#25660: `GEOSGeomerty.dims` is not documented -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization |

Re: [Django] #25660: `GEOSGeomerty.dims` is not documented

#25660: `GEOSGeomerty.dims` is not documented -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization |

Re: [Django] #25660: `GEOSGeomerty.dims` is not documented

#25660: `GEOSGeomerty.dims` is not documented -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization |

Re: [Django] #24244: Document contrib.admin.models.LogEntry

#24244: Document contrib.admin.models.LogEntry --+--- Reporter: timgraham |Owner: alexmorozov Type: New feature | Status: closed Component: Documentation

Re: [Django] #24244: Document contrib.admin.models.LogEntry

#24244: Document contrib.admin.models.LogEntry --+--- Reporter: timgraham |Owner: alexmorozov Type: New feature | Status: closed Component: Documentation

Re: [Django] #24244: Document contrib.admin.models.LogEntry

#24244: Document contrib.admin.models.LogEntry --+--- Reporter: timgraham |Owner: alexmorozov Type: New feature | Status: closed Component: Documentation

Re: [Django] #25675: divisibleby template filter optimization

#25675: divisibleby template filter optimization -+- Reporter: hramezani|Owner: hramezani Type: | Status: assigned Cleanup/optimization

Re: [Django] #25676: Queryset.extra planned deprecation - Sorting a calculated field

#25676: Queryset.extra planned deprecation - Sorting a calculated field -+- Reporter: YunJD|Owner: nobody Type: Uncategorized| Status: new

Re: [Django] #25663: `LinearRing` and `LineString` don't check number of points during instantiation

#25663: `LinearRing` and `LineString` don't check number of points during instantiation -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd

Re: [Django] #25665: deprecate public getters/setters for properties of `GEOSGeometry` and its subclasses

#25665: deprecate public getters/setters for properties of `GEOSGeometry` and its subclasses -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd