Closed ds-steventondeur closed 3 years ago
I got here via the 'numpy-quaternion' package and I'm trying to change my code to using quaternionic as the latter seems to be the preferred approach (at least quaternionic seems to have a bit better documentation).
The latter certainly takes advantage of newer capabilities, which makes the documentation easier to write. And I myself have mostly switched to quaternionic at this point. But I should point out that it's not as battle-tested as the former, just because it's newer and far fewer people use it.
any chance we can get rid of it/upgrade it to a higher version?
Absolutely. The new version should be on PyPI in about half an hour, and conda-forge later in the day.
Thanks a bunch! Lucky Luke, fixing issues faster than his shadow.
Hi,
I got here via the 'numpy-quaternion' package and I'm trying to change my code to using
quaternionic
as the latter seems to be the preferred approach (at leastquaternionic
seems to have a bit better documentation).The 'importlib-metadata' dependency is causing a problem though (I'm on python 3.6; hope to upgrade soon but not there yet):
importlib-metadata = {version = "^1.0", python = "<3.8"}
importlib-metadata>=3.6
When running
python -m pip install quaternionic
in my .venv, I get the following error message:A workaround for this problem is to temporarily comment out any reference to our Azure repo in the venv's
pip.ini
file and then upgradeimportlib-metadata
back to a high enough version (>=3.6), but I was wondering why this dependency onimportlib-metadata
exists inquaternionic
; any chance we can get rid of it/upgrade it to a higher version?Kind regards, steven