Re: [Django] #27956: Template error raised in an {% extends %} parent template shows incorrect source location on debug page (was: In DEBUG interface, the section "error during template rendering" doe

#27956: Template error raised in an {% extends %} parent template shows incorrect source location on debug page -+ Reporter: Ling-Xiao Yang |Owner: nobody Type: Bug |

Re: [Django] #27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails

#27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required

#27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required -+- Reporter: karyon |Owner: nobody Type: Bug |

Re: [Django] #27584: Template error raised in a parent template shows incorrect source location on debug page

#27584: Template error raised in a parent template shows incorrect source location on debug page -+ Reporter: Bob |Owner: nobody Type: Bug | Status:

Re: [Django] #27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required

#27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required -+- Reporter: karyon |Owner: nobody Type: Bug |

Re: [Django] #27962: allow lookups on Area annotation

#27962: allow lookups on Area annotation -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

[Django] #27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails

#27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails + Reporter: Sergey Fedoseev | Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails

#27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

[Django] #27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required

#27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required -+- Reporter: karyon | Owner: nobody Type: Bug| Status: new

Re: [Django] #27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails

#27965: gis_tests.test_geoforms.GeometryFieldTest.test_field_string_value fails -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #27956: Template error raised in an {% extends %} parent template shows incorrect source location on debug page

#27956: Template error raised in an {% extends %} parent template shows incorrect source location on debug page -+ Reporter: Ling-Xiao Yang |Owner: nobody Type: Bug |

Re: [Django] #27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required

#27966: db.backends.postgresql checks for psycopg2 2.4.5, but actually 2.5 is required -+- Reporter: karyon |Owner: nobody Type: Bug |

Re: [Django] #9475: add(), create(), etc. should be supported by intermediate ManyToMany model with extra attributes if extra fields can be calculated

#9475: add(), create(), etc. should be supported by intermediate ManyToMany model with extra attributes if extra fields can be calculated -+- Reporter: omat@… |Owner: nobody

Re: [Django] #27967: The autogenerated OneToOneField on multi table inheritance breaks the InlineAdminForm given UUID pk

#27967: The autogenerated OneToOneField on multi table inheritance breaks the InlineAdminForm given UUID pk ---+-- Reporter: Robin Anupol |Owner: nobody Type: Bug|

Re: [Django] #27961: HTTP_X_FORWARDED_PROTO is bypassed

#27961: HTTP_X_FORWARDED_PROTO is bypassed -+- Reporter: cryptogun|Owner: nobody Type: Bug | Status: new Component: HTTP handling

[Django] #27967: The autogenerated OneToOneField on multi table inheritance breaks the InlineAdminForm given UUID pk

#27967: The autogenerated OneToOneField on multi table inheritance breaks the InlineAdminForm given UUID pk -+ Reporter: Robin Anupol | Owner: nobody Type: Uncategorized |

Re: [Django] #27964: on MySQL geometry with other SRID is saved silently in DB

#27964: on MySQL geometry with other SRID is saved silently in DB -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: Bug

[Django] #27964: on MySQL geometry with other SRID is saved silently in DB

#27964: on MySQL geometry with other SRID is saved silently in DB ---+ Reporter: Sergey Fedoseev | Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #27962: allow lookups on Area annotation

#27962: allow lookups on Area annotation -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

Re: [Django] #27963: Example in docs doesn't follow PEP 257 in example immediately following the note about following PEP 257

#27963: Example in docs doesn't follow PEP 257 in example immediately following the note about following PEP 257 -+- Reporter: Mikkel Munch |Owner: nobody Mortensen

[Django] #27963: Example in docs doesn't follow PEP 257 in example immediately following the note about following PEP 257

#27963: Example in docs doesn't follow PEP 257 in example immediately following the note about following PEP 257 --+ Reporter: Mikkel Munch Mortensen | Owner: nobody Type:

Re: [Django] #27919: Decide if attrs (and possibly others) are named or positional parameters in new widget rendering code

#27919: Decide if attrs (and possibly others) are named or positional parameters in new widget rendering code -+-- Reporter: Claude Paroz |Owner: Tim Graham Type: Bug |

[Django] #27962: allow lookups on Area annotation

#27962: allow lookups on Area annotation ---+ Reporter: Sergey Fedoseev | Owner: nobody Type: New feature | Status: new Component: GIS |

Re: [Django] #27962: allow lookups on Area annotation

#27962: allow lookups on Area annotation -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

Re: [Django] #27956: In DEBUG interface, the section "error during template rendering" doesn't go inside an included template

#27956: In DEBUG interface, the section "error during template rendering" doesn't go inside an included template -+-- Reporter: Ling-Xiao Yang |Owner: nobody Type: Bug |

Re: [Django] #27964: Raise an error if a MySQL geometry with an unsupported SRID is saved to the database (was: on MySQL geometry with other SRID is saved silently in DB)

#27964: Raise an error if a MySQL geometry with an unsupported SRID is saved to the database -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev

Re: [Django] #27952: core.validators.validate_slug doesn't mention that only latin letters are accepted.

#27952: core.validators.validate_slug doesn't mention that only latin letters are accepted. -+- Reporter: Serhiy Zahoriya |Owner: Paul Type: | Sajna

Re: [Django] #27919: Decide if attrs (and possibly others) are named or positional parameters in new widget rendering code

#27919: Decide if attrs (and possibly others) are named or positional parameters in new widget rendering code -+-- Reporter: Claude Paroz |Owner: Tim Graham Type: Bug |

Re: [Django] #27890: runtests.py cleanup exception on Python 3.6

#27890: runtests.py cleanup exception on Python 3.6 -+ Reporter: Vytis Banaitis |Owner: nobody Type: Bug | Status: closed Component: Core (Other) |

Re: [Django] #27952: core.validators.validate_slug doesn't mention that only latin letters are accepted.

#27952: core.validators.validate_slug doesn't mention that only latin letters are accepted. -+- Reporter: Serhiy Zahoriya |Owner: Paul Type: | Sajna

Re: [Django] #27890: runtests.py cleanup exception on Python 3.6

#27890: runtests.py cleanup exception on Python 3.6 -+ Reporter: Vytis Banaitis |Owner: nobody Type: Bug | Status: closed Component: Core (Other) |

Re: [Django] #27935: BrinIndex crashes if name > 30 characters

#27935: BrinIndex crashes if name > 30 characters -+- Reporter: Den |Owner: Tim | Graham Type: Bug |

Re: [Django] #27935: BrinIndex crashes if name > 30 characters

#27935: BrinIndex crashes if name > 30 characters -+- Reporter: Den |Owner: Tim | Graham Type: Bug |

Re: [Django] #27935: BrinIndex crashes if name > 30 characters

#27935: BrinIndex crashes if name > 30 characters -+- Reporter: Den |Owner: Tim | Graham Type: Bug |

Re: [Django] #27957: Remove technical terms from InlineForeignKeyField/ModelMultipleChoiceField error messages

#27957: Remove technical terms from InlineForeignKeyField/ModelMultipleChoiceField error messages -+- Reporter: Jon Dufresne |Owner: nobody Type: |

Re: [Django] #27952: core.validators.validate_slug doesn't mention that only latin letters are accepted.

#27952: core.validators.validate_slug doesn't mention that only latin letters are accepted. --+ Reporter: Serhiy Zahoriya |Owner: (none) Type: Cleanup/optimization |

Re: [Django] #27960: ds = DataSource('/path/to/your/cities.shp') fails on first try (GDALException Unknown error code: "198770787"), but works on second

#27960: ds = DataSource('/path/to/your/cities.shp') fails on first try (GDALException Unknown error code: "198770787"), but works on second ---+-- Reporter: Etiënne Thomassen |Owner: nobody

Re: [Django] #27957: Remove technical terms from InlineForeignKeyField/ModelMultipleChoiceField error messages (was: User facing error messages should avoid technical jargon)

#27957: Remove technical terms from InlineForeignKeyField/ModelMultipleChoiceField error messages -+- Reporter: Jon Dufresne |Owner: nobody Type: |

Re: [Django] #27365: Fields suddenly not found.

#27365: Fields suddenly not found. -+- Reporter: Brandon |Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #27365: Fields suddenly not found.

#27365: Fields suddenly not found. -+- Reporter: Brandon |Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #27963: Docstring example in docs doesn't follow PEP 257 (was: Example in docs doesn't follow PEP 257 in example immediately following the note about following PEP 257)

#27963: Docstring example in docs doesn't follow PEP 257 -+- Reporter: Mikkel Munch |Owner: nobody Mortensen | Type: |

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

#27931: Clarify the meaning of "django catch-all logger" -+- Reporter: Jesse|Owner: Vedran Type: | Karačić Cleanup/optimization |