Re: [Django] #26376: Explain what "searching for a list of template names" means in TemplateResponse.Mixin.get_template_names() docs.

2016-03-20 Thread Django
#26376: Explain what "searching for a list of template names" means in TemplateResponse.Mixin.get_template_names() docs. --+ Reporter: guettli |Owner: nobody Type: Cleanup/opti

Re: [Django] #26384: migrations fail with Python 2.7 and Django > 1.9

2016-03-20 Thread Django
#26384: migrations fail with Python 2.7 and Django > 1.9 +-- Reporter: brian |Owner: nobody Type: Bug | Status: new Component: Migrations | Ve

[Django] #26384: migrations fail with Python 2.7 and Django > 1.9

2016-03-20 Thread Django
#26384: migrations fail with Python 2.7 and Django > 1.9 + Reporter: brian | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.9 Severity: Normal | Keywords: Triag

Re: [Django] #26382: Improve Storage and FileField

2016-03-20 Thread Django
#26382: Improve Storage and FileField -+- Reporter: cristianocca |Owner: nobody Type: | Status: new Cleanup/optimization |

Re: [Django] #26382: Improve Storage and FileField

2016-03-20 Thread Django
#26382: Improve Storage and FileField -+- Reporter: cristianocca |Owner: nobody Type: | Status: new Cleanup/optimization |

Re: [Django] #26383: Incomplete/incorrect documentation about using wsgi with Apache when project using virtualenv

2016-03-20 Thread Django
#26383: Incomplete/incorrect documentation about using wsgi with Apache when project using virtualenv -+- Reporter: zshimanchik |Owner: nobody Type: |

[Django] #26383: Incomplete/incorrect documentation about using wsgi with Apache when project using virtualenv

2016-03-20 Thread Django
#26383: Incomplete/incorrect documentation about using wsgi with Apache when project using virtualenv -+- Reporter: zshimanchik | Owner: nobody Type: | Status: new Clea

Re: [Django] #26378: Incorrect behavior in GenericIPAddressField with protocol='both', unpack_ipv4=False

2016-03-20 Thread Django
#26378: Incorrect behavior in GenericIPAddressField with protocol='both', unpack_ipv4=False -+- Reporter: bshen|Owner: | AmineYaiche Type:

[Django] #26382: Improve Storage and FileField

2016-03-20 Thread Django
#26382: Improve Storage and FileField --+--- Reporter: cristianocca | Owner: nobody Type: Cleanup/optimization | Status: new Component: File uploads/storage |Version: 1.9 Severity:

Re: [Django] #26355: Add support for PostgreSQL's array_append to ArrayField

2016-03-20 Thread Django
#26355: Add support for PostgreSQL's array_append to ArrayField --+ Reporter: graup |Owner: Type: New feature | Status: new Component: contrib.postgres

Re: [Django] #26378: Incorrect behavior in GenericIPAddressField with protocol='both', unpack_ipv4=False

2016-03-20 Thread Django
#26378: Incorrect behavior in GenericIPAddressField with protocol='both', unpack_ipv4=False -+- Reporter: bshen|Owner: | AmineYaiche Type:

Re: [Django] #26366: Implicitly save related models as needed instead of raising "unsaved related objects error" on Model.save()

2016-03-20 Thread Django
#26366: Implicitly save related models as needed instead of raising "unsaved related objects error" on Model.save() -+- Reporter: aki33524 |Owner: nobody Type: New feature

[Django] #26377: Allow migrations to specify another migration they should run before. (Kind of like `dependencies` in reverse.)

2016-03-20 Thread Django
#26377: Allow migrations to specify another migration they should run before. (Kind of like `dependencies` in reverse.) -+ Reporter: morganwahl | Owner: nobody Type: New feature | Status: new Component: Migrations

Re: [Django] #26372: admin_order_field ignored when shadowing model field

2016-03-20 Thread Django
#26372: admin_order_field ignored when shadowing model field ---+-- Reporter: julianandrews |Owner: nobody Type: Bug| Status: new Component: contrib.admin |

Re: [Django] #25617: Disallow usernames that differ only in case in UserCreationForm

2016-03-20 Thread Django
#25617: Disallow usernames that differ only in case in UserCreationForm --+ Reporter: timgraham |Owner: nmundar Type: Cleanup/optimization | Status: assigned

Re: [Django] #26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value

2016-03-20 Thread Django
#26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value --+ Reporter: berkerpeksag |Owner: berkerpeksag Type: Bug | Status: assigned Compon

Re: [Django] #26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value

2016-03-20 Thread Django
#26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value --+-- Reporter: berkerpeksag |Owner: nobody Type: Bug | Status: new Component: contrib

Re: [Django] #26371: please add section to tutorial for switching over to and using postgres

2016-03-20 Thread Django
#26371: please add section to tutorial for switching over to and using postgres ---+-- Reporter: beckastar |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value

2016-03-20 Thread Django
#26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value --+-- Reporter: berkerpeksag |Owner: nobody Type: Bug | Status: new Component: contrib

[Django] #26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value

2016-03-20 Thread Django
#26381: UserCreationForm cannot be reused with a custom USERNAME_FIELD value --+ Reporter: berkerpeksag | Owner: nobody Type: Bug | Status: new Component: contrib.auth |Version: 1.9 Severity: Norm

Re: [Django] #26265: RendererMixin id_for_label causes HTML id uniqueness violation

2016-03-20 Thread Django
#26265: RendererMixin id_for_label causes HTML id uniqueness violation -+ Reporter: scoenye |Owner: tedmx Type: Bug | Status: assigned Component: Forms|

Re: [Django] #26366: models.Model.save() method improvement.

2016-03-20 Thread Django
#26366: models.Model.save() method improvement. -+- Reporter: aki33524 |Owner: nobody Type: New feature | Status: new Component: Database layer

Re: [Django] #26364: Updating an object in a queryset with save() leads to bug using that queryset as a lookup filter

2016-03-20 Thread Django
#26364: Updating an object in a queryset with save() leads to bug using that queryset as a lookup filter -+- Reporter: jonathan-golorry |Owner: nobody Type: Bug |