Merge pull request #174 from bluelabsio/float128_fix

Handle exception when machine has no np.float128
bluelabsio · Dec 13, 2022 · 5c689f0 · 5c689f0
2 parents f2483d2 + c41e09b
commit 5c689f0
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 2 deletions.
diff --git a/metrics/coverage_high_water_mark b/metrics/coverage_high_water_mark
@@ -1 +1 @@
-93.6400
+93.6200
diff --git a/records_mover/records/schema/field/__init__.py b/records_mover/records/schema/field/__init__.py
@@ -95,7 +95,6 @@ def python_type_to_field_type(specific_type: Type[Any]) -> Optional['FieldType']
             np.float16: 'decimal',
             np.float32: 'decimal',
             np.float64: 'decimal',
-            np.float128: 'decimal',
             float: 'decimal',
 
             str: 'string',
@@ -113,6 +112,12 @@ def python_type_to_field_type(specific_type: Type[Any]) -> Optional['FieldType']
 
             pd.Timestamp: 'datetime',
         }
+        try:
+            type_mapping[np.float128] = 'decimal'
+        except AttributeError:
+            # np.float128 is not available on some machines
+            pass
+
         if specific_type not in type_mapping:
             logger.warning(f"Please teach me how to map {specific_type} into records "
                            "schema field types")