#1161: g.region and r.info decimal issue when using grass python libs -------------------------+-------------------------------------------------- Reporter: isaacullah | Owner: grass-...@… Type: defect | Status: closed Priority: normal | Milestone: 6.4.1 Component: Python | Version: 6.4.0 Resolution: invalid | Keywords: g.region, precision Platform: All | Cpu: All -------------------------+-------------------------------------------------- Changes (by cmbarton):
* cc: cmbarton (added) Comment: Replying to [comment:10 hamish]: > Replying to [comment:8 hamish]: > > I guess what I find weird is that g.region will never report > > with precision > .15g, which is exactly representable > > well, no, as in the "5.1" example. but reproducible anyhow.. > > > & will never saturate the double-prec bitspace, and so the python > > repr() example above is perhaps using %.16f internally? > > anyway, if it matters python's "print" gives it back to you in the form you were expecting, > > {{{ > >>> n = 4293588.60267 > >>> n > 4293588.6026699999 > >>> print n > 4293588.60267 > }}} > > > Hamish > > ps- do you mind if I move LandDyn/ in addons svn to raster/LandDyn? That's fine. But we need to copy Isaac, as he is maintaining this. Michael -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1161#comment:11> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev