Re: [Django] #24341: Subclasses of django.contrib.postgres.forms.ranges.BaseRangeField should have more specific error messages

#24341: Subclasses of django.contrib.postgres.forms.ranges.BaseRangeField should have more specific error messages --+-- Reporter: void |Owner: Type: New feature |

Re: [Django] #24291: Migrations fail with unused swappable model

#24291: Migrations fail with unused swappable model -+- Reporter: knbk |Owner: knbk Type: Bug | Status: assigned Component:

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24361: The doc is not right w.r.t. LOGGING overwriting.

#24361: The doc is not right w.r.t. LOGGING overwriting. ---+ Reporter: Tuttle |Owner: nobody Type: Bug| Status: new Component: Documentation |

[Django] #24362: Migration test failure on Oracle

#24362: Migration test failure on Oracle ---+ Reporter: shaib| Owner: nobody Type: Bug | Status: new Component: Migrations |

[Django] #24361: The doc is not right w.r.t. LOGGING overwriting.

#24361: The doc is not right w.r.t. LOGGING overwriting. ---+ Reporter: Tuttle | Owner: nobody Type: Bug| Status: new Component: Documentation |Version: master Severity: Normal |

Re: [Django] #24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL

#24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL -+- Reporter: JorisBenschop|Owner: shaib Type: Bug | Status:

Re: [Django] #24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL

#24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL -+- Reporter: JorisBenschop|Owner: shaib Type: Bug | Status:

Re: [Django] #24360: when LocaleMiddleware activated, no error page with traceback and error message in logger

#24360: when LocaleMiddleware activated, no error page with traceback and error message in logger ---+-- Reporter: mishust|Owner: nobody Type: Bug| Status:

Re: [Django] #24360: when LocaleMiddleware activated, no error page with traceback and error message in logger

#24360: when LocaleMiddleware activated, no error page with traceback and error message in logger ---+-- Reporter: mishust|Owner: nobody Type: Bug| Status:

[Django] #24360: when LocaleMiddleware activated, no error page with traceback and error message in logger

#24360: when LocaleMiddleware activated, no error page with traceback and error message in logger ---+ Reporter: mishust| Owner: nobody Type: Bug| Status: new Component: Uncategorized |Version:

Re: [Django] #24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL

#24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL -+- Reporter: JorisBenschop|Owner: shaib Type: Bug | Status:

Re: [Django] #24359: "Http exceptions are provided in django.http" links to a page that does not list or link to HTTP exceptions

#24359: "Http exceptions are provided in django.http" links to a page that does not list or link to HTTP exceptions ---+-- Reporter: pydanny|Owner: nobody Type: Bug|

Re: [Django] #24359: "Http exceptions are provided in django.http" links to a page that does not list or link to HTTP exceptions

#24359: "Http exceptions are provided in django.http" links to a page that does not list or link to HTTP exceptions ---+-- Reporter: pydanny|Owner: nobody Type: Bug|

[Django] #24359: "Http exceptions are provided in django.http" links to a page that does not list or link to HTTP exceptions

#24359: "Http exceptions are provided in django.http" links to a page that does not list or link to HTTP exceptions ---+--- Reporter: pydanny| Owner: nobody Type: Bug| Status: new Component:

[Django] #24358: Incorrect code-block for console sessions

#24358: Incorrect code-block for console sessions + Reporter: timgraham | Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #24354: Migrations that rename subclasses cause problems with relations

#24354: Migrations that rename subclasses cause problems with relations ---+ Reporter: MatthewWilkes |Owner: nobody Type: Bug| Status: new Component: Migrations

Re: [Django] #23811: Document how to use git bisect with runtests.py

#23811: Document how to use git bisect with runtests.py -+- Reporter: timgraham|Owner: bmispelon Type: | Status: assigned

Re: [Django] #24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL

#24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL -+- Reporter: JorisBenschop|Owner: nobody Type: Bug | Status: new

Re: [Django] #24354: Migrations that rename subclasses cause problems with relations

#24354: Migrations that rename subclasses cause problems with relations ---+-- Reporter: MatthewWilkes |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #24357: Renaming Foreignkey field leaves index

#24357: Renaming Foreignkey field leaves index +-- Reporter: poirier |Owner: nobody Type: Bug | Status: closed Component: Migrations | Version:

[Django] #24357: Renaming Foreignkey field leaves index

#24357: Renaming Foreignkey field leaves index + Reporter: poirier | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.7 Severity: Normal | Keywords: Triage Stage:

Re: [Django] #24354: Migrations that rename subclasses cause problems with relations

#24354: Migrations that rename subclasses cause problems with relations ---+-- Reporter: MatthewWilkes |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #24100: Make `post_migrate` dispatch the migration plan.

#24100: Make `post_migrate` dispatch the migration plan. -+ Reporter: charettes|Owner: MarkusH Type: New feature | Status: assigned Component: Migrations |

Re: [Django] #24356: Link in 403 Forbidden "CSRF verification failed." page has broken doc link

#24356: Link in 403 Forbidden "CSRF verification failed." page has broken doc link ---+-- Reporter: aliteralmind |Owner: nobody Type: Bug| Status: closed

[Django] #24356: Link in 403 Forbidden "CSRF verification failed." page has broken doc link

#24356: Link in 403 Forbidden "CSRF verification failed." page has broken doc link ---+ Reporter: aliteralmind | Owner: nobody Type: Bug| Status: new Component: Documentation |Version: 1.7

Re: [Django] #24347: parameter 'widget' of BoundField.as_widget is ignored

#24347: parameter 'widget' of BoundField.as_widget is ignored -+- Reporter: srkunze |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24355: Cannot use Django 1.8a1 with mysql.connector.python (Oracle's official mysql connector.)

#24355: Cannot use Django 1.8a1 with mysql.connector.python (Oracle's official mysql connector.) -+- Reporter: ubill|Owner: nobody Type: Uncategorized|

Re: [Django] #24347: parameter 'widget' of BoundField.as_widget is ignored

#24347: parameter 'widget' of BoundField.as_widget is ignored -+- Reporter: srkunze |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24291: Migrations fail with unused swappable model

#24291: Migrations fail with unused swappable model -+- Reporter: knbk |Owner: knbk Type: Bug | Status: assigned Component: Migrations |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

#24324: Crashes when project path or path to Django install contains a non-ascii character -+- Reporter: notsqrt |Owner: timgraham Type: Bug |

Re: [Django] #24290: postgres_tests fail ungracefully if psycopg2 isn't installed

#24290: postgres_tests fail ungracefully if psycopg2 isn't installed -+- Reporter: aaugustin|Owner: Type: | joelburton Cleanup/optimization

Re: [Django] #24290: postgres_tests fail ungracefully if psycopg2 isn't installed

#24290: postgres_tests fail ungracefully if psycopg2 isn't installed -+- Reporter: aaugustin|Owner: Type: | joelburton Cleanup/optimization

Re: [Django] #24335: DateRange and friends require psycopg2 >= 2.5

#24335: DateRange and friends require psycopg2 >= 2.5 -+- Reporter: claudep |Owner: timgraham Type: | Status: closed

Re: [Django] #24335: DateRange and friends require psycopg2 >= 2.5

#24335: DateRange and friends require psycopg2 >= 2.5 -+- Reporter: claudep |Owner: timgraham Type: | Status: closed

Re: [Django] #24355: Cannot use Django 1.8a1 with mysql.connector.python (Oracle's official mysql connector.)

#24355: Cannot use Django 1.8a1 with mysql.connector.python (Oracle's official mysql connector.) -+- Reporter: ubill|Owner: nobody Type: Uncategorized|

Re: [Django] #24351: RunPython/RunSQL operations in contrib migrations and multi-db routers.

#24351: RunPython/RunSQL operations in contrib migrations and multi-db routers. -+- Reporter: loic |Owner: nobody Type: Uncategorized| Status: new

[Django] #24355: Cannot use Django 1.8a1 with mysql.connector.python (Oracle's official mysql connector.)

#24355: Cannot use Django 1.8a1 with mysql.connector.python (Oracle's official mysql connector.) --+--- Reporter: ubill | Owner: nobody Type: Uncategorized | Status:

Re: [Django] #24354: Migrations that rename subclasses cause problems with relations

#24354: Migrations that rename subclasses cause problems with relations ---+-- Reporter: MatthewWilkes |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #24351: RunPython/RunSQL operations in contrib migrations and multi-db routers.

#24351: RunPython/RunSQL operations in contrib migrations and multi-db routers. -+- Reporter: loic |Owner: nobody Type: Uncategorized| Status: new