Re: [Django] #30213: Add support for a "watchdog" based autoreloader

#30213: Add support for a "watchdog" based autoreloader -+ Reporter: Tom Forbes |Owner: nobody Type: New feature | Status: new Component: Utilities|

Re: [Django] #30215: `AttributeError: __spec__` on `./manage.py runserver`

#30215: `AttributeError: __spec__` on `./manage.py runserver` -+- Reporter: flaviut |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #30215: `AttributeError: __spec__` on `./manage.py runserver`

#30215: `AttributeError: __spec__` on `./manage.py runserver` -+- Reporter: flaviut |Owner: nobody Type: Bug | Status: new Component:

[Django] #30215: `AttributeError: __spec__` on `./manage.py runserver`

#30215: `AttributeError: __spec__` on `./manage.py runserver` -+- Reporter: flaviut| Owner: nobody Type: Bug| Status: new Component: Core

Re: [Django] #27685: Allow autoreloader to use watchman

#27685: Allow autoreloader to use watchman -+- Reporter: Aymeric Augustin |Owner: Tom Type: | Forbes Cleanup/optimization |

Re: [Django] #27685: Allow autoreloader to use watchman

#27685: Allow autoreloader to use watchman -+- Reporter: Aymeric Augustin |Owner: Tom Type: | Forbes Cleanup/optimization |

Re: [Django] #27685: Allow autoreloader to use watchman

#27685: Allow autoreloader to use watchman -+- Reporter: Aymeric Augustin |Owner: Tom Type: | Forbes Cleanup/optimization |

Re: [Django] #27685: Allow autoreloader to use watchman

#27685: Allow autoreloader to use watchman -+- Reporter: Aymeric Augustin |Owner: Tom Type: | Forbes Cleanup/optimization |

Re: [Django] #30196: Make FileResponse always set Content-Disposition header.

#30196: Make FileResponse always set Content-Disposition header. -+- Reporter: Piotr Kunicki|Owner: nobody Type: | Status: new

Re: [Django] #30214: Indexes defined on abstract base classes are not propagated to subclasses

#30214: Indexes defined on abstract base classes are not propagated to subclasses -+- Reporter: wKavey |Owner: nobody Type: Uncategorized| Status:

[Django] #30214: Indexes defined on abstract base classes are not propagated to subclasses

#30214: Indexes defined on abstract base classes are not propagated to subclasses -+- Reporter: wKavey | Owner: nobody Type: | Status: new Uncategorized

[Django] #30213: Add support for a "watchdog" based autoreloader

#30213: Add support for a "watchdog" based autoreloader ---+ Reporter: Tom Forbes | Owner: nobody Type: New feature | Status: new Component: Utilities|

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

#30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings ---+ Reporter: Matt Westcott |Owner: nobody Type: Bug| Status: new

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

#30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings ---+ Reporter: Matt Westcott |Owner: nobody Type: Bug| Status: new

Re: [Django] #30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings

#30179: Merging 3 or more media objects can throw unnecessary MediaOrderConflictWarnings ---+ Reporter: Matt Westcott |Owner: nobody Type: Bug| Status: new

Re: [Django] #30208: Login header sizing is inconsistent when window resizes

#30208: Login header sizing is inconsistent when window resizes -+- Reporter: Matthias Kestenholz |Owner: nobody Type: Bug | Status: closed

Re: [Django] #30208: Login header sizing is inconsistent when window resizes

#30208: Login header sizing is inconsistent when window resizes -+- Reporter: Matthias Kestenholz |Owner: nobody Type: Bug | Status: closed

Re: [Django] #29683: Add the view permission to several places in the docs

#29683: Add the view permission to several places in the docs -+- Reporter: Ariel Pontes |Owner: nobody Type: | Status: closed

Re: [Django] #29683: Add the view permission to several places in the docs

#29683: Add the view permission to several places in the docs -+- Reporter: Ariel Pontes |Owner: nobody Type: | Status: closed

Re: [Django] #29683: Add the view permission to several places in the docs

#29683: Add the view permission to several places in the docs -+- Reporter: Ariel Pontes |Owner: nobody Type: | Status: closed

Re: [Django] #29683: Add the view permission to several places in the docs

#29683: Add the view permission to several places in the docs -+- Reporter: Ariel Pontes |Owner: nobody Type: | Status: closed

Re: [Django] #29683: Add the view permission to several places in the docs

#29683: Add the view permission to several places in the docs -+- Reporter: Ariel Pontes |Owner: nobody Type: | Status: closed

Re: [Django] #30208: Login header sizing is inconsistent when window resizes

#30208: Login header sizing is inconsistent when window resizes -+- Reporter: Matthias Kestenholz |Owner: nobody Type: Bug | Status: closed

Re: [Django] #30208: Login header sizing is inconsistent when window resizes

#30208: Login header sizing is inconsistent when window resizes -+- Reporter: Matthias Kestenholz |Owner: nobody Type: Bug | Status: closed

Re: [Django] #30208: Login header sizing is inconsistent when window resizes (was: Login header sizing is inconsistent)

#30208: Login header sizing is inconsistent when window resizes -+- Reporter: Matthias Kestenholz |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #30212: Update documentation for multiple databases to reflect four default permissions

#30212: Update documentation for multiple databases to reflect four default permissions ---+- Reporter: Ryan Schave|Owner: nobody Type: Bug| Status: closed

Re: [Django] #30212: Update documentation for multiple databases to reflect four default permissions

#30212: Update documentation for multiple databases to reflect four default permissions ---+ Reporter: Ryan Schave|Owner: nobody Type: Uncategorized | Status: new

[Django] #30212: Update documentation for multiple databases to reflect four default permissions

#30212: Update documentation for multiple databases to reflect four default permissions -+ Reporter: Ryan Schave| Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #30207: Optimise paginator for tables with massive records

#30207: Optimise paginator for tables with massive records -+- Reporter: M. Javidan Darugar |Owner: M. Type: | Javidan Darugar Cleanup/optimization |

Re: [Django] #30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong

#30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong -+- Reporter: Kal Sze |

Re: [Django] #30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong

#30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong -+- Reporter: Kal Sze |

Re: [Django] #30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong

#30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong -+- Reporter: Kal Sze |

Re: [Django] #30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self

#30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self ---+ Reporter: Carsten Fuchs |Owner: Dart Type: Bug|

[Django] #30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong

#30211: Using QuerySet.union with a QuerySet.values_list with annotations results in broken SQL where the order of the fields from one side of the union is wrong -+- Reporter: Kal Sze| Owner:

Re: [Django] #30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self

#30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self ---+ Reporter: Carsten Fuchs |Owner: Dart Type: Bug|

Re: [Django] #30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self

#30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self ---+ Reporter: Carsten Fuchs |Owner: nobody Type: Bug|