Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exclude np.float128 type registration in MacM1 #624

Merged
merged 2 commits into from Sep 18, 2021
Merged

exclude np.float128 type registration in MacM1 #624

merged 2 commits into from Sep 18, 2021

Conversation

cosmicBboy
Copy link
Collaborator

#623 reports an issue with importing np.float128 in MacOS, M11 architecture. This PR may (?) address it

@codecov
Copy link

codecov bot commented Sep 15, 2021

Codecov Report

Merging #624 (29392c4) into dev (7083836) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##              dev     #624   +/-   ##
=======================================
  Coverage   98.84%   98.84%           
=======================================
  Files          29       30    +1     
  Lines        3384     3384           
=======================================
  Hits         3345     3345           
  Misses         39       39           
Impacted Files Coverage Δ
pandera/engines/numpy_engine.py 100.00% <100.00%> (ø)
pandera/engines/pandas_engine.py 99.29% <100.00%> (-0.01%) ⬇️
pandera/system.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7083836...29392c4. Read the comment docs.

@jeffzi
Copy link
Collaborator

jeffzi commented Sep 15, 2021

Alternatively, we could try-catch the import of sensitive dtypes (np.float256, etc) instead of hardcoding platform specificities as we did for windows and perhaps Macs M1.

We could also detect missing dtypes from that line in the build_number_equivalents function:

https://github.com/pandera-dev/pandera/blob/f0ddcbf287b4edf08be47d9365e5532a703a8077/pandera/engines/numpy_engine.py#L131

@cosmicBboy cosmicBboy merged commit fde35c5 into dev Sep 18, 2021
@cosmicBboy cosmicBboy deleted the bugfix/623 branch September 19, 2021 20:46
cosmicBboy added a commit that referenced this pull request Sep 22, 2021
* Strategies should not rely on pandas dtype aliases (#620)

* add test for strategy with pandas.DatetimeTZDtype using a datetime.tzinfo

* avoid coercing with string alias in strategies

* support timedelta in data synthesis strats (#621)

* fix multiindex error reporting (#622)

* Pin pylint (#629)

* bump pre-commit pylint version

* pin pylint

* remove setuptools pins

* setup.py setuptools

* add back setuptools dep

* update ci build

* update build

* update nox build

* update nox build

* exclude np.float128 type registration in MacM1 (#624)

* exclude np.float128 type registration in MacM1

* replace windows/mac m1 checks with float128 check

* fix numpy_pandas_coercible bug dealing with single element (#626)

* fix numpy_pandas_coercible bug dealing with single element

* add test

* remove empty case

* update pylint (#630)

* unpin pylint, remove setuptools constraint

* bump cache

* install simpleeval in noxfile

* re-pin pylint

* fix lint

* nox uses setuptools < 58.0.0

Co-authored-by: Jean-Francois Zinque <jzinque@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants