Re: [Django] #28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore

2017-04-05 Thread Django
#28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore ---+-- Reporter: Thomas Kähn|Owner: nobody Type: Bug| Status: closed Component:

Re: [Django] #28029: Removal of ability to reverse by dotted path found to be very non-DRY

2017-04-05 Thread Django
#28029: Removal of ability to reverse by dotted path found to be very non-DRY --+-- Reporter: Henrik Levkowetz |Owner: nobody Type: Uncategorized | Status: closed

Re: [Django] #28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed

2017-04-05 Thread Django
#28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed -+ Reporter: Richard Barrell |Owner: nobody Type: Bug |

Re: [Django] #28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore

2017-04-05 Thread Django
#28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore ---+-- Reporter: Thomas Kähn|Owner: nobody Type: Bug| Status: closed Component:

Re: [Django] #28019: Django django.db.models.Model.save() logic bit illogical?

2017-04-05 Thread Django
#28019: Django django.db.models.Model.save() logic bit illogical? -+- Reporter: Jacek Kałucki|Owner: nobody Type: Bug | Status: closed

Re: [Django] #28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed

2017-04-05 Thread Django
#28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed -+ Reporter: Richard Barrell |Owner: nobody Type: Bug |

Re: [Django] #27846: refresh_from_db() doesn't clear reverse OneToOneFields

2017-04-05 Thread Django
#27846: refresh_from_db() doesn't clear reverse OneToOneFields -+- Reporter: Keith Hostetler |Owner: Matvey | Kukuy Type: Bug |

Re: [Django] #28029: Removal of ability to reverse by dotted path found to be very non-DRY

2017-04-05 Thread Django
#28029: Removal of ability to reverse by dotted path found to be very non-DRY --+-- Reporter: Henrik Levkowetz |Owner: nobody Type: Uncategorized | Status: closed

Re: [Django] #27985: Converting `Foo.objects.filter(bar=None)` to an `IsNull` too early.

2017-04-05 Thread Django
#27985: Converting `Foo.objects.filter(bar=None)` to an `IsNull` too early. -+- Reporter: Jarek Glowacki |Owner: (none) Type: Bug | Status: new

Re: [Django] #28030: queryset.union count() method throws TypeError

2017-04-05 Thread Django
#28030: queryset.union count() method throws TypeError -+- Reporter: David Binetti|Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed

2017-04-05 Thread Django
#28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed -+-- Reporter: Richard Barrell |Owner: nobody Type: Bug |

[Django] #28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed

2017-04-05 Thread Django
#28031: Documentation for uwsgi deployment mentions buggy uwsgi packages in some distros but not when they were fixed ---+ Reporter: Richard Barrell | Owner: nobody Type: Bug

[Django] #28030: queryset.union count() method throws TypeError

2017-04-05 Thread Django
#28030: queryset.union count() method throws TypeError -+- Reporter: David | Owner: nobody Binetti| Type: Bug| Status: new

[Django] #28029: Removal of ability to reverse by dotted path found to be very non-DRY

2017-04-05 Thread Django
#28029: Removal of ability to reverse by dotted path found to be very non-DRY + Reporter: Henrik Levkowetz | Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #24030: default id field not migrated correctly

2017-04-05 Thread Django
#24030: default id field not migrated correctly +-- Reporter: Brian May |Owner: nobody Type: Bug | Status: new Component: Migrations | Version:

Re: [Django] #28015: Add makemessages --add-location=full|file|never option (was: New argument for makemessages: --add-location=full|file|never)

2017-04-05 Thread Django
#28015: Add makemessages --add-location=full|file|never option -+- Reporter: Ling-Xiao Yang |Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #6989: Inability to define DNS_NAME in django.core.mail results in e-mail messages being rejected or marked as spam

2017-04-05 Thread Django
#6989: Inability to define DNS_NAME in django.core.mail results in e-mail messages being rejected or marked as spam -+- Reporter: Franklin |Owner: heathervm Type: Bug

Re: [Django] #7452: Settings for HTML4 or XHTML output

2017-04-05 Thread Django
#7452: Settings for HTML4 or XHTML output -+- Reporter: Marc Fargas |Owner: nobody Type: New feature | Status: closed Component: Core (Other)

Re: [Django] #27580: add special field for storing content types

2017-04-05 Thread Django
#27580: add special field for storing content types -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

Re: [Django] #28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks

2017-04-05 Thread Django
#28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #28023: Wrong method in SQL query log

2017-04-05 Thread Django
#28023: Wrong method in SQL query log -+- Reporter: erkib|Owner: nobody Type: Bug | Status: closed Component: Database layer |

Re: [Django] #28023: Wrong method in SQL query log

2017-04-05 Thread Django
#28023: Wrong method in SQL query log -+- Reporter: erkib|Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore

2017-04-05 Thread Django
#28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore ---+-- Reporter: Thomas Kähn|Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #27895: Test Client fails to decode json response with unicode characters

2017-04-05 Thread Django
#27895: Test Client fails to decode json response with unicode characters -+- Reporter: Aniruddha Maru |Owner: Aniruddha | Maru Type: Bug

Re: [Django] #27730: Document that template tags with "as" variable assignment don't propogate variables across blocks

2017-04-05 Thread Django
#27730: Document that template tags with "as" variable assignment don't propogate variables across blocks -+- Reporter: Peter Bittner|Owner: kapil Type: |

Re: [Django] #24030: default id field not migrated correctly

2017-04-05 Thread Django
#24030: default id field not migrated correctly +-- Reporter: Brian May |Owner: nobody Type: Bug | Status: new Component: Migrations | Version:

Re: [Django] #28028: Support HTTP_HOST header: 'xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, ...'

2017-04-05 Thread Django
#28028: Support HTTP_HOST header: 'xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx,...' -+- Reporter: Rafael Herrero |Owner: Rafael Solís | Herrero Solís Type: Bug

Re: [Django] #28028: Support HTTP_HOST header: 'xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, ...'

2017-04-05 Thread Django
#28028: Support HTTP_HOST header: 'xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx,...' -+- Reporter: Rafael Herrero |Owner: nobody Solís | Type: Bug |

Re: [Django] #28014: "manage.py makemigrations --check" exits with 0 in case of exception

2017-04-05 Thread Django
#28014: "manage.py makemigrations --check" exits with 0 in case of exception -+- Reporter: Daniel Hahler|Owner: nobody Type: Bug | Status: closed

[Django] #28028: Support HTTP_HOST header: 'xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, ...'

2017-04-05 Thread Django
#28028: Support HTTP_HOST header: 'xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx,...' -+- Reporter: Rafael | Owner: nobody Herrero Solís | Type: Bug|

Re: [Django] #28014: "manage.py makemigrations --check" exits with 0 in case of exception

2017-04-05 Thread Django
#28014: "manage.py makemigrations --check" exits with 0 in case of exception -+- Reporter: Daniel Hahler|Owner: nobody Type: Bug | Status: closed

[Django] #28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore

2017-04-05 Thread Django
#28027: UTF-8 in help_text in models.ManyToManyField doesn't work anymore -+ Reporter: tkaehn | Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #28026: Pillow version > 4.0.0 not recognized

2017-04-05 Thread Django
#28026: Pillow version > 4.0.0 not recognized ---+-- Reporter: voodoo-burger |Owner: nobody Type: Bug| Status: closed Component: Uncategorized |

Re: [Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

[Django] #28026: Pillow version > 4.0.0 not recognized

2017-04-05 Thread Django
#28026: Pillow version > 4.0.0 not recognized -+ Reporter: voodoo-burger | Owner: nobody Type: Bug| Status: new Component: Uncategorized |

Re: [Django] #28013: admin/inlines.js has different functionality from admin/inlines.min.js

2017-04-05 Thread Django
#28013: admin/inlines.js has different functionality from admin/inlines.min.js +-- Reporter: Joseph Solomon |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #28022: pillow not being recognised

2017-04-05 Thread Django
#28022: pillow not being recognised -+- Reporter: fboerman |Owner: nobody Type: Bug | Status: closed Component: Core (System |

Re: [Django] #28021: Add active_login_required decorator

2017-04-05 Thread Django
#28021: Add active_login_required decorator --+-- Reporter: Wim Feijen|Owner: nobody Type: New feature | Status: new Component: contrib.auth |

Re: [Django] #28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks

2017-04-05 Thread Django
#28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #28018: OneToOneField not working with inlineadmin

2017-04-05 Thread Django
#28018: OneToOneField not working with inlineadmin ---+-- Reporter: alex |Owner: nobody Type: Bug| Status: closed Component: contrib.admin |

Re: [Django] #28019: Django django.db.models.Model.save() logic bit illogical?

2017-04-05 Thread Django
#28019: Django django.db.models.Model.save() logic bit illogical? -+- Reporter: Jacek Kałucki|Owner: nobody Type: Bug | Status: new

Re: [Django] #28018: OneToOneField not working with inlineadmin

2017-04-05 Thread Django
#28018: OneToOneField not working with inlineadmin ---+-- Reporter: alex |Owner: nobody Type: Bug| Status: closed Component: contrib.admin |

Re: [Django] #28018: OneToOneField not working with inlineadmin

2017-04-05 Thread Django
#28018: OneToOneField not working with inlineadmin ---+-- Reporter: alex |Owner: nobody Type: Bug| Status: new Component: contrib.admin |

Re: [Django] #28018: OneToOneField not working with inlineadmin

2017-04-05 Thread Django
#28018: OneToOneField not working with inlineadmin ---+-- Reporter: alex |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #28022: pillow not being recognised

2017-04-05 Thread Django
#28022: pillow not being recognised -+- Reporter: fboerman |Owner: nobody Type: Bug | Status: closed Component: Core (System |

Re: [Django] #28025: Typo in the documentation of 1.11 release

2017-04-05 Thread Django
#28025: Typo in the documentation of 1.11 release -+- Reporter: Sudhanshu Mishra |Owner: Sudhanshu | Mishra Type: Uncategorized|

Re: [Django] #28025: Typo in the documentation of 1.11 release

2017-04-05 Thread Django
#28025: Typo in the documentation of 1.11 release -+- Reporter: Sudhanshu Mishra |Owner: Sudhanshu | Mishra Type: Uncategorized|

Re: [Django] #28025: Typo in the documentation of 1.11 release

2017-04-05 Thread Django
#28025: Typo in the documentation of 1.11 release -+- Reporter: Sudhanshu Mishra |Owner: Sudhanshu | Mishra Type: Uncategorized|

Re: [Django] #28025: Typo in the documentation of 1.11 release

2017-04-05 Thread Django
#28025: Typo in the documentation of 1.11 release -+- Reporter: Sudhanshu Mishra |Owner: Sudhanshu | Mishra Type: Uncategorized|

Re: [Django] #28025: Typo in the documentation of 1.11 release

2017-04-05 Thread Django
#28025: Typo in the documentation of 1.11 release -+- Reporter: Sudhanshu Mishra |Owner: Sudhanshu | Mishra Type: Uncategorized|

[Django] #28025: Typo in the documentation of 1.11 release

2017-04-05 Thread Django
#28025: Typo in the documentation of 1.11 release + Reporter: Sudhanshu Mishra | Owner: nobody Type: Uncategorized | Status: assigned Component:

Re: [Django] #28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks

2017-04-05 Thread Django
#28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

[Django] #28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks

2017-04-05 Thread Django
#28024: GEOSCoordSeq performance could be improved significantly by avoiding superfluous checks + Reporter: Sergey Fedoseev | Owner: nobody Type: Cleanup/optimization |

Re: [Django] #27917: Allow ModelAdmin.radio_fields to work with NullBooleanField

2017-04-05 Thread Django
#27917: Allow ModelAdmin.radio_fields to work with NullBooleanField --+ Reporter: Jerome Leclanche |Owner: Musen Type: Cleanup/optimization | Status: assigned

[Django] #28023: Wrong method in SQL query log

2017-04-05 Thread Django
#28023: Wrong method in SQL query log -+- Reporter: erkib | Owner: nobody Type: Bug| Status: new Component: Database |Version: 1.11

Re: [Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

[Django] #28022: pillow not being recognised

2017-04-05 Thread Django
#28022: pillow not being recognised + Reporter: fboerman | Owner: nobody Type: Bug | Status: new Component: Core (System

Re: [Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #28017: Add option to specify a different secret to PasswordResetTokenGenerator

2017-04-05 Thread Django
#28017: Add option to specify a different secret to PasswordResetTokenGenerator --+-- Reporter: Jann Haber|Owner: Jann Haber Type: New feature | Status: assigned

[Django] #28021: Add active_login_required decorator

2017-04-05 Thread Django
#28021: Add active_login_required decorator + Reporter: Wim Feijen| Owner: nobody Type: New feature | Status: new Component: contrib.auth |Version:

Re: [Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

[Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) + Reporter: Sergey Fedoseev | Owner: nobody Type: Cleanup/optimization | Status:

Re: [Django] #28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons)

2017-04-05 Thread Django
#28020: make GEOSGeometry.json use OGRGeometry.json again (for performance reasons) -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #27998: LogEntry messages do not list m2m fields that were changed when an object is changed via ModelAdmin

2017-04-05 Thread Django
#27998: LogEntry messages do not list m2m fields that were changed when an object is changed via ModelAdmin ---+ Reporter: ljsjl |Owner: ljsjl Type: Bug|

[Django] #28019: Django django.db.models.Model.save() logic bit illogical?

2017-04-05 Thread Django
#28019: Django django.db.models.Model.save() logic bit illogical? -+- Reporter: Jacek | Owner: nobody Kałucki| Type: Bug| Status: