Re: [Django] #30231: Field's verbose_name is ignored in FilteredSelectMultiple widget for inlines created with "Add another" button

2019-03-04 Thread Django
#30231: Field's verbose_name is ignored in FilteredSelectMultiple widget for inlines created with "Add another" button -+- Reporter: Florian Schuler |Owner: Ahisahar

Re: [Django] #30236: UsernameField should use autocapitalize="none" (was: Username Fields should use autocapitalize="none")

2019-03-04 Thread Django
#30236: UsernameField should use autocapitalize="none" --+ Reporter: Clayton Daley |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #30231: Field's verbose_name is ignored in FilteredSelectMultiple widget for inlines created with "Add another" button (was: "verbose_name" is ignored in FilteredSelectMultiple widget for

2019-03-04 Thread Django
#30231: Field's verbose_name is ignored in FilteredSelectMultiple widget for inlines created with "Add another" button -+- Reporter: Florian Schuler |Owner: Ahisahar

[Django] #30236: should Use autocapitalize="none"

2019-03-04 Thread Django
#30236: should Use autocapitalize="none" + Reporter: Clayton Daley | Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.auth

Re: [Django] #30236: Username Fields should use autocapitalize="none" (was: should Use autocapitalize="none")

2019-03-04 Thread Django
#30236: Username Fields should use autocapitalize="none" -+- Reporter: Clayton Daley|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #30232: Correct expected format in invalid DurationField error message

2019-03-04 Thread Django
#30232: Correct expected format in invalid DurationField error message -+- Reporter: Aidas Bendoraitis|Owner: avas9366 Type: Bug | Status: closed

Re: [Django] #30232: Correct expected format in invalid DurationField error message (was: Correct the error message for the invalid DurationField)

2019-03-04 Thread Django
#30232: Correct expected format in invalid DurationField error message -+- Reporter: Aidas Bendoraitis|Owner: avas9366 Type: Bug | Status: assigned

Re: [Django] #30234: Disallow non-uppercase settings in settings.configure() (was: Disallow non-upper settings)

2019-03-04 Thread Django
#30234: Disallow non-uppercase settings in settings.configure() --+ Reporter: orlnub123 |Owner: nobody Type: Bug | Status: new Component: Core (Other) |

Re: [Django] #29459: Make Form data/files initialize with an empty MultiValueDict rather than dict

2019-03-04 Thread Django
#29459: Make Form data/files initialize with an empty MultiValueDict rather than dict -+- Reporter: Sven R. Kunze|Owner: Andra Type: | Denis Ionescu

Re: [Django] #30231: "verbose_name" is ignored in FilteredSelectMultiple widget for new objects

2019-03-04 Thread Django
#30231: "verbose_name" is ignored in FilteredSelectMultiple widget for new objects -+- Reporter: Florian Schuler |Owner: Ahisahar | Pretel Type:

Re: [Django] #28477: Strip unused annotations from count queries

2019-03-04 Thread Django
#28477: Strip unused annotations from count queries -+- Reporter: Tom Forbes |Owner: Tom Type: | Forbes Cleanup/optimization |

Re: [Django] #28477: Strip unused annotations from count queries

2019-03-04 Thread Django
#28477: Strip unused annotations from count queries -+- Reporter: Tom Forbes |Owner: Tom Type: | Forbes Cleanup/optimization |

Re: [Django] #30188: Aggregate annotation, Case() - When(): AssertionError No exception message supplied

2019-03-04 Thread Django
#30188: Aggregate annotation, Case() - When(): AssertionError No exception message supplied -+- Reporter: Lukas Klement|Owner: nobody Type: Bug |

Re: [Django] #30224: Mysql Datetime value is string instead of datetime object

2019-03-04 Thread Django
#30224: Mysql Datetime value is string instead of datetime object -+- Reporter: Martin Kuhn |Owner: nobody Type: Bug | Status: new

Re: [Django] #30224: Mysql Datetime value is string instead of datetime object

2019-03-04 Thread Django
#30224: Mysql Datetime value is string instead of datetime object -+- Reporter: Martin Kuhn |Owner: nobody Type: Bug | Status: new

Re: [Django] #30224: Mysql Datetime value is string instead of datetime object

2019-03-04 Thread Django
#30224: Mysql Datetime value is string instead of datetime object -+- Reporter: Martin Kuhn |Owner: nobody Type: Bug | Status: new

Re: [Django] #30235: Fix a Russian localization

2019-03-04 Thread Django
#30235: Fix a Russian localization -+- Reporter: amalchuk |Owner: nobody Type: Bug | Status: closed Component: |

Re: [Django] #30234: Disallow non-upper settings

2019-03-04 Thread Django
#30234: Disallow non-upper settings --+ Reporter: orlnub123 |Owner: nobody Type: Bug | Status: new Component: Core (Other) | Version: master

[Django] #30235: Fix a Russian localization

2019-03-04 Thread Django
#30235: Fix a Russian localization -+- Reporter: amalchuk | Owner: nobody Type: Bug| Status: new Component: |Version: master

Re: [Django] #30224: Mysql Datetime value is string instead of datetime object

2019-03-04 Thread Django
#30224: Mysql Datetime value is string instead of datetime object -+- Reporter: Martin Kuhn |Owner: nobody Type: Bug | Status: new

Re: [Django] #30231: "verbose_name" is ignored in FilteredSelectMultiple widget for new objects

2019-03-04 Thread Django
#30231: "verbose_name" is ignored in FilteredSelectMultiple widget for new objects -+- Reporter: Florian Schuler |Owner: Ahisahar | Pretel Type:

Re: [Django] #30234: Disallow non-upper settings

2019-03-04 Thread Django
#30234: Disallow non-upper settings --+ Reporter: orlnub123 |Owner: nobody Type: Bug | Status: new Component: Core (Other) | Version: master