Re: [Django] #32243: Clarify docs on manually setting and saving a FileField.

#32243: Clarify docs on manually setting and saving a FileField. -+- Reporter: Gordon Wrigley |Owner: Joshua Type: | Massover Cleanup/optimization

Re: [Django] #33300: Hidden fields are visible on small screens.

#33300: Hidden fields are visible on small screens. -+- Reporter: Maxim Danilov|Owner: Shubh | Parmar Type: Bug |

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

#23273: MigrationRecorder does not obey db_router allow_migrate rules +- Reporter: froomzy |Owner: Jacob Walls Type: Bug | Status: closed Component: Migra

Re: [Django] #33399: Overriding Choices for a field in the Form not working when using ModelForm. (was: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2)

#33399: Overriding Choices for a field in the Form not working when using ModelForm. ---+-- Reporter: Swaroop P |Owner: nobody Type: Uncategorized | Status: closed Compo

Re: [Django] #33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2

#33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2 ---+-- Reporter: Swaroop P |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2

#33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2 ---+-- Reporter: Swaroop P |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2

#33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2 ---+-- Reporter: Swaroop P |Owner: nobody Type: Uncategorized | Status: new

[Django] #33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2

#33399: Overriding Choices for a field in the Form not working when using ModelForm | Django 3.2 -+--- Reporter: Swaroop P | Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #33300: Hidden fields are visible on small screens.

#33300: Hidden fields are visible on small screens. -+- Reporter: Maxim Danilov|Owner: Shubh | Parmar Type: Bug |

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

#23273: MigrationRecorder does not obey db_router allow_migrate rules +- Reporter: froomzy |Owner: Jacob Walls Type: Bug | Status: assigned Component: Mig

Re: [Django] #33398: ModelAdmin.empty_value_display example in docs should use list_display. (was: ModelAdmin.empty_value_display documentation)

#33398: ModelAdmin.empty_value_display example in docs should use list_display. --+ Reporter: Michael |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #33256: Some schema tests don't clean up their tables

#33256: Some schema tests don't clean up their tables -+- Reporter: Tim Graham |Owner: banani720 Type: | Status: assigned Cleanup/optimiza

Re: [Django] #33256: Some schema tests don't clean up their tables

#33256: Some schema tests don't clean up their tables -+- Reporter: Tim Graham |Owner: banani720 Type: | Status: assigned Cleanup/optimiza

[Django] #33398: ModelAdmin.empty_value_display documentation

#33398: ModelAdmin.empty_value_display documentation -+ Reporter: Michael| Owner: nobody Type: Bug| Status: new Component: Documentation |

Re: [Django] #33397: Arithmetic operations on DateField/DateTimeField/DurationField expressions are buggy.

#33397: Arithmetic operations on DateField/DateTimeField/DurationField expressions are buggy. -+- Reporter: Luke Plant |Owner: Luke | Plant Ty

Re: [Django] #31335: Renaming a ForeignKey included in an index, and removing UniqueConstraint, Index with ForeignKey fails on MySQL.

#31335: Renaming a ForeignKey included in an index, and removing UniqueConstraint, Index with ForeignKey fails on MySQL. -+- Reporter: Stephen Finucane |Owner: Sergey

[Django] #33397: Arithmetic operations on DateField/DateTimeField/DurationField expressions are buggy.

#33397: Arithmetic operations on DateField/DateTimeField/DurationField expressions are buggy. -+- Reporter: Luke | Owner: Luke Plant Plant | Typ

Re: [Django] #33396: Add the ResolverMatch's name to the technical 500 page.

#33396: Add the ResolverMatch's name to the technical 500 page. -+ Reporter: Keryn Knight |Owner: Keryn Knight Type: New feature | Status: assigned Component:

Re: [Django] #33396: Add the ResolverMatch's name to the technical 500 page.

#33396: Add the ResolverMatch's name to the technical 500 page. -+ Reporter: Keryn Knight |Owner: (none) Type: New feature | Status: new Component: Error reporti

[Django] #33396: Add the ResolverMatch's name to the technical 500 page.

#33396: Add the ResolverMatch's name to the technical 500 page. ---+ Reporter: Keryn Knight | Owner: (none) Type: New feature | Status: new Component: Error

Re: [Django] #27936: Add some clarifications to "Spanning multi-valued relationships"

#27936: Add some clarifications to "Spanning multi-valued relationships" -+- Reporter: Thomas Güttler |Owner: Jacob Type: | Walls Cleanup/optimization

Re: [Django] #33394: Adding inlines doesn't work with a manually crafted HTML.

#33394: Adding inlines doesn't work with a manually crafted HTML. -+- Reporter: Maxim Danilov|Owner: nobody Type: | Status: closed Cleanup/o

Re: [Django] #33394: Adding inlines doesn't work with a manually crafted HTML.

#33394: Adding inlines doesn't work with a manually crafted HTML. -+- Reporter: Maxim Danilov|Owner: nobody Type: | Status: new Cleanup/opti

Re: [Django] #33395: No error raised when FILE_UPLOAD_TEMP_DIR is not accessible

#33395: No error raised when FILE_UPLOAD_TEMP_DIR is not accessible -+- Reporter: Martin Koščak|Owner: nobody Type: Bug | Status: closed Compo

[Django] #33395: No error raised when FILE_UPLOAD_TEMP_DIR is not accessible

#33395: No error raised when FILE_UPLOAD_TEMP_DIR is not accessible -+- Reporter: Martin | Owner: nobody Koščak | Type: | Status

Re: [Django] #26872: Django Admin filter choice list can overflow the whole page

#26872: Django Admin filter choice list can overflow the whole page ---+ Reporter: Damien |Owner: Kenneth Type: Bug| Status: closed Component: contrib.adm

Re: [Django] #33394: Adding inlines doesn't work with a manually crafted HTML. (was: inlines.js error in django.contrib.admin since Django 1.xx)

#33394: Adding inlines doesn't work with a manually crafted HTML. -+- Reporter: Maxim Danilov|Owner: nobody Type: | Status: closed Cleanup/o

Re: [Django] #33393: Weird title level in logging how-to

#33393: Weird title level in logging how-to -+- Reporter: Claude Paroz |Owner: nobody Type: | Status: closed Cleanup/optimization

[Django] #33394: inlines.js error in django.contrib.admin since Django 1.xx

#33394: inlines.js error in django.contrib.admin since Django 1.xx -+- Reporter: Maxim | Owner: nobody Danilov| Type: Bug| Status:

Re: [Django] #28135: simplify_regex() doesn't handle non-capturing groups

#28135: simplify_regex() doesn't handle non-capturing groups -+- Reporter: German M. Bravo |Owner: Ayush Type: | Joshi Cleanup/optimization |

Re: [Django] #28135: simplify_regex() doesn't handle non-capturing groups

#28135: simplify_regex() doesn't handle non-capturing groups -+- Reporter: German M. Bravo |Owner: Ayush Type: | Joshi Cleanup/optimization |

Re: [Django] #33300: Hidden fields are visible on small screens.

#33300: Hidden fields are visible on small screens. -+- Reporter: Maxim Danilov|Owner: Shubh | Parmar Type: Bug |

[Django] #33393: Weird title level in logging how-to

#33393: Weird title level in logging how-to + Reporter: Claude Paroz | Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentat