Re: [Django] #15602: Using get_readonly_fields and StackedInline/TabularInline admin objects doesn't allow creating new objects, immutible existing objects

2015-01-11 Thread Django
#15602: Using get_readonly_fields and StackedInline/TabularInline admin objects doesn't allow creating new objects, immutible existing objects -+ Reporter: bradwhittington |Owner: nobody Type:

Re: [Django] #24089: Misleading error raised during system check related to ModelAdmin

2015-01-11 Thread Django
#24089: Misleading error raised during system check related to ModelAdmin -+- Reporter: okrutny |Owner: Type: | arcturusannamalai Cleanup/optimization

Re: [Django] #24133: DeleteView success_url = reverse_lazy(...) bug for non ascii urls

2015-01-11 Thread Django
#24133: DeleteView success_url = reverse_lazy(...) bug for non ascii urls -+- Reporter: laurentpayot |Owner: nobody Type: Bug | Status: new Co

Re: [Django] #24133: DeleteView success_url = reverse_lazy(...) bug for non ascii urls

2015-01-11 Thread Django
#24133: DeleteView success_url = reverse_lazy(...) bug for non ascii urls -+- Reporter: laurentpayot |Owner: nobody Type: Bug | Status: new Co

[Django] #24133: DeleteView success_url = reverse_lazy(...) bug for non ascii urls

2015-01-11 Thread Django
#24133: DeleteView success_url = reverse_lazy(...) bug for non ascii urls --+ Reporter: laurentpayot | Owner: nobody Type: Bug | Status: new Component: Internationaliza

Re: [Django] #24075: Can't migrate contenttypes and auth to zero

2015-01-11 Thread Django
#24075: Can't migrate contenttypes and auth to zero -+ Reporter: apollo13 |Owner: nobody Type: Bug | Status: new Component: Migrations |

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

2015-01-11 Thread Django
#24100: Make `post_migrate` dispatch the migration plan. -+- Reporter: charettes|Owner: charettes Type: New feature | Status: new Component: Migrations |

Re: [Django] #24132: auth_permission name field is too short

2015-01-11 Thread Django
#24132: auth_permission name field is too short ---+-- Reporter: mark0978 |Owner: nobody Type: Uncategorized | Status: closed Component: contrib.auth |

Re: [Django] #24118: Add --debug-sql option to tests to print SQL queries on failure

2015-01-11 Thread Django
#24118: Add --debug-sql option to tests to print SQL queries on failure -+- Reporter: mjtamlyn |Owner: mjtamlyn Type: New feature | Status: new Co

Re: [Django] #24132: auth_permission name field is too short

2015-01-11 Thread Django
#24132: auth_permission name field is too short ---+-- Reporter: mark0978 |Owner: nobody Type: Uncategorized | Status: new Component: contrib.auth |

[Django] #24132: auth_permission name field is too short

2015-01-11 Thread Django
#24132: auth_permission name field is too short ---+ Reporter: mark0978 | Owner: nobody Type: Uncategorized | Status: new Component: contrib.auth |Version: 1.7 Severity: Normal | Keywords:

Re: [Django] #20377: BinaryField doesn't work on MySQL and Python 3

2015-01-11 Thread Django
#20377: BinaryField doesn't work on MySQL and Python 3 -+- Reporter: aaugustin|Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #20377: BinaryField doesn't work on MySQL and Python 3

2015-01-11 Thread Django
#20377: BinaryField doesn't work on MySQL and Python 3 -+- Reporter: aaugustin|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #24031: Implement a Case/When expression

2015-01-11 Thread Django
#24031: Implement a Case/When expression -+- Reporter: jarshwah |Owner: michalmo Type: New feature | Status: assigned Component: Database layer

Re: [Django] #24115: Bcrypt hashers don't implement must_update

2015-01-11 Thread Django
#24115: Bcrypt hashers don't implement must_update ---+-- Reporter: cancan101 |Owner: nobody Type: Bug| Status: new Component: Uncategorized |

Re: [Django] #24115: Bcrypt hashers don't implement must_update

2015-01-11 Thread Django
#24115: Bcrypt hashers don't implement must_update ---+-- Reporter: cancan101 |Owner: nobody Type: Bug| Status: new Component: Uncategorized |

Re: [Django] #24131: Docs: Shouldn't have ligatures enabled for monospace text

2015-01-11 Thread Django
#24131: Docs: Shouldn't have ligatures enabled for monospace text -+- Reporter: davidfstr|Owner: nobody Type: | Status: closed Cleanup/o

Re: [Django] #24131: Docs: Shouldn't have ligatures enabled for monospace text

2015-01-11 Thread Django
#24131: Docs: Shouldn't have ligatures enabled for monospace text -+- Reporter: davidfstr|Owner: nobody Type: | Status: new Cleanup/opti

Re: [Django] #24130: Docs: FastCGI deployment: flup6 as alternative to flup

2015-01-11 Thread Django
#24130: Docs: FastCGI deployment: flup6 as alternative to flup ---+-- Reporter: davidfstr |Owner: nobody Type: Bug| Status: closed Component: Documentation

[Django] #24131: Docs: Shouldn't have ligatures enabled for monospace text

2015-01-11 Thread Django
#24131: Docs: Shouldn't have ligatures enabled for monospace text --+ Reporter: davidfstr | Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |Version: 1.7

Re: [Django] #24129: Add indicator that migrations are rendering model states before applying the first migration

2015-01-11 Thread Django
#24129: Add indicator that migrations are rendering model states before applying the first migration -+- Reporter: MarkusH |Owner: MarkusH Type: New feature |

Re: [Django] #24123: LookupError when rolling back migrations

2015-01-11 Thread Django
#24123: LookupError when rolling back migrations -+ Reporter: MarkusH |Owner: MarkusH Type: Bug | Status: new Component: Migrations |

Re: [Django] #24130: Docs: FastCGI deployment: flup6 as alternative to flup

2015-01-11 Thread Django
#24130: Docs: FastCGI deployment: flup6 as alternative to flup ---+-- Reporter: davidfstr |Owner: nobody Type: Bug| Status: new Component: Documentation |

Re: [Django] #24130: Docs: FastCGI deployment: flup6 as alternative to flup

2015-01-11 Thread Django
#24130: Docs: FastCGI deployment: flup6 as alternative to flup ---+-- Reporter: davidfstr |Owner: nobody Type: Bug| Status: new Component: Documentation |

Re: [Django] #23913: = comparison does work in templates although it shouldn't

2015-01-11 Thread Django
#23913: = comparison does work in templates although it shouldn't -+- Reporter: googol7 |Owner: Type: | olasitarska Cleanup/optimization |

[Django] #24130: Docs: FastCGI deployment: flup6 as alternative to flup

2015-01-11 Thread Django
#24130: Docs: FastCGI deployment: flup6 as alternative to flup ---+ Reporter: davidfstr | Owner: nobody Type: Bug| Status: new Component: Documentation |Version: master Severity: Normal

Re: [Django] #24053: Drop IE6/7 admin CSS/icons

2015-01-11 Thread Django
#24053: Drop IE6/7 admin CSS/icons --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.admin |

Re: [Django] #23878: Query object/expression documentation needs to tidied

2015-01-11 Thread Django
#23878: Query object/expression documentation needs to tidied --+ Reporter: EvilDMP |Owner: ngzhian Type: Cleanup/optimization | Status: assigned Compon

Re: [Django] #23913: = comparison does work in templates although it shouldn't

2015-01-11 Thread Django
#23913: = comparison does work in templates although it shouldn't -+- Reporter: googol7 |Owner: Type: | olasitarska Cleanup/optimization |

Re: [Django] #20380: MySQL doesn't support dates below 1000 on Python 3.2

2015-01-11 Thread Django
#20380: MySQL doesn't support dates below 1000 on Python 3.2 -+- Reporter: aaugustin|Owner: nobody Type: | Status: closed Cleanup/optimi

Re: [Django] #20380: MySQL doesn't support dates below 1000 on Python 3.2

2015-01-11 Thread Django
#20380: MySQL doesn't support dates below 1000 on Python 3.2 -+- Reporter: aaugustin|Owner: nobody Type: | Status: new Cleanup/optimizat

[Django] #24129: Add indicator that migrations are rendering model states before applying the first migration

2015-01-11 Thread Django
#24129: Add indicator that migrations are rendering model states before applying the first migration +- Reporter: MarkusH | Owner: MarkusH Type: New feature | Status: new

Re: [Django] #23913: = comparison does work in templates although it shouldn't

2015-01-11 Thread Django
#23913: = comparison does work in templates although it shouldn't -+- Reporter: googol7 |Owner: Type: | olasitarska Cleanup/optimization |

Re: [Django] #24116: Refactor AdminSite.check_dependencies with the checks framework

2015-01-11 Thread Django
#24116: Refactor AdminSite.check_dependencies with the checks framework -+- Reporter: aaugustin|Owner: nobody Type: | Status: new Cleanu

[Django] #24128: Admindocs doesn't account for template loaders

2015-01-11 Thread Django
#24128: Admindocs doesn't account for template loaders -+ Reporter: aaugustin | Owner: nobody Type: Bug| Status: new Component: contrib.

[Django] #24127: Automatically set the current URL namespace based on the URL of the current request

2015-01-11 Thread Django
#24127: Automatically set the current URL namespace based on the URL of the current request -+- Reporter: aaugustin | Owner: nobody Type: New| Status: new featu

[Django] #24126: Consider deprecating the current_app argument of auth views

2015-01-11 Thread Django
#24126: Consider deprecating the current_app argument of auth views -+- Reporter: aaugustin | Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #24125: TemplateDetailView in admindocs requires a single Django templates engine

2015-01-11 Thread Django
#24125: TemplateDetailView in admindocs requires a single Django templates engine -+- Reporter: aaugustin | Owner: nobody Type: Bug| Status: new Com

[Django] #24124: Review the list of default context processors

2015-01-11 Thread Django
#24124: Review the list of default context processors -+- Reporter: aaugustin | Owner: nobody Type: | Status: new Cleanup/optimization |

Re: [Django] #24123: LookupError when rolling back migrations

2015-01-11 Thread Django
#24123: LookupError when rolling back migrations -+ Reporter: MarkusH |Owner: MarkusH Type: Bug | Status: new Component: Migrations |

Re: [Django] #24123: LookupError when rolling back migrations

2015-01-11 Thread Django
#24123: LookupError when rolling back migrations -+-- Reporter: MarkusH |Owner: MarkusH Type: Bug | Status: new Component: Migrations |

[Django] #24123: LookupError when rolling back migrations

2015-01-11 Thread Django
#24123: LookupError when rolling back migrations -+- Reporter: MarkusH | Owner: MarkusH Type: Bug | Status: new Component: Migrations |Version: master Severity: Release blocker

[Django] #24122: Redirect to translated url after setting language

2015-01-11 Thread Django
#24122: Redirect to translated url after setting language -+- Reporter: gbdlin | Owner: nobody Type: Uncategorized| Status: new Component: |Version:

Re: [Django] #24096: GROUP BY on oracle fails with TextField and BinaryField

2015-01-11 Thread Django
#24096: GROUP BY on oracle fails with TextField and BinaryField -+- Reporter: jarshwah |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24109: Provide a way to mark a migration operation as elidable when squashing

2015-01-11 Thread Django
#24109: Provide a way to mark a migration operation as elidable when squashing -+-- Reporter: carljm |Owner: nobody Type: New feature | Status: new Component: Migratio

Re: [Django] #24121: Provide a better repr() experience

2015-01-11 Thread Django
#24121: Provide a better repr() experience ---+ Reporter: kezabelle |Owner: nobody Type: New feature| Status: new Component: Uncategorized | Versio

Re: [Django] #24121: Provide a better repr() experience

2015-01-11 Thread Django
#24121: Provide a better repr() experience ---+ Reporter: kezabelle |Owner: nobody Type: New feature| Status: new Component: Uncategorized | Versio

Re: [Django] #24060: Allow expressions to be used in order_by queryset method

2015-01-11 Thread Django
#24060: Allow expressions to be used in order_by queryset method -+- Reporter: jarshwah |Owner: jarshwah Type: New feature | Status: assigned Comp

[Django] #24121: Provide a better repr() experience

2015-01-11 Thread Django
#24121: Provide a better repr() experience ---+ Reporter: kezabelle | Owner: nobody Type: New feature| Status: new Component: Uncategorized |Version: master Severity: Normal | Keywords: T

[Django] #24120: Backend-agnostic debug information on template loading failures

2015-01-11 Thread Django
#24120: Backend-agnostic debug information on template loading failures -+- Reporter: aaugustin | Owner: nobody Type: Bug| Status: new Component: Te

[Django] #24119: Backend-agnostic tracebacks on template rendering errors

2015-01-11 Thread Django
#24119: Backend-agnostic tracebacks on template rendering errors -+- Reporter: aaugustin | Owner: nobody Type: Bug| Status: new Component: Template

Re: [Django] #24118: Add --debug-sql option to tests to print SQL queries on failure

2015-01-11 Thread Django
#24118: Add --debug-sql option to tests to print SQL queries on failure ---+ Reporter: mjtamlyn |Owner: mjtamlyn Type: New feature| Status: new Component