Re: [Django] #26755: test_middleware_classes_headers fails when django files aren't writable

#26755: test_middleware_classes_headers fails when django files aren't writable --+ Reporter: Raphaël Hertzog |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #28212: Allow customizing the port that LiveServerTestCase uses

#28212: Allow customizing the port that LiveServerTestCase uses --+ Reporter: Robert Rollins|Owner: nobody Type: Cleanup/optimization | Status: closed Compone

Re: [Django] #28212: Allow customizing the port that LiveServerTestCase uses

#28212: Allow customizing the port that LiveServerTestCase uses --+ Reporter: Robert Rollins|Owner: nobody Type: Cleanup/optimization | Status: closed Compone

Re: [Django] #25418: URL Validator to check only hostname part without domain nor tld

#25418: URL Validator to check only hostname part without domain nor tld --+ Reporter: FoxMaSk |Owner: nobody Type: New feature | Status: new Component: Core (Other)

Re: [Django] #26755: test_middleware_classes_headers fails when django files aren't writable

#26755: test_middleware_classes_headers fails when django files aren't writable --+ Reporter: Raphaël Hertzog |Owner: nobody Type: Cleanup/optimization | Status: ne

Re: [Django] #26294: Clarify call_command()'s handling of args and options

#26294: Clarify call_command()'s handling of args and options -+- Reporter: Malcolm Box |Owner: nobody Type: | Status: closed Cleanup/optim

Re: [Django] #26294: Clarify call_command()'s handling of args and options

#26294: Clarify call_command()'s handling of args and options -+- Reporter: Malcolm Box |Owner: nobody Type: | Status: closed Cleanup/optim

Re: [Django] #26294: Clarify call_command()'s handling of args and options

#26294: Clarify call_command()'s handling of args and options -+- Reporter: Malcolm Box |Owner: nobody Type: | Status: closed Cleanup/optim

Re: [Django] #25418: URL Validator to check only hostname part without domain nor tld

#25418: URL Validator to check only hostname part without domain nor tld --+ Reporter: FoxMaSk |Owner: nobody Type: New feature | Status: new Component: Core (Other)

Re: [Django] #28201: Make CharField/TextField prohibit null characters (was: Saving a Char/TextField with psycopg2 2.7+ raises ValueError: A string literal cannot contain NUL (0x00) characters is unha

#28201: Make CharField/TextField prohibit null characters --+ Reporter: CM Lubinski |Owner: (none) Type: Cleanup/optimization | Status: new Component: Form

Re: [Django] #28257: Add support for GDAL 2.2

#28257: Add support for GDAL 2.2 --+ Reporter: Tim Graham|Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS |

Re: [Django] #28257: Add support for GDAL 2.2

#28257: Add support for GDAL 2.2 --+ Reporter: Tim Graham|Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS |

Re: [Django] #28117: loaddata raises ValueError with psycopg2 backend

#28117: loaddata raises ValueError with psycopg2 backend -+- Reporter: Nicolas Kuttler |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #28255: URLValidator rejects hostname only URLs (was: http://foo is a valid url)

#28255: URLValidator rejects hostname only URLs ---+-- Reporter: Chris Withers |Owner: nobody Type: Bug| Status: closed Component: Core (Other) |

Re: [Django] #22550: QuerySet last() and reverse() confusing when used with ordered slices

#22550: QuerySet last() and reverse() confusing when used with ordered slices -+- Reporter: Jon Dufresne |Owner: Michael | Käufl Type: Bug

Re: [Django] #28209: Date-based generic views can fail with ValueError: year is out of range

#28209: Date-based generic views can fail with ValueError: year is out of range -+- Reporter: Tim Graham |Owner: Adit | Biswas Type: Bug

Re: [Django] #28209: Date-based generic views can fail with ValueError: year is out of range

#28209: Date-based generic views can fail with ValueError: year is out of range -+- Reporter: Tim Graham |Owner: Adit | Biswas Type: Bug

Re: [Django] #28237: Allow GDAL library detection to work with non "dot zero" releases

#28237: Allow GDAL library detection to work with non "dot zero" releases --+ Reporter: Adam Starrh |Owner: nobody Type: Cleanup/optimization | Status: closed

Re: [Django] #28237: Allow GDAL library detection to work with non "dot zero" releases

#28237: Allow GDAL library detection to work with non "dot zero" releases --+ Reporter: Adam Starrh |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #28257: Add support for GDAL 2.2

#28257: Add support for GDAL 2.2 --+ Reporter: Tim Graham|Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS |

Re: [Django] #28257: Add support for GDAL 2.2

#28257: Add support for GDAL 2.2 --+ Reporter: Tim Graham|Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS |

[Django] #28257: Add support for GDAL 2.2

#28257: Add support for GDAL 2.2 + Reporter: Tim Graham| Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS

Re: [Django] #28256: Django `update_last_login` always providing lastest time. not last login time

#28256: Django `update_last_login` always providing lastest time. not last login time --+-- Reporter: Vinay Kumar |Owner: nobody Type: Bug | Status: closed Compone

Re: [Django] #28250: migration depending on non-existing legacy migration

#28250: migration depending on non-existing legacy migration ---+ Reporter: Brian May |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |

Re: [Django] #28253: Integrity error in get_or_create

#28253: Integrity error in get_or_create -+- Reporter: Anuranjit maindola |Owner: Anuranjit | maindola Type: Bug |

[Django] #28256: Django `update_last_login` always providing lastest time. not last login time

#28256: Django `update_last_login` always providing lastest time. not last login time + Reporter: Vinay Kumar | Owner: nobody Type: Bug | Status: new

Re: [Django] #28181: Versions in GDAL lib_names are outdated

#28181: Versions in GDAL lib_names are outdated +-- Reporter: Tim Graham |Owner: Tim Graham Type: Bug | Status: closed Component: GIS | Vers

Re: [Django] #28181: Versions in GDAL lib_names are outdated

#28181: Versions in GDAL lib_names are outdated +-- Reporter: Tim Graham |Owner: Tim Graham Type: Bug | Status: closed Component: GIS | Vers

Re: [Django] #23804: Add a RasterField to GeoDjango

#23804: Add a RasterField to GeoDjango -+- Reporter: Daniel Wiesmann |Owner: Daniel | Wiesmann Type: New feature | Statu

[Django] #28255: http://foo is a valid url

#28255: http://foo is a valid url -+ Reporter: Chris Withers | Owner: nobody Type: Bug| Status: new Component: Forms |Version: 1.11

Re: [Django] #28250: migration depending on non-existing legacy migration

#28250: migration depending on non-existing legacy migration ---+-- Reporter: Brian May |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |

Re: [Django] #28199: `Subquery` in __in filter generating invalid SQL

#28199: `Subquery` in __in filter generating invalid SQL -+- Reporter: Murray |Owner: nobody Christopherson | Type: Bug |

Re: [Django] #28199: `Subquery` in __in filter generating invalid SQL

#28199: `Subquery` in __in filter generating invalid SQL -+- Reporter: Murray |Owner: nobody Christopherson | Type: Bug |

Re: [Django] #28254: get 304 HTTP code and can't open the pages on windows 10

#28254: get 304 HTTP code and can't open the pages on windows 10 ---+-- Reporter: 冯钊 |Owner: nobody Type: Bug| Status: closed Component: HTTP handling

Re: [Django] #28250: migration depending on non-existing legacy migration

#28250: migration depending on non-existing legacy migration ---+-- Reporter: Brian May |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |

Re: [Django] #28253: Integrity error in get_or_create

#28253: Integrity error in get_or_create -+- Reporter: Anuranjit maindola |Owner: 冯钊 Type: Bug | Status: assigned Component: Database layer

[Django] #28254: get 304 HTTP code and can't open the pages on windows 10

#28254: get 304 HTTP code and can't open the pages on windows 10 -+--- Reporter: 冯钊 | Owner: nobody Type: Bug| Status: new Component: HTTP

Re: [Django] #28250: migration depending on non-existing legacy migration

#28250: migration depending on non-existing legacy migration ---+-- Reporter: Brian May |Owner: nobody Type: Uncategorized | Status: new Component: Migrations |