Opened 5 years ago

Closed 3 years ago

#2442 closed defect (fixed)

np.float128 does not always exist

Reported by: jradinger Owned by: grass-dev@…
Priority: normal Milestone: 7.2.0
Component: Python Version: svn-trunk
Keywords: t.vect.univar Cc:
CPU: x86-32 Platform: Unspecified

Description

When compiling the latest SVN (62197) of GRASS7 trunk I run into following error (first among the error list, mostly in the temporal dir):

Traceback (most recent call last):
  File "/usr/local/src/grass7_trunk/dist.i686-pc-linux-gnu/scripts/t.vect.univar", line 66, in <module>
    import grass.temporal as tgis
  File "/usr/local/src/grass7_trunk/dist.i686-pc-linux-gnu/etc/python/grass/temporal/__init__.py", line 29, in <module>
    from temporal_vector_algebra import *
  File "/usr/local/src/grass7_trunk/dist.i686-pc-linux-gnu/etc/python/grass/temporal/temporal_vector_algebra.py", line 420, in <module>
    import grass.pygrass.modules as pygrass
  File "/usr/local/src/grass7_trunk/dist.i686-pc-linux-gnu/etc/python/grass/pygrass/__init__.py", line 15, in <module>
    from . import raster
  File "/usr/local/src/grass7_trunk/dist.i686-pc-linux-gnu/etc/python/grass/pygrass/raster/__init__.py", line 35, in <module>
    from grass.pygrass.raster.buffer import Buffer
  File "/usr/local/src/grass7_trunk/dist.i686-pc-linux-gnu/etc/python/grass/pygrass/raster/buffer.py", line 14, in <module>
    DCELL = (np.float64, np.float128)
AttributeError: 'module' object has no attribute 'float128'
make[1]: *** [t.vect.univar.tmp.html] Error 1

Here I am running Python 2.7.3 with numpy 1.9.0.

Here http://stackoverflow.com/questions/9062562/what-is-the-internal-precision-of-numpy-float128 it says that is is related to the architecture. In my case I am on a 32 bit system.

Changing from np.float128() to np.longdouble() (which exists on my system) should solve the problem.

Change History (6)

comment:1 Changed 5 years ago by martinl

Component: DefaultPython
Milestone: 7.1.0

comment:2 in reply to:  description Changed 5 years ago by zarch

Here http://stackoverflow.com/questions/9062562/what-is-the-internal-precision-of-numpy-float128 it says that is is related to the architecture. In my case I am on a 32 bit system.

Right, I didn't thought about it!

Now should be fix in r62206. Moreover I've disconnected (r62205) and isolate the ctypes part of pygrass from the rest, this should make the whole pygrass more stable (I hope).

comment:3 Changed 4 years ago by lucadelu

Is this ticket still valid?

comment:4 Changed 4 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:5 Changed 3 years ago by neteler

Keywords: t.vect.univar added

No response, closing.

comment:6 Changed 3 years ago by neteler

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.