Re: [Django] #27273: Make usage of construct_change_message easier outside of admin

#27273: Make usage of construct_change_message easier outside of admin --+ Reporter: Alexey Rogachev |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #27273: Make usage of construct_change_message easier outside of admin

#27273: Make usage of construct_change_message easier outside of admin --+ Reporter: Alexey Rogachev |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27286: Tests fails when using multi-db and some DB is read-only

#27286: Tests fails when using multi-db and some DB is read-only ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #26720: migration optimizer can produce operations that references removed models under certain circumstances

#26720: migration optimizer can produce operations that references removed models under certain circumstances -+- Reporter: Sergey Fedoseev |Owner: Sergey |

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #11078: Proxy models do not inherit META.app_label

#11078: Proxy models do not inherit META.app_label -+- Reporter: George Song |Owner: Jonatas Type: | CD Cleanup/optimization |

Re: [Django] #11078: Proxy models do not inherit META.app_label

#11078: Proxy models do not inherit META.app_label -+- Reporter: George Song |Owner: Jonatas Type: | CD Cleanup/optimization |

Re: [Django] #25504: Django test teardown fails when there is no default database

#25504: Django test teardown fails when there is no default database ---+ Reporter: Sjoerd Langkemper |Owner: mihaicc Type: Bug| Status: assigned

Re: [Django] #26886: TECHNICAL_404_TEMPLATE logs an "Exception while resolving variable" warning (was: Wrong warnings during template rendering)

#26886: TECHNICAL_404_TEMPLATE logs an "Exception while resolving variable" warning --+ Reporter: None |Owner: None Type: Cleanup/optimization | Status:

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

[Django] #27291: Missing attribute: CheckboxSelectMultiple.dont_use_model_field_default_for_empty_data = True

#27291: Missing attribute: CheckboxSelectMultiple.dont_use_model_field_default_for_empty_data = True + Reporter: stephenmcd | Owner: nobody Type: Bug | Status: new Component: Forms |Version: 1.10

Re: [Django] #27291: Missing attribute: CheckboxSelectMultiple.dont_use_model_field_default_for_empty_data = True

#27291: Missing attribute: CheckboxSelectMultiple.dont_use_model_field_default_for_empty_data = True +-- Reporter: stephenmcd |Owner: nobody Type: Bug | Status: new

Re: [Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Bug| Status: closed

Re: [Django] #27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf

#27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf + Reporter: Graham Wideman |Owner: nobody Type: Bug | Status: closed

Re: [Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status: closed

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27188: Allow using unique=True with FileField

#27188: Allow using unique=True with FileField -+- Reporter: Jon Ribbens |Owner: Michael | Scott Type: New feature |

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27279: Slow test framework initialization in 1.10.1 compared to 1.10

#27279: Slow test framework initialization in 1.10.1 compared to 1.10 -+- Reporter: mtomiyoshi |Owner: nobody Type: | Status: new

Re: [Django] #27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf

#27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf + Reporter: Graham Wideman |Owner: nobody Type: Bug | Status: closed

Re: [Django] #27272: Add a on_delete RESTRICT handler to allow cascading deletions while protecting direct ones

#27272: Add a on_delete RESTRICT handler to allow cascading deletions while protecting direct ones -+- Reporter: Daniel Izquierdo |Owner: Daniel | Izquierdo

[Django] #27283: Typo in the documentation

#27283: Typo in the documentation ---+ Reporter: Vinay Singh| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.10 Severity: Normal | Keywords: Triage

[Django] #27284: Typo error in doc file

#27284: Typo error in doc file ---+ Reporter: Vinay Singh| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.10 Severity: Normal | Keywords: Triage Stage:

Re: [Django] #27284: Typo error in doc file

#27284: Typo error in doc file ---+-- Reporter: Vinay Singh|Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized | Version: 1.10

Re: [Django] #27287: IndexError in logging on runserver broken pipe error (was: IndexError on broken pipe)

#27287: IndexError in logging on runserver broken pipe error +-- Reporter: Sjoerd Job Postmus |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #27226: Remove patch_response_headers()'s setting of the "Last-Modified" header

#27226: Remove patch_response_headers()'s setting of the "Last-Modified" header -+- Reporter: Rinat Khabibiev |Owner: Rinat Type: | Khabibiev

Re: [Django] #27287: IndexError in logging on runserver broken pipe error

#27287: IndexError in logging on runserver broken pipe error +-- Reporter: Sjoerd Job Postmus |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #27288: In multi-db setup changes written to master are not seen on read-replicas

#27288: In multi-db setup changes written to master are not seen on read-replicas ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status: new

[Django] #27287: IndexError on broken pipe

#27287: IndexError on broken pipe + Reporter: Sjoerd Job Postmus | Owner: nobody Type: Bug | Status: new Component: Uncategorized |Version: 1.10 Severity: Normal |

[Django] #27288: In multi-db setup changes written to master are not seen on read-replicas

#27288: In multi-db setup changes written to master are not seen on read-replicas ---+--- Reporter: Jose M Herrero | Owner: nobody Type: Uncategorized | Status: new Component: Testing framework |

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data (was: can-order: we don't use initial data)

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

Re: [Django] #27283: Typo in the documentation

#27283: Typo in the documentation --+ Reporter: Vinay Singh |Owner: nobody Type: Cleanup/optimization | Status: closed Component: Documentation |

Re: [Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #27286: Tests fails when using multi-db and some DB is read-only

#27286: Tests fails when using multi-db and some DB is read-only ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #27284: Typo error in doc file

#27284: Typo error in doc file ---+-- Reporter: Vinay Singh|Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized | Version:

Re: [Django] #27284: Typo error in doc file

#27284: Typo error in doc file -+- Reporter: Vinay Singh |Owner: nobody Type: | Status: closed Cleanup/optimization |

Re: [Django] #27283: Typo in the documentation

#27283: Typo in the documentation --+ Reporter: Vinay Singh |Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |

[Django] #27286: Tests fails when using multi-db and some DB is read-only

#27286: Tests fails when using multi-db and some DB is read-only ---+--- Reporter: Jose M Herrero | Owner: nobody Type: Bug| Status: new Component: Testing framework |Version: 1.10

Re: [Django] #27280: can-order: we don't use initial data

#27280: can-order: we don't use initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf

#27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf +- Reporter: Graham Wideman | Owner: nobody Type: Bug | Status: new Component: Documentation |Version: 1.10

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

Re: [Django] #27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf

#27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf + Reporter: Graham Wideman |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #27226: Remove patch_response_headers()'s setting of the "Last-Modified" header

#27226: Remove patch_response_headers()'s setting of the "Last-Modified" header -+- Reporter: Rinat Khabibiev |Owner: Rinat Type: | Khabibiev

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

Re: [Django] #27267: Migrations: Need API to drop a foreign key constraint

#27267: Migrations: Need API to drop a foreign key constraint +-- Reporter: Melvyn Sopacua |Owner: nobody Type: Bug | Status: new Component: Migrations

Re: [Django] #27288: In multi-db setup changes written to master are not seen on read-replicas

#27288: In multi-db setup changes written to master are not seen on read-replicas ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status:

[Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict +--- Reporter: Jose M Herrero | Owner: nobody Type: Uncategorized | Status: new Component: Documentation |Version: 1.10

Re: [Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #27267: Migrations: Need API to drop a foreign key constraint

#27267: Migrations: Need API to drop a foreign key constraint +-- Reporter: Melvyn Sopacua |Owner: nobody Type: Bug | Status: new Component: Migrations

Re: [Django] #27283: Typo in the documentation

#27283: Typo in the documentation --+ Reporter: Vinay Singh |Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |

Re: [Django] #22309: DatabaseFeatures.supports_transactions should use temporary tables

#22309: DatabaseFeatures.supports_transactions should use temporary tables -+- Reporter: lucastan@… |Owner: nobody Type: | Status: new

Re: [Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #27217: makemigrations crashes with "'SpatialRefSysMixin' has no attribute '_meta'" on PostGIS

#27217: makemigrations crashes with "'SpatialRefSysMixin' has no attribute '_meta'" on PostGIS -+ Reporter: Satish V Madala |Owner: nobody Type: Bug | Status:

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

Re: [Django] #27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf

#27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf + Reporter: Graham Wideman |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

Re: [Django] #27285: Multi-db example : default database config can not be an empty dict

#27285: Multi-db example : default database config can not be an empty dict ---+-- Reporter: Jose M Herrero |Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #26886: Wrong warnings during template rendering

#26886: Wrong warnings during template rendering -+-- Reporter: None |Owner: None Type: Bug | Status: new Component: Error reporting |

Re: [Django] #27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf

#27289: Docs: Badly wrong explanation of View.as_view() and its use in urlconf + Reporter: Graham Wideman |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #27280: can_order/can_delete documentation examples don't require initial data

#27280: can_order/can_delete documentation examples don't require initial data -+- Reporter: Kifsif |Owner: nobody Type: | Status:

[Django] #27290: Email validation doesn't check length

#27290: Email validation doesn't check length ---+ Reporter: kyoki | Owner: nobody Type: Bug| Status: new Component: Uncategorized |Version: 1.10 Severity: Normal | Keywords: