Re: [Django] #23626: Change coding style for sql, params return lines

#23626: Change coding style for sql, params return lines -+- Reporter: mjtamlyn |Owner: pavel- Type: | shpilev Cleanup/optimization |

Re: [Django] #23630: AlterModelTable doesn't rename auto-created tables

#23630: AlterModelTable doesn't rename auto-created tables -+ Reporter: Naddiseo |Owner: nobody Type: Bug | Status: new Component: Migrations

Re: [Django] #23649: Oracle GIS testing -- fails to destroy old leftover test database after unclean ending

#23649: Oracle GIS testing -- fails to destroy old leftover test database after unclean ending -+- Reporter: shaib|Owner: shaib Type: Uncategorized|

Re: [Django] #23649: Oracle GIS testing -- fails to destroy old leftover test database after unclean ending

#23649: Oracle GIS testing -- fails to destroy old leftover test database after unclean ending -+- Reporter: shaib|Owner: shaib Type: Uncategorized|

[Django] #23657: Migrations framework doesn't properly handle factory-generated base classes.

#23657: Migrations framework doesn't properly handle factory-generated base classes. + Reporter: jfialkoff | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.7 Severity:

Re: [Django] #23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3

#23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3 -+- Reporter: rhertzog |Owner: nobody Type: Bug |

Re: [Django] #23649: Oracle GIS testing -- fails to destroy old leftover test database after unclean ending

#23649: Oracle GIS testing -- fails to destroy old leftover test database after unclean ending -+- Reporter: shaib|Owner: shaib Type: Uncategorized|

Re: [Django] #23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3

#23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3 -+- Reporter: rhertzog |Owner: nobody Type: Bug |

[Django] #23656: FormMixin.get_form's form_class argument should be optional

#23656: FormMixin.get_form's form_class argument should be optional + Reporter: charettes | Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #9519: Add QuerySet.bulk_delete() that issues only a single SQL query

#9519: Add QuerySet.bulk_delete() that issues only a single SQL query -+- Reporter: Tarken |Owner: nobody Type: New feature | Status: new

Re: [Django] #23637: Remove TUX from static-files and modwsgi docs

#23637: Remove TUX from static-files and modwsgi docs --+ Reporter: collinanderson|Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #23654: test_index_view_with_two_past_questions() raising ValueError

#23654: test_index_view_with_two_past_questions() raising ValueError ---+-- Reporter: skalrynd |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #23655: Update of Tutorial Part 2, Templates section

#23655: Update of Tutorial Part 2, Templates section ---+-- Reporter: andreafagan|Owner: nobody Type: Bug| Status: closed Component: Documentation |

Re: [Django] #23655: Update of Tutorial Part 2, Templates section

#23655: Update of Tutorial Part 2, Templates section ---+ Reporter: andreafagan|Owner: nobody Type: Bug| Status: new Component: Documentation |

[Django] #23655: Update of Tutorial Part 2, Templates section

#23655: Update of Tutorial Part 2, Templates section ---+ Reporter: andreafagan| Owner: nobody Type: Bug| Status: new Component: Documentation |Version: 1.7 Severity: Normal |

Re: [Django] #23654: test_index_view_with_two_past_questions() raising ValueError

#23654: test_index_view_with_two_past_questions() raising ValueError ---+-- Reporter: skalrynd |Owner: nobody Type: Uncategorized | Status: new Component:

[Django] #23654: test_index_view_with_two_past_questions() raising ValueError

#23654: test_index_view_with_two_past_questions() raising ValueError ---+ Reporter: skalrynd | Owner: nobody Type: Uncategorized | Status: new Component: Documentation |Version: 1.7 Severity: Normal

Re: [Django] #23615: Naming a model Check causes Django's check framework to fail with an exception (was: Naming a model Check causes Django's check framework to fail with an acception)

#23615: Naming a model Check causes Django's check framework to fail with an exception --+ Reporter: bramd |Owner: zedr Type: Bug |

Re: [Django] #23615: Naming a model Check causes Django's check framework to fail with an acception

#23615: Naming a model Check causes Django's check framework to fail with an acception --+ Reporter: bramd |Owner: zedr Type: Bug |

Re: [Django] #23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form

#23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form --+ Reporter: macarena |Owner: gchp Type: Cleanup/optimization

Re: [Django] #23615: Naming a model Check causes Django's check framework to fail with an acception

#23615: Naming a model Check causes Django's check framework to fail with an acception --+ Reporter: bramd |Owner: zedr Type: Bug |

Re: [Django] #23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form

#23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form --+ Reporter: macarena |Owner: gchp Type: Cleanup/optimization

Re: [Django] #23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form

#23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form --+ Reporter: macarena |Owner: gchp Type: Cleanup/optimization

Re: [Django] #23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form

#23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form --+ Reporter: macarena |Owner: gchp Type: Cleanup/optimization

Re: [Django] #23629: Migrations doesn't detect changes to db_table

#23629: Migrations doesn't detect changes to db_table -+ Reporter: Naddiseo |Owner: tianyi33 Type: Bug | Status: assigned Component: Migrations

Re: [Django] #23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form

#23595: “add” button for related fields in admin interface should send 'limit_choices_to' parameter to add form --+ Reporter: macarena |Owner: gchp Type: Cleanup/optimization

Re: [Django] #23615: Naming a model Check causes Django's check framework to fail with an acception

#23615: Naming a model Check causes Django's check framework to fail with an acception --+ Reporter: bramd |Owner: zedr Type: Bug |

Re: [Django] #12008: included templates' blocks do not get processed as if they were from the context of the including page

#12008: included templates' blocks do not get processed as if they were from the context of the including page --+ Reporter: tim@… |Owner: mcgeeco Type: Cleanup/optimization

Re: [Django] #12008: included templates' blocks do not get processed as if they were from the context of the including page

#12008: included templates' blocks do not get processed as if they were from the context of the including page --+ Reporter: tim@… |Owner: mcgeeco Type: Cleanup/optimization

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: closed

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: closed

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: closed

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: closed

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: closed

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: assigned

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: assigned

Re: [Django] #12008: included templates' blocks do not get processed as if they were from the context of the including page

#12008: included templates' blocks do not get processed as if they were from the context of the including page --+ Reporter: tim@… |Owner: mcgeeco Type: Cleanup/optimization

Re: [Django] #23622: Subquery doesn't respect order when not bound to a __pk__ field.

#23622: Subquery doesn't respect order when not bound to a __pk__ field. -+- Reporter: ris |Owner: Type: Bug | machinelady Component: Database layer

[Django] #23653: Test failures Windows 7

#23653: Test failures Windows 7 ---+ Reporter: patclaffey | Owner: nobody Type: Bug| Status: new Component: Testing framework |Version: 1.7 Severity: Normal |

Re: [Django] #23652: Database name is not reset after destroying test database

#23652: Database name is not reset after destroying test database -+- Reporter: Bjarkias |Owner: nobody Type: Bug | Status: new

Re: [Django] #23652: Database name is not reset after destroying test database

#23652: Database name is not reset after destroying test database -+- Reporter: Bjarkias |Owner: nobody Type: Uncategorized| Status: new

[Django] #23652: Database name is not reset after destroying test database

#23652: Database name is not reset after destroying test database ---+-- Reporter: Bjarkias | Owner: nobody Type: Uncategorized | Status: new Component: Testing framework |Version:

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

#23640: StaticLiveServerTestCase does not properly respect data migrations -+- Reporter: eldamir |Owner: gchp Type: Bug | Status: assigned

Re: [Django] #23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3

#23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3 -+- Reporter: rhertzog |Owner: nobody Type: Bug |

Re: [Django] #23615: Naming a model Check causes Django's check framework to fail with an acception

#23615: Naming a model Check causes Django's check framework to fail with an acception --+ Reporter: bramd |Owner: zedr Type: Bug |

Re: [Django] #23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3

#23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3 -+- Reporter: rhertzog |Owner: nobody Type: Bug |

Re: [Django] #23615: Naming a model Check causes Django's check framework to fail with an acception

#23615: Naming a model Check causes Django's check framework to fail with an acception --+ Reporter: bramd |Owner: zedr Type: Bug |

Re: [Django] #23606: RequestFactory does not have a trace method.

#23606: RequestFactory does not have a trace method. ---+ Reporter: KevinEtienne |Owner: zedr Type: New feature| Status: assigned Component: Testing

[Django] #23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3

#23651: fixtures.tests.FixtureLoadingTests.test_loading_and_dumping fails with Python 3 + Reporter: rhertzog| Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23638: Django raises exceptions on unicode in cookies/headers

#23638: Django raises exceptions on unicode in cookies/headers -+- Reporter: defcube |Owner: nobody Type: Bug | Status: closed

[Django] #23650: System checks framework runs 3 times while performing manage.py test

#23650: System checks framework runs 3 times while performing manage.py test --+-- Reporter: coagulant | Owner: nobody Type: Bug | Status: new Component: Core (System checks)

Re: [Django] #23638: Django raises exceptions on unicode in cookies/headers

#23638: Django raises exceptions on unicode in cookies/headers -+- Reporter: defcube |Owner: nobody Type: Bug | Status: closed