Re: [Django] #24523: django.apps.registry.populate() does not handle failures in app_config.ready()

#24523: django.apps.registry.populate() does not handle failures in app_config.ready() ---+-- Reporter: kalium99 |Owner: nobody Type: Bug| Status: new

Re: [Django] #24527: Using standalone templates gives confusing error message

#24527: Using standalone templates gives confusing error message -+- Reporter: cjerdonek|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

[Django] #24527: Using standalone templates gives confusing error message

#24527: Using standalone templates gives confusing error message ---+--- Reporter: cjerdonek | Owner: nobody Type: Bug| Status: new Component: Uncategorized |Version: 1.7

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: | Status:

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status: new

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status: new

Re: [Django] #23658: Provide the password to PostgreSQL from "dbshell" command

#23658: Provide the password to PostgreSQL from "dbshell" command -+- Reporter: etanol |Owner: nobody Type: New feature | Status: new

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

[Django] #24526: Default logging config filters out anything below ERROR for django.request/django.security loggers

#24526: Default logging config filters out anything below ERROR for django.request/django.security loggers -+- Reporter: timgraham | Owner: timgraham Type: |

Re: [Django] #24525: AssertionError at `Query.change_aliases`

#24525: AssertionError at `Query.change_aliases` -+- Reporter: coolRR |Owner: nobody Type: Bug | Status: closed Component: Database

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #24525: AssertionError at `Query.change_aliases`

#24525: AssertionError at `Query.change_aliases` -+- Reporter: coolRR |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #12400: column "X" named in key does not exist error when models.PointField used in unique_together

#12400: column "X" named in key does not exist error when models.PointField used in unique_together + Reporter: monkut |Owner: claudep Type: Bug | Status: new Component:

Re: [Django] #24525: AssertionError at `Query.change_aliases`

#24525: AssertionError at `Query.change_aliases` -+- Reporter: coolRR |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #24280: CSRF cookie error only happening with Chrome.

#24280: CSRF cookie error only happening with Chrome. -+-- Reporter: jkapple |Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #24525: AssertionError at `Query.change_aliases`

#24525: AssertionError at `Query.change_aliases` -+- Reporter: coolRR |Owner: nobody Type: Bug | Status: new Component: Database layer

[Django] #24525: AssertionError at `Query.change_aliases`

#24525: AssertionError at `Query.change_aliases` --+ Reporter: coolRR| Owner: nobody Type: Bug | Status: new Component: Database layer (models, ORM) |

Re: [Django] #12400: column "X" named in key does not exist error when models.PointField used in unique_together

#12400: column "X" named in key does not exist error when models.PointField used in unique_together +- Reporter: monkut |Owner: claudep Type: Bug | Status: closed

Re: [Django] #24483: keepdb migrations break choices as generators

#24483: keepdb migrations break choices as generators -+- Reporter: davidszotten |Owner: Type: Bug | Status: new Component: Migrations

Re: [Django] #11390: If you use a callable as default value on a model field, it gets called 3 times.

#11390: If you use a callable as default value on a model field, it gets called 3 times. --+ Reporter: espen.nettbruk@… |Owner: Type: Bug | Status: new

Re: [Django] #24347: parameter 'widget' of BoundField.as_widget is ignored

#24347: parameter 'widget' of BoundField.as_widget is ignored -+- Reporter: srkunze |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #10060: Multiple table annotation failure

#10060: Multiple table annotation failure -+- Reporter: svsharma@… |Owner: Type: Bug | Status: new Component: Database layer |

Re: [Django] #24523: django.apps.registry.populate() does not handle failures in app_config.ready()

#24523: django.apps.registry.populate() does not handle failures in app_config.ready() ---+-- Reporter: kalium99 |Owner: nobody Type: Bug| Status: new

Re: [Django] #24440: Debug.py could use additional padding for individual stack rows.

#24440: Debug.py could use additional padding for individual stack rows. -+- Reporter: commadelimited |Owner: nobody Type: | Status: closed

Re: [Django] #24521: frozensets don't seem to work quite right in migrations as field kwargs

#24521: frozensets don't seem to work quite right in migrations as field kwargs -+- Reporter: ris |Owner: nobody Type: Bug | Status:

Re: [Django] #24521: frozensets don't seem to work quite right in migrations as field kwargs

#24521: frozensets don't seem to work quite right in migrations as field kwargs -+- Reporter: ris |Owner: nobody Type: Bug | Status: new

Re: [Django] #24442: Index name truncation is odd

#24442: Index name truncation is odd + Reporter: shaib |Owner: nobody Type: Bug | Status: new Component: Migrations | Version: master

Re: [Django] #24470: Serialization of base classes is not customizable for migrations

#24470: Serialization of base classes is not customizable for migrations -+ Reporter: rockymeza|Owner: nobody Type: New feature | Status: new Component: Migrations |

Re: [Django] #24521: frozensets don't seem to work quite right in migrations as field kwargs

#24521: frozensets don't seem to work quite right in migrations as field kwargs -+- Reporter: ris |Owner: nobody Type: Bug | Status: new

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status:

Re: [Django] #24520: Add documentation for supports_microseconds widget property

#24520: Add documentation for supports_microseconds widget property --+ Reporter: pkatseas |Owner: wdmgsm Type: Cleanup/optimization | Status: assigned

Re: [Django] #23697: Confusing exception raised upon unknown field in queryset filter argument

#23697: Confusing exception raised upon unknown field in queryset filter argument -+- Reporter: mbertheau|Owner: exonian Type: | Status:

Re: [Django] #24513: "... has no field named None" with M2MField when migrating

#24513: "... has no field named None" with M2MField when migrating -+-- Reporter: Kondou-ger |Owner: nobody Type: Uncategorized| Status: new Component:

Re: [Django] #24134: Document short command line options for management commands

#24134: Document short command line options for management commands --+ Reporter: mjtamlyn |Owner: staeff Type: Cleanup/optimization | Status: assigned

Re: [Django] #24361: The doc is not right w.r.t. LOGGING overwriting.

#24361: The doc is not right w.r.t. LOGGING overwriting. ---+ Reporter: Tuttle |Owner: nobody Type: Bug| Status: new Component: Documentation |

Re: [Django] #11390: If you use a callable as default value on a model field, it gets called 3 times.

#11390: If you use a callable as default value on a model field, it gets called 3 times. --+ Reporter: espen.nettbruk@… |Owner: tomviner Type: Bug | Status:

Re: [Django] #11390: If you use a callable as default value on a model field, it gets called 3 times.

#11390: If you use a callable as default value on a model field, it gets called 3 times. --+ Reporter: espen.nettbruk@… |Owner: tomviner Type: Bug | Status:

Re: [Django] #24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly

#24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly -+- Reporter: gergelypolonkai |Owner: | marcofucci

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status:

Re: [Django] #15667: Implement template-based widget rendering

#15667: Implement template-based widget rendering + Reporter: brutasse|Owner: auvipy Type: New feature | Status: assigned Component: Forms |

Re: [Django] #15667: Implement template-based widget rendering

#15667: Implement template-based widget rendering + Reporter: brutasse|Owner: auvipy Type: New feature | Status: assigned Component: Forms |

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status: new

Re: [Django] #16362: Ignore, rather than disallow, negative lookahead assertions

#16362: Ignore, rather than disallow, negative lookahead assertions -+- Reporter: charles@…|Owner: bpeschier Type: | Status: closed

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

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

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

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

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

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

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status: new

Re: [Django] #13525: Document how to reverse URL patterns with nested groups

#13525: Document how to reverse URL patterns with nested groups -+- Reporter: nickretallack|Owner: bpeschier Type: | Status: closed

Re: [Django] #13525: Document how to reverse URL patterns with nested groups

#13525: Document how to reverse URL patterns with nested groups -+- Reporter: nickretallack|Owner: bpeschier Type: | Status: closed

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble --+ Reporter: riklaunim |Owner: nobody Type: Bug | Status: new Component: Forms

Re: [Django] #12400: column "X" named in key does not exist error when models.PointField used in unique_together

#12400: column "X" named in key does not exist error when models.PointField used in unique_together +- Reporter: monkut |Owner: claudep Type: Bug | Status: assigned

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status: new

Re: [Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: SimonSteinberger |Owner: nobody Type: Bug | Status: new

[Django] #24524: Automatic migrations prevent creation of initial database table layout

#24524: Automatic migrations prevent creation of initial database table layout -+- Reporter: | Owner: nobody SimonSteinberger | Type: Bug | Status: new

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble --+ Reporter: riklaunim |Owner: nobody Type: Bug | Status: new Component: Forms