Re: [Django] #25707: Use py.test for internal testing

#25707: Use py.test for internal testing -+- Reporter: olethanh |Owner: nobody Type: New feature | Status: new Component: Testing framework|

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2) ---+ Reporter: stevejalim |Owner: nobody Type: Bug| Status: new

[Django] #25811: Error in consultation with models of different database

#25811: Error in consultation with models of different database --+-- Reporter: ebar0n| Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #25796: annotate() exception if there are same fields name OR in Q

#25796: annotate() exception if there are same fields name OR in Q -+- Reporter: Falldog |Owner: nobody Type: Bug | Status: closed

Re: [Django] #25807: makemigrations failed when CharField has validators=[validate_slug]

#25807: makemigrations failed when CharField has validators=[validate_slug] -+- Reporter: mrgaolei |Owner: charettes Type: Bug | Status: assigned

Re: [Django] #25370: Error display when makemigrations' field serializing fails with ValueError

#25370: Error display when makemigrations' field serializing fails with ValueError --+ Reporter: torstenrudolf |Owner: awwester Type: Cleanup/optimization |

Re: [Django] #25810: verbose_name_plural is not respected in filter_horizontal or filter_vertical widget

#25810: verbose_name_plural is not respected in filter_horizontal or filter_vertical widget ---+-- Reporter: MacLake|Owner: nobody Type: Bug| Status: closed

Re: [Django] #25723: Related field checks should use their model's apps to lookup related models

#25723: Related field checks should use their model's apps to lookup related models -+- Reporter: charettes|Owner: nobody Type: Bug | Status:

Re: [Django] #25723: Related field checks should use their model's apps to lookup related models

#25723: Related field checks should use their model's apps to lookup related models -+- Reporter: charettes|Owner: nobody Type: Bug | Status:

Re: [Django] #25723: Related field checks should use their model's apps to lookup related models

#25723: Related field checks should use their model's apps to lookup related models -+- Reporter: charettes|Owner: nobody Type: Bug | Status:

Re: [Django] #4140: oracle: manage.py syncdb fails with ORA-06552 when a fieldname is a keyword

#4140: oracle: manage.py syncdb fails with ORA-06552 when a fieldname is a keyword -+- Reporter: frank.hoffsummer@… |Owner: Type: Bug | Status: new

Re: [Django] #4140: oracle: manage.py syncdb fails with ORA-06552 when a fieldname is a keyword

#4140: oracle: manage.py syncdb fails with ORA-06552 when a fieldname is a keyword -+- Reporter: frank.hoffsummer@… |Owner: Type: Bug | Status: new

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres -+- Reporter: auvipy |Owner: Type: New feature | Status: new Component:

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres --+-- Reporter: auvipy|Owner: Type: New feature | Status: new Component: contrib.postgres

[Django] #25810: verbose_name_plural is not respected in filter_horizontal or filter_vertical widget

#25810: verbose_name_plural is not respected in filter_horizontal or filter_vertical widget ---+ Reporter: MacLake| Owner: nobody Type: Bug| Status: new Component: contrib.admin |Version: 1.8

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres --+-- Reporter: auvipy|Owner: Type: New feature | Status: new Component: contrib.postgres

[Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres --+ Reporter: auvipy| Owner: Type: New feature | Status: new Component: contrib.postgres |Version: master Severity: Normal

Re: [Django] #24632: PostgreSQL table inheritance

#24632: PostgreSQL table inheritance -+- Reporter: yennicks |Owner: Type: New feature | Status: new Component: contrib.postgres |

Re: [Django] #25808: Setting to allow django.test.Client default requests to follow=True

#25808: Setting to allow django.test.Client default requests to follow=True ---+-- Reporter: awwester |Owner: nobody Type: New feature| Status: new

Re: [Django] #25808: Setting to allow django.test.Client default requests to follow=True

#25808: Setting to allow django.test.Client default requests to follow=True ---+-- Reporter: awwester |Owner: nobody Type: New feature| Status: new

Re: [Django] #25808: Setting to allow django.test.Client default requests to follow=True

#25808: Setting to allow django.test.Client default requests to follow=True ---+-- Reporter: awwester |Owner: nobody Type: New feature| Status: new

[Django] #25808: Setting to allow django.test.Client default requests to follow=True

#25808: Setting to allow django.test.Client default requests to follow=True ---+ Reporter: awwester | Owner: nobody Type: New feature| Status: new Component: Testing framework |Version: 1.8

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

#25767: integer_field_ranges are incorrect for MySQL backend -+- Reporter: georgemarshall |Owner: | georgemarshall Type: Bug |

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

#25767: integer_field_ranges are incorrect for MySQL backend -+- Reporter: georgemarshall |Owner: | georgemarshall Type: Bug |

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

#25767: integer_field_ranges are incorrect for MySQL backend -+- Reporter: georgemarshall |Owner: | georgemarshall Type: Bug |

Re: [Django] #25805: Django 1.8 startup takes longer than Django 1.7

#25805: Django 1.8 startup takes longer than Django 1.7 -+- Reporter: fopina |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25806: syndication.Feed uses name-mangling for __get_dynamic_attr

#25806: syndication.Feed uses name-mangling for __get_dynamic_attr --+ Reporter: kezabelle |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #25807: makemigrations failed when CharField has validators=[validate_slug]

#25807: makemigrations failed when CharField has validators=[validate_slug] -+ Reporter: mrgaolei |Owner: nobody Type: Bug | Status: new Component:

[Django] #25807: makemigrations failed when CharField has validators=[validate_slug]

#25807: makemigrations failed when CharField has validators=[validate_slug] ---+ Reporter: mrgaolei | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.9rc1

Re: [Django] #25805: Django 1.8 startup takes longer than Django 1.7

#25805: Django 1.8 startup takes longer than Django 1.7 -+- Reporter: fopina |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25806: syndication.Feed uses name-mangling for __get_dynamic_attr

#25806: syndication.Feed uses name-mangling for __get_dynamic_attr -+- Reporter: kezabelle|Owner: nobody Type: | Status: new

Re: [Django] #21221: Widgets and Admin's Media should use the configured staticfiles storage to create the right path to a file

#21221: Widgets and Admin's Media should use the configured staticfiles storage to create the right path to a file -+- Reporter: Guilherme Gondim |Owner: codingjoe

Re: [Django] #25806: syndication.Feed uses name-mangling for __get_dynamic_attr

#25806: syndication.Feed uses name-mangling for __get_dynamic_attr -+- Reporter: kezabelle|Owner: nobody Type: | Status: new

Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

#25789: Inefficient Queries Generated due to not using WHERE EXISTS -+- Reporter: cancan101|Owner: nobody Type: | Status: new

[Django] #25806: syndication.Feed uses name-mangling for __get_dynamic_attr

#25806: syndication.Feed uses name-mangling for __get_dynamic_attr --+ Reporter: kezabelle | Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.syndication |Version:

Re: [Django] #25805: Django 1.8 startup takes longer than Django 1.7 (was: Raspberry Pi 1.7 vs 1.8 performance)

#25805: Django 1.8 startup takes longer than Django 1.7 -+- Reporter: fopina |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25805: Raspberry Pi 1.7 vs 1.8 performance

#25805: Raspberry Pi 1.7 vs 1.8 performance -+- Reporter: fopina |Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #25805: Raspberry Pi 1.7 vs 1.8 performance

#25805: Raspberry Pi 1.7 vs 1.8 performance ---+ Reporter: fopina | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.8 Severity: Normal | Keywords:

Re: [Django] #25662: allow creation of empty GEOSGeometries

#25662: allow creation of empty GEOSGeometries -+-- Reporter: sir-sigurd |Owner: sir-sigurd Type: New feature | Status: assigned Component: GIS |