[gdal-dev] os.remove and os.unlink in the testsuite
Hi Even What do you think about adding some convenience functions to the gdaltest module like "try_remove" and "try_unlink" that never throw an exception if the file doesn't exist? This would remove a lot of lines like these from the test cases: try: os.unlink('some file') except OSError: pass Cheers, Ben ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] os.remove and os.unlink in the testsuite
On lundi 16 avril 2018 19:33:33 CEST Ben Elliston wrote: > Hi Even > > What do you think about adding some convenience functions to the > gdaltest module like "try_remove" and "try_unlink" that never throw an > exception if the file doesn't exist? This would remove a lot of lines > like these from the test cases: > > try: > os.unlink('some file') > except OSError: > pass > You can use gdal.Unlink(filename) and gdal.RmdirRecursive(dirname). They will not throw any exception or error message. Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] Large number of "Unable to translate coordinate system" in epsg file
Hi All, Slightly off-topic question, but I'm curious why I'm seeing so many entries that look like this in my epsg file: # NAD27 / Michigan North # Unable to translate coordinate system EPSG:6200 into PROJ.4 format. Is this normal, or the sign of a flawed install of dependencies, or something else? Thanks, Roger ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev