Re: [Django] #13666: Updates with F objects on decimal fields raise MySQL warnings

#13666: Updates with F objects on decimal fields raise MySQL warnings -+- Reporter: KyleMac |Owner: nobody Type: Bug | Status: new Compon

Re: [Django] #24235: Deprecate is_usable attribute on template loaders?

#24235: Deprecate is_usable attribute on template loaders? --+ Reporter: prestontimmons|Owner: nobody Type: Cleanup/optimization | Status: new Component: Tem

Re: [Django] #24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3)

#24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3) -+- Reporter: hheimbuerger |Owner: nobody Type: Bug | Status: new Compo

Re: [Django] #6785: QuerySet.get() should only attempt to fetch a limited number of rows

#6785: QuerySet.get() should only attempt to fetch a limited number of rows -+- Reporter: deadwisdom |Owner: nobody Type: | Status: new Cl

Re: [Django] #24218: Use sub-query in ORM when distinct and order_by columns do not match

#24218: Use sub-query in ORM when distinct and order_by columns do not match -+- Reporter: miki725 |Owner: nobody Type: New feature | Status: new

Re: [Django] #24218: Use sub-query in ORM when distinct and order_by columns do not match

#24218: Use sub-query in ORM when distinct and order_by columns do not match -+- Reporter: miki725 |Owner: nobody Type: New feature | Status: new

Re: [Django] #24233: group-by column construction is broken

#24233: group-by column construction is broken -+- Reporter: megatrump|Owner: nobody Type: Bug | Status: closed Component: Database layer

[Django] #24235: Deprecate is_usable attribute on template loaders?

#24235: Deprecate is_usable attribute on template loaders? -+ Reporter: prestontimmons | Owner: nobody Type: Uncategorized| Status: new Component: Template system |Version: master Severity: Normal

[Django] #24234: Create Context object in a separate method

#24234: Create Context object in a separate method -+--- Reporter: AlexHill | Owner: nobody Type: Uncategorized| Status: new Component: Template system |Version: 1.8alpha1 Severity: Normal

Re: [Django] #24215: Refactor of lazy model operations

#24215: Refactor of lazy model operations -+- Reporter: AlexHill |Owner: nobody Type: | Status: new Cleanup/optimization |

[Django] #24233: group-by column construction is broken

#24233: group-by column construction is broken --+--- Reporter: megatrump | Owner: nobody Type: Bug | Status: new Component: Database layer (models, ORM) |

Re: [Django] #17617: Middleware Loader swallows useful stacktraces

#17617: Middleware Loader swallows useful stacktraces --+ Reporter: davedash |Owner: nobody Type: Cleanup/optimization | Status: closed Component: Core

Re: [Django] #24231: Regression in availability of `_meta.get_field()` before app registry is fully populated

#24231: Regression in availability of `_meta.get_field()` before app registry is fully populated -+- Reporter: carljm |Owner: nobody Type: Bug |

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

#14030: Use F() objects in aggregates(), annotates() and values() -+- Reporter: delfick |Owner: jarshwah Type: New feature | Status: closed Compo

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

#14030: Use F() objects in aggregates(), annotates() and values() -+- Reporter: delfick |Owner: jarshwah Type: New feature | Status: closed Compo

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

#24060: Allow expressions to be used in order_by queryset method -+- Reporter: jarshwah |Owner: jarshwah Type: New feature | Status: closed Compon

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

#14030: Use F() objects in aggregates(), annotates() and values() -+- Reporter: delfick |Owner: jarshwah Type: New feature | Status: closed Compo

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

#14030: Use F() objects in aggregates(), annotates() and values() -+- Reporter: delfick |Owner: jarshwah Type: New feature | Status: closed Compo

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

#24060: Allow expressions to be used in order_by queryset method -+- Reporter: jarshwah |Owner: jarshwah Type: New feature | Status: closed Compon

[Django] #24232: Add conditional expressions to block tag

#24232: Add conditional expressions to block tag -+ Reporter: giuliettamasina | Owner: nobody Type: New feature | Status: new Component: Template system |Version: master Severity: Normal

Re: [Django] #24231: Regression in availability of `_meta.get_field()` before app registry is fully populated

#24231: Regression in availability of `_meta.get_field()` before app registry is fully populated -+- Reporter: carljm |Owner: nobody Type: Bug |

Re: [Django] #24223: SessionMiddleware tests leaving Session objects in database

#24223: SessionMiddleware tests leaving Session objects in database --+ Reporter: matt-leach|Owner: nobody Type: Cleanup/optimization | Status: new Compon

Re: [Django] #24223: SessionMiddleware tests leaving Session objects in database

#24223: SessionMiddleware tests leaving Session objects in database -+- Reporter: matt-leach |Owner: matt- Type: | leach Cleanup/optimization

[Django] #24231: Regression in availability of `_meta.get_field()` before app registry is fully populated

#24231: Regression in availability of `_meta.get_field()` before app registry is fully populated -+- Reporter: carljm | Owner: nobody Type: Bug| Status: new

Re: [Django] #24226: Need to be able to change "(None)" display for null fields in Django admin

#24226: Need to be able to change "(None)" display for null fields in Django admin --+ Reporter: meesterguyperson |Owner: nobody Type: New feature | Status: new Co

Re: [Django] #24230: Filter: language_translated returns translated name of language

#24230: Filter: language_translated returns translated name of language -+- Reporter: tricoder42 |Owner: nobody Type: New feature | Status: new Comp

Re: [Django] #24229: forms.IntegerField.clean() fails to clean float objects that are integers

#24229: forms.IntegerField.clean() fails to clean float objects that are integers -+ Reporter: jdufresne|Owner: nobody Type: New feature | Status: new Component: Forms

Re: [Django] #24137: Reason phrases use all upper case by default; standard suggests title case

#24137: Reason phrases use all upper case by default; standard suggests title case -+- Reporter: jdufresne|Owner: nobody Type: | Status:

Re: [Django] #24229: forms.IntegerField.clean() fails to clean float objects that are integers

#24229: forms.IntegerField.clean() fails to clean float objects that are integers -+-- Reporter: jdufresne|Owner: nobody Type: New feature | Status: new Component: Form

Re: [Django] #24181: THOUSAND_SEPARATOR strings are reversed

#24181: THOUSAND_SEPARATOR strings are reversed ---+ Reporter: hannal |Owner: varun Type: Bug| Status: assigned Component: Utilities | Version: 1.7

Re: [Django] #24228: Signals have unclear & inconsistent transaction handling

#24228: Signals have unclear & inconsistent transaction handling -+- Reporter: Gaffney |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

#23273: MigrationRecorder does not obey db_router allow_migrate rules + Reporter: froomzy |Owner: nobody Type: Bug | Status: new Component: Migrations |

[Django] #24230: Filter: language_translated returns translated name of language

#24230: Filter: language_translated returns translated name of language -+- Reporter: tricoder42 | Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #6785: QuerySet.get() should only attempt to fetch a limited number of rows

#6785: QuerySet.get() should only attempt to fetch a limited number of rows -+- Reporter: deadwisdom |Owner: nobody Type: | Status: new Cl

Re: [Django] #6785: QuerySet.get() should only attempt to fetch a limited number of rows

#6785: QuerySet.get() should only attempt to fetch a limited number of rows -+- Reporter: deadwisdom |Owner: nobody Type: | Status: new Cl

Re: [Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many -+- Reporter: coldmind |Owner: coldmind Type: | Sta

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

#23273: MigrationRecorder does not obey db_router allow_migrate rules + Reporter: froomzy |Owner: nobody Type: Bug | Status: new Component: Migrations |

Re: [Django] #12500: Support for MySQL Connector/Python

#12500: Support for MySQL Connector/Python -+- Reporter: geertjanvdk |Owner: nobody Type: New feature | Status: closed Component: Database layer

Re: [Django] #5745: MySQL Collations/Charsets and Engines

#5745: MySQL Collations/Charsets and Engines -+- Reporter: Armin Ronacher |Owner: nobody Type: New feature | Status: new Component: Database layer

Re: [Django] #24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3)

#24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3) -+- Reporter: hheimbuerger |Owner: nobody Type: Bug | Status: new Compo

Re: [Django] #16859: CSRF Improvements

#16859: CSRF Improvements --+ Reporter: PaulM |Owner: PaulM Type: Cleanup/optimization | Status: new Component: CSRF |

Re: [Django] #24224: sqlmigrate is slow

#24224: sqlmigrate is slow -+- Reporter: TorstenRottmann |Owner: nobody Type: | Status: new Cleanup/optimization | Component:

Re: [Django] #24209: Incorrectly formatted Content-Disposition headers may cause error.

#24209: Incorrectly formatted Content-Disposition headers may cause error. ---+- Reporter: tomchristie|Owner: raulcd Type: Bug| Status: closed Component: HTTP

Re: [Django] #24209: Incorrectly formatted Content-Disposition headers may cause error.

#24209: Incorrectly formatted Content-Disposition headers may cause error. ---+- Reporter: tomchristie|Owner: raulcd Type: Bug| Status: closed Component: HTTP

[Django] #24229: forms.IntegerField.clean() fails to clean float objects that are integers

#24229: forms.IntegerField.clean() fails to clean float objects that are integers -+ Reporter: jdufresne| Owner: nobody Type: New feature | Status: new Component: Forms|Version: master Severity:

Re: [Django] #12500: Support for MySQL Connector/Python

#12500: Support for MySQL Connector/Python -+- Reporter: geertjanvdk |Owner: nobody Type: New feature | Status: new Component: Database layer

Re: [Django] #24223: SessionMiddleware tests leaving Session objects in database

#24223: SessionMiddleware tests leaving Session objects in database --+ Reporter: matt-leach|Owner: nobody Type: Cleanup/optimization | Status: new Compon

Re: [Django] #20542: pymysql breaks last_executed_query()

#20542: pymysql breaks last_executed_query() -+- Reporter: christian.oudard@… |Owner: nobody Type: Bug | Status: closed Component: Database layer

[Django] #24228: Signals have unclear & inconsistent transaction handling

#24228: Signals have unclear & inconsistent transaction handling -+- Reporter: Gaffney | Owner: nobody Type: Bug | Status: new Component: Database layer |V

Re: [Django] #24215: Refactor of lazy model operations

#24215: Refactor of lazy model operations -+- Reporter: AlexHill |Owner: nobody Type: | Status: new Cleanup/optimization |

Re: [Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many -+- Reporter: coldmind |Owner: coldmind Type: | Sta

Re: [Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many -+- Reporter: coldmind |Owner: coldmind Type: | Sta

Re: [Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many -+- Reporter: coldmind |Owner: coldmind Type: | Sta

Re: [Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many -+- Reporter: coldmind |Owner: coldmind Type: | Sta

Re: [Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many -+- Reporter: coldmind |Owner: nobody Type: | Statu

[Django] #24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many

#24227: isinstance checks on ManyToManyField should be replaced with field.many_to_many --+ Reporter: coldmind | Owner: nobody Type: Cleanup/optimization | Status: new Component: Uncategorized

[Django] #24226: Need to be able to change "(None)" display for null fields in Django admin

#24226: Need to be able to change "(None)" display for null fields in Django admin --+ Reporter: meesterguyperson | Owner: nobody Type: New feature | Status: new Component: Generic views |Version: 1

Re: [Django] #24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3)

#24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3) --+-- Reporter: hheimbuerger |Owner: nobody Type: Bug | Status: new Component: M

[Django] #24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3)

#24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in 1.7.3) --+ Reporter: hheimbuerger | Owner: nobody Type: Bug | Status: new Component: Migrations|Version: master Severi

Re: [Django] #24219: Deprecate django.forms.extras and move SelectDateWidget with the other widget.

#24219: Deprecate django.forms.extras and move SelectDateWidget with the other widget. -+- Reporter: loic |Owner: loic Type: | Status:

Re: [Django] #24219: Deprecate django.forms.extras and move SelectDateWidget with the other widget.

#24219: Deprecate django.forms.extras and move SelectDateWidget with the other widget. -+- Reporter: loic |Owner: loic Type: | Status:

Re: [Django] #24210: Clean up relational fields __init__ args/kwargs.

#24210: Clean up relational fields __init__ args/kwargs. -+- Reporter: loic |Owner: loic Type: | Status: closed Cleanup/optimization

Re: [Django] #24104: SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields

#24104: SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields -+- Reporter: coldmind |Owner: coldmind Type:

Re: [Django] #24104: SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields

#24104: SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields -+- Reporter: coldmind |Owner: coldmind Type:

[Django] #24224: sqlmigrate is slow

#24224: sqlmigrate is slow --+ Reporter: TorstenRottmann | Owner: nobody Type: Cleanup/optimization | Status: new Component: Migrations|Version: 1.7 Severity: Normal

[Django] #24223: SessionMiddleware tests leaving Session objects in database

#24223: SessionMiddleware tests leaving Session objects in database --+ Reporter: matt-leach| Owner: nobody Type: Cleanup/optimization | Status: new Component: Uncategorized |Version: m

Re: [Django] #24210: Clean up relational fields __init__ args/kwargs.

#24210: Clean up relational fields __init__ args/kwargs. -+- Reporter: loic |Owner: loic Type: | Status: assigned Cleanup/optimizati

Re: [Django] #24104: SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields

#24104: SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields -+- Reporter: coldmind |Owner: coldmind Type:

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

#24053: Drop IE6/7 admin CSS/icons --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization | Status: closed Component: contrib.admin |

Re: [Django] #24209: Incorrectly formatted Content-Disposition headers may cause error.

#24209: Incorrectly formatted Content-Disposition headers may cause error. ---+- Reporter: tomchristie|Owner: raulcd Type: Bug| Status: assigned Component: HT