Re: [Django] #25476: bug in array handling hit in get_constraints() for psycopg2?

2015-12-15 Thread Django
#25476: bug in array handling hit in get_constraints() for psycopg2? -+- Reporter: heasus |Owner: nobody Type: Bug | Status: new Compone

Re: [Django] #25476: bug in array handling hit in get_constraints() for psycopg2?

2015-12-15 Thread Django
#25476: bug in array handling hit in get_constraints() for psycopg2? -+- Reporter: heasus |Owner: nobody Type: Bug | Status: new Compone

Re: [Django] #25476: bug in array handling hit in get_constraints() for psycopg2?

2015-12-15 Thread Django
#25476: bug in array handling hit in get_constraints() for psycopg2? -+- Reporter: heasus |Owner: nobody Type: Bug | Status: new Compone

Re: [Django] #25476: bug in array handling hit in get_constraints() for psycopg2?

2015-12-15 Thread Django
#25476: bug in array handling hit in get_constraints() for psycopg2? -+- Reporter: heasus |Owner: nobody Type: Bug | Status: closed Comp

Re: [Django] #25945: Unable to refer to partially-run squashed migrations in newer migrations. (was: Unabled to refer to partially-run squashed migrations in newer migrations.)

2015-12-15 Thread Django
#25945: Unable to refer to partially-run squashed migrations in newer migrations. -+- Reporter: jarekwg |Owner: nobody Type: Bug | Status: n

[Django] #25945: Unabled to refer to partially-run squashed migrations in newer migrations.

2015-12-15 Thread Django
#25945: Unabled to refer to partially-run squashed migrations in newer migrations. -+- Reporter: jarekwg | Owner: nobody Type: Bug | Status: new Component: |Version: 1.9 Mi

Re: [Django] #25944: Add the ability to specify which app a migration should be created in

2015-12-15 Thread Django
#25944: Add the ability to specify which app a migration should be created in -+-- Reporter: RamezIssac |Owner: nobody Type: New feature | Status: closed Component: Migrat

Re: [Django] #25944: Add the ability to specify which app a migration should be created in

2015-12-15 Thread Django
#25944: Add the ability to specify which app a migration should be created in -+-- Reporter: RamezIssac |Owner: nobody Type: New feature | Status: new Component: Migration

Re: [Django] #25894: Evaluation of zero-length slices of queryset.values() fails

2015-12-15 Thread Django
#25894: Evaluation of zero-length slices of queryset.values() fails -+- Reporter: debnet |Owner: sir- | sigurd Type: Bug

Re: [Django] #25944: Add the ability to specify which app a migration should be created in (was: Allow to tunnel migration to specific app)

2015-12-15 Thread Django
#25944: Add the ability to specify which app a migration should be created in -+-- Reporter: RamezIssac |Owner: nobody Type: New feature | Status: new Component: Migration

Re: [Django] #25944: Allow to tunnel migration to specific app

2015-12-15 Thread Django
#25944: Allow to tunnel migration to specific app -+-- Reporter: RamezIssac |Owner: nobody Type: New feature | Status: new Component: Migrations | Versi

Re: [Django] #25894: Evaluation of zero-length slices of queryset.values() fails

2015-12-15 Thread Django
#25894: Evaluation of zero-length slices of queryset.values() fails -+- Reporter: debnet |Owner: sir- | sigurd Type: Bug

Re: [Django] #25944: Allow to tunnel migration to specific app

2015-12-15 Thread Django
#25944: Allow to tunnel migration to specific app -+-- Reporter: RamezIssac |Owner: nobody Type: New feature | Status: new Component: Migrations | Versi

[Django] #25944: Allow to tunnel migration to specific app

2015-12-15 Thread Django
#25944: Allow to tunnel migration to specific app -+ Reporter: RamezIssac | Owner: nobody Type: New feature | Status: new Component: Migrations |Version: 1.8 Severity: Normal | Keywords: Triage

Re: [Django] #25942: TypedChoiceField.has_changed behaviour has changed between 1.8 and 1.9

2015-12-15 Thread Django
#25942: TypedChoiceField.has_changed behaviour has changed between 1.8 and 1.9 -+ Reporter: arthru |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #25943: Auto Generated urls.py On startapp

2015-12-15 Thread Django
#25943: Auto Generated urls.py On startapp -+- Reporter: cmhedrick|Owner: nobody Type: | Status: closed Cleanup/optimization

[Django] #25943: Auto Generated urls.py On startapp

2015-12-15 Thread Django
#25943: Auto Generated urls.py On startapp -+- Reporter: cmhedrick| Owner: nobody Type: | Status: new Cleanup/optimization | Component: Uncategori

Re: [Django] #25852: Batch migrations fail when dependent on a custom manager

2015-12-15 Thread Django
#25852: Batch migrations fail when dependent on a custom manager -+- Reporter: lightstrike |Owner: charettes Type: Bug | Status: closed Component: Migration

Re: [Django] #25852: Batch migrations fail when dependent on a custom manager

2015-12-15 Thread Django
#25852: Batch migrations fail when dependent on a custom manager -+- Reporter: lightstrike |Owner: charettes Type: Bug | Status: closed Component: Migration

Re: [Django] #25852: Batch migrations fail when dependent on a custom manager

2015-12-15 Thread Django
#25852: Batch migrations fail when dependent on a custom manager -+- Reporter: lightstrike |Owner: charettes Type: Bug | Status: closed Component: Migration

Re: [Django] #25852: Batch migrations fail when dependent on a custom manager

2015-12-15 Thread Django
#25852: Batch migrations fail when dependent on a custom manager -+- Reporter: lightstrike |Owner: charettes Type: Bug | Status: assigned Component: Migrati

[Django] #25942: TypedChoiceField.has_changed behaviour has changed between 1.8 and 1.9

2015-12-15 Thread Django
#25942: TypedChoiceField.has_changed behaviour has changed between 1.8 and 1.9 + Reporter: arthru | Owner: nobody Type: Bug | Status: new Component: Forms |Version: 1.9 Severity: Normal

Re: [Django] #25942: TypedChoiceField.has_changed behaviour has changed between 1.8 and 1.9

2015-12-15 Thread Django
#25942: TypedChoiceField.has_changed behaviour has changed between 1.8 and 1.9 + Reporter: arthru | Owner: nobody Type: Bug | Status: new Component: Forms |Version: 1.9 Severity: Normal | Resolution:

Re: [Django] #25852: Batch migrations fail when dependent on a custom manager

2015-12-15 Thread Django
#25852: Batch migrations fail when dependent on a custom manager -+- Reporter: lightstrike |Owner: charettes Type: Bug | Status: assigned Component: Migrations |

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

2015-12-15 Thread Django
#24100: Make `post_migrate` dispatch the migration plan. -+ Reporter: charettes|Owner: MarkusH Type: New feature | Status: assigned Component: Migrations |

Re: [Django] #25941: Improve the error message for runtests.py when Django isn't on the path

2015-12-15 Thread Django
#25941: Improve the error message for runtests.py when Django isn't on the path --+ Reporter: kezabelle |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #25941: Improve the error message for runtests.py when Django isn't on the path

2015-12-15 Thread Django
#25941: Improve the error message for runtests.py when Django isn't on the path --+ Reporter: kezabelle |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #25941: Improve the error message for runtests.py when Django isn't on the path

2015-12-15 Thread Django
#25941: Improve the error message for runtests.py when Django isn't on the path --+ Reporter: kezabelle |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #24675: Skip "SET SQL_AUTO_IS_NULL = 0" on versions of MySQL that don't need it

2015-12-15 Thread Django
#24675: Skip "SET SQL_AUTO_IS_NULL = 0" on versions of MySQL that don't need it -+- Reporter: ssjunior |Owner: ssjunior Type: | Status: cl

Re: [Django] #25941: Improve the error message for runtests.py when Django isn't on the path (was: Supply a runtests.sh in the tests directory.)

2015-12-15 Thread Django
#25941: Improve the error message for runtests.py when Django isn't on the path --+ Reporter: kezabelle |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #25941: Supply a runtests.sh in the tests directory.

2015-12-15 Thread Django
#25941: Supply a runtests.sh in the tests directory. ---+-- Reporter: kezabelle |Owner: nobody Type: New feature| Status: new Component: Testing framewor

Re: [Django] #25911: The decorator override_settings resets SETTINGS_MODULE variable

2015-12-15 Thread Django
#25911: The decorator override_settings resets SETTINGS_MODULE variable ---+-- Reporter: kwist |Owner: nobody Type: Bug| Status: closed Compon

Re: [Django] #25941: Supply a runtests.sh in the tests directory.

2015-12-15 Thread Django
#25941: Supply a runtests.sh in the tests directory. ---+-- Reporter: kezabelle |Owner: nobody Type: New feature| Status: new Component: Testing framewor

[Django] #25941: Supply a runtests.sh in the tests directory.

2015-12-15 Thread Django
#25941: Supply a runtests.sh in the tests directory. ---+ Reporter: kezabelle | Owner: nobody Type: New feature| Status: new Component: Testing framework |Version: master Severity: Norma

Re: [Django] #24865: Add a feature to programmatically remove stale content types

2015-12-15 Thread Django
#24865: Add a feature to programmatically remove stale content types --+ Reporter: Protosac |Owner: Type: New feature | Status: new Component: c

Re: [Django] #24865: Add a feature to programmatically remove stale content types

2015-12-15 Thread Django
#24865: Add a feature to programmatically remove stale content types --+ Reporter: Protosac |Owner: Type: New feature | Status: new Component: c

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

2015-12-15 Thread Django
#24100: Make `post_migrate` dispatch the migration plan. -+ Reporter: charettes|Owner: MarkusH Type: New feature | Status: assigned Component: Migrations |

Re: [Django] #10060: Multiple table annotation failure

2015-12-15 Thread Django
#10060: Multiple table annotation failure -+- Reporter: svsharma@… |Owner: Type: Bug | Status: new Component: Database layer |

Re: [Django] #10060: Multiple table annotation failure

2015-12-15 Thread Django
#10060: Multiple table annotation failure -+- Reporter: svsharma@… |Owner: Type: Bug | Status: new Component: Database layer |

Re: [Django] #25940: Add a way to create OGRGeometry from GML (was: OGRGeometry from GML)

2015-12-15 Thread Django
#25940: Add a way to create OGRGeometry from GML -+-- Reporter: yellow-sky |Owner: sir-sigurd Type: New feature | Status: assigned Component: GIS |

Re: [Django] #25911: The decorator override_settings resets SETTINGS_MODULE variable

2015-12-15 Thread Django
#25911: The decorator override_settings resets SETTINGS_MODULE variable ---+-- Reporter: kwist |Owner: nobody Type: Bug| Status: closed Compon

Re: [Django] #25911: The decorator override_settings resets SETTINGS_MODULE variable

2015-12-15 Thread Django
#25911: The decorator override_settings resets SETTINGS_MODULE variable ---+-- Reporter: kwist |Owner: nobody Type: Bug| Status: closed Compon

Re: [Django] #25894: Evaluation of zero-length slices of queryset.values() fails

2015-12-15 Thread Django
#25894: Evaluation of zero-length slices of queryset.values() fails -+- Reporter: debnet |Owner: sir- | sigurd Type: Bug

Re: [Django] #25894: Evaluation of zero-length slices of queryset.values() fails

2015-12-15 Thread Django
#25894: Evaluation of zero-length slices of queryset.values() fails -+- Reporter: debnet |Owner: sir- | sigurd Type: Bug

Re: [Django] #22268: Document values_list() behavior for ManyToManyField

2015-12-15 Thread Django
#22268: Document values_list() behavior for ManyToManyField -+- Reporter: k_sze|Owner: Type: | umeshksingla Cleanup/optimization |

Re: [Django] #25940: OGRGeometry from GML

2015-12-15 Thread Django
#25940: OGRGeometry from GML -+-- Reporter: yellow-sky |Owner: sir-sigurd Type: New feature | Status: assigned Component: GIS | Version: 1.9

Re: [Django] #17659: django_admin_log searches are slow

2015-12-15 Thread Django
#17659: django_admin_log searches are slow --+ Reporter: anonymous |Owner: keeff Type: Cleanup/optimization | Status: new Component: contrib.admin

Re: [Django] #25940: OGRGeometry from GML

2015-12-15 Thread Django
#25940: OGRGeometry from GML -+-- Reporter: yellow-sky |Owner: nobody Type: New feature | Status: new Component: GIS | Version: 1.9 Severit

[Django] #25940: OGRGeometry from GML

2015-12-15 Thread Django
#25940: OGRGeometry from GML -+ Reporter: yellow-sky | Owner: nobody Type: New feature | Status: new Component: GIS |Version: 1.9 Severity: Normal | Keywords: Triage Stage: Unreviewed

Re: [Django] #25938: deduplicate GEOSBase and GDALBase

2015-12-15 Thread Django
#25938: deduplicate GEOSBase and GDALBase -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status

Re: [Django] #25911: The decorator override_settings resets SETTINGS_MODULE variable

2015-12-15 Thread Django
#25911: The decorator override_settings resets SETTINGS_MODULE variable ---+-- Reporter: kwist |Owner: nobody Type: Bug| Status: closed Compon