Re: [Django] #25869: add support for GEOSWKTWriter_setRoundingPrecision and GEOSWKTWriter_setTrim

#25869: add support for GEOSWKTWriter_setRoundingPrecision and GEOSWKTWriter_setTrim -+-- Reporter: sir-sigurd |Owner: sir-sigurd Type: New feature | Status: assigned

[Django] #25869: add support for GEOSWKTWriter_setRoundingPrecision and GEOSWKTWriter_setTrim

#25869: add support for GEOSWKTWriter_setRoundingPrecision and GEOSWKTWriter_setTrim -+ Reporter: sir-sigurd | Owner: nobody Type: New feature | Status: new Component: GIS |Version: master

Re: [Django] #25547: refresh_from_db leaves FieldFile with reference to db_instance

#25547: refresh_from_db leaves FieldFile with reference to db_instance -+- Reporter: vinnyrose|Owner: nobody Type: Bug | Status: new

Re: [Django] #25547: refresh_from_db leaves FieldFile with reference to db_instance

#25547: refresh_from_db leaves FieldFile with reference to db_instance -+- Reporter: vinnyrose|Owner: nobody Type: Bug | Status: new

Re: [Django] #25677: compilemessages throws an exception and does not report msgformat errors correctly

#25677: compilemessages throws an exception and does not report msgformat errors correctly -+- Reporter: gavinwahl|Owner: Claude | Paroz

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField --+ Reporter: gabn88|Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #25868: Importing django.test.utils.get_runner fails on Django 1.9 with Python 3.3

#25868: Importing django.test.utils.get_runner fails on Django 1.9 with Python 3.3 ---+-- Reporter: sobotklp |Owner: nobody Type: Bug| Status:

[Django] #25868: Importing django.test.utils.get_runner fails on Django 1.9 with Python 3.3

#25868: Importing django.test.utils.get_runner fails on Django 1.9 with Python 3.3 ---+ Reporter: sobotklp | Owner: nobody Type: Bug| Status: new Component: Testing framework |

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField -+- Reporter: gabn88 |Owner: nobody Type: Bug | Status: new

Re: [Django] #25867: Nested ArrayField cause error in system check on 1.9

#25867: Nested ArrayField cause error in system check on 1.9 --+- Reporter: mpre |Owner: charettes Type: Bug | Status: assigned Component:

Re: [Django] #25867: Nested ArrayField cause error in system check on 1.9

#25867: Nested ArrayField cause error in system check on 1.9 --+- Reporter: mpre |Owner: charettes Type: Bug | Status: assigned Component:

[Django] #25867: Nested ArrayField cause error in system check on 1.9

#25867: Nested ArrayField cause error in system check on 1.9 --+- Reporter: mpre | Owner: Type: Bug | Status: new Component: contrib.postgres |Version: 1.9 Severity: Normal

Re: [Django] #25740: document GEOSGeomerty operators

#25740: document GEOSGeomerty operators -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status:

Re: [Django] #25740: document GEOSGeomerty operators

#25740: document GEOSGeomerty operators -+- Reporter: sir-sigurd |Owner: sir- Type: | sigurd Cleanup/optimization | Status:

Re: [Django] #25840: cache.get_or_set() works incorrectly with DummyCache backend

#25840: cache.get_or_set() works incorrectly with DummyCache backend -+- Reporter: oleksiyivanenko |Owner: nobody Type: Bug | Status: closed

Re: [Django] #25840: cache.get_or_set() works incorrectly with DummyCache backend

#25840: cache.get_or_set() works incorrectly with DummyCache backend -+- Reporter: oleksiyivanenko |Owner: nobody Type: Bug | Status: closed

Re: [Django] #25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9

#25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9 ---+-- Reporter: stephanm |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField -+- Reporter: gabn88 |Owner: nobody Type: Bug | Status: new

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField -+- Reporter: gabn88 |Owner: nobody Type: Bug | Status: new

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField -+- Reporter: gabn88 |Owner: nobody Type: Bug | Status: new

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField -+- Reporter: gabn88 |Owner: nobody Type: Bug | Status: new

Re: [Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField -+- Reporter: gabn88 |Owner: nobody Type: Bug | Status: new

[Django] #25866: Django migrations not picking up max_length change on FileField

#25866: Django migrations not picking up max_length change on FileField --+ Reporter: gabn88| Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #25865: OSMGeoAdmin should require GDAL only if model has fields with SRID that differs from map srid

#25865: OSMGeoAdmin should require GDAL only if model has fields with SRID that differs from map srid ---+-- Reporter: sir-sigurd |Owner: sir-sigurd Type: Uncategorized |

Re: [Django] #25845: False timezone offset warnings in admin if a custom base template doesn't set data-admin-utc-offset

#25845: False timezone offset warnings in admin if a custom base template doesn't set data-admin-utc-offset ---+ Reporter: Strayer|Owner: nobody Type: Bug|

Re: [Django] #25853: add support for GeoHash GIS function on SpatiaLite backend

#25853: add support for GeoHash GIS function on SpatiaLite backend -+- Reporter: sir-sigurd |Owner: sir-sigurd Type: New feature | Status: closed Component: GIS

Re: [Django] #13774: Add model Field.rel_db_type() method

#13774: Add model Field.rel_db_type() method -+- Reporter: Suor |Owner: Suor Type: New feature | Status: closed Component: Database layer

Re: [Django] #25855: Improve runserver migration notification output.

#25855: Improve runserver migration notification output. -+- Reporter: kezabelle|Owner: emre Type: | Status: assigned

Re: [Django] #25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9

#25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9 ---+-- Reporter: stephanm |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #25734: Nodata value not excluded when computing GDALBand min/max values

#25734: Nodata value not excluded when computing GDALBand min/max values -+- Reporter: yellowcap|Owner: nobody Type: Bug | Status: closed

Re: [Django] #25734: Nodata value not excluded when computing GDALBand min/max values

#25734: Nodata value not excluded when computing GDALBand min/max values -+- Reporter: yellowcap|Owner: nobody Type: Bug | Status: new

Re: [Django] #25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9

#25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9 ---+-- Reporter: stephanm |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #25860: Test setup error: Cannot operate on a closed database

#25860: Test setup error: Cannot operate on a closed database ---+-- Reporter: jonashaag |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9

#25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9 ---+-- Reporter: stephanm |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #25860: Test setup error: Cannot operate on a closed database

#25860: Test setup error: Cannot operate on a closed database ---+-- Reporter: jonashaag |Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9

#25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9 ---+-- Reporter: stephanm |Owner: nobody Type: Uncategorized | Status: new Component:

[Django] #25865: OSMGeoAdmin should require GDAL only if model has fields with SRID that differs from map srid

#25865: OSMGeoAdmin should require GDAL only if model has fields with SRID that differs from map srid ---+ Reporter: sir-sigurd | Owner: nobody Type: Uncategorized | Status: new Component: GIS|

Re: [Django] #25865: OSMGeoAdmin should require GDAL only if model has fields with SRID that differs from map srid

#25865: OSMGeoAdmin should require GDAL only if model has fields with SRID that differs from map srid ---+-- Reporter: sir-sigurd |Owner: sir-sigurd Type: Uncategorized |

[Django] #25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9

#25864: AppRegistryNotReady exception since update from 1.8.7 to 1.9 ---+ Reporter: stephanm | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.9 Severity: Normal

Re: [Django] #25862: AttributeError: 'FileSystemStorage' object has no attribute 'location'

#25862: AttributeError: 'FileSystemStorage' object has no attribute 'location' --+-- Reporter: codingjoe |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #25862: AttributeError: 'FileSystemStorage' object has no attribute 'location'

#25862: AttributeError: 'FileSystemStorage' object has no attribute 'location' --+-- Reporter: codingjoe |Owner: nobody Type: Bug | Status: new Component: Core

Re: [Django] #25855: Improve runserver migration notification output.

#25855: Improve runserver migration notification output. -+- Reporter: kezabelle|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25699: Allow using test client session handling with custom session apps

#25699: Allow using test client session handling with custom session apps -+- Reporter: sergeykolosov|Owner: | sergeykolosov Type: New feature

Re: [Django] #25862: AttributeError: 'FileSystemStorage' object has no attribute 'location'

#25862: AttributeError: 'FileSystemStorage' object has no attribute 'location' --+-- Reporter: codingjoe |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #25677: compilemessages throws an exception and does not report msgformat errors correctly

#25677: compilemessages throws an exception and does not report msgformat errors correctly -+- Reporter: gavinwahl|Owner: Claude | Paroz

Re: [Django] #25855: Improve runserver migration notification output.

#25855: Improve runserver migration notification output. -+- Reporter: kezabelle|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25677: compilemessages throws an exception and does not report msgformat errors correctly

#25677: compilemessages throws an exception and does not report msgformat errors correctly -+- Reporter: gavinwahl|Owner: Claude | Paroz

Re: [Django] #25862: AttributeError: 'FileSystemStorage' object has no attribute 'location'

#25862: AttributeError: 'FileSystemStorage' object has no attribute 'location' --+-- Reporter: codingjoe |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #25734: Nodata value not excluded when computing GDALBand min/max values

#25734: Nodata value not excluded when computing GDALBand min/max values -+- Reporter: yellowcap|Owner: nobody Type: Bug | Status: new

Re: [Django] #25863: RenameModel migration does not rename indexes, subsequent index creation fails

#25863: RenameModel migration does not rename indexes, subsequent index creation fails -+-- Reporter: jbaum-cmcrc |Owner: nobody Type: Bug | Status: new Component: