Open bra-fsn opened 1 year ago
This is due to my including the generated C files so users don't need Cython...
Should I be building them against older numpy?
Is there a compatibility flag I can include to build against the older API but with newer numpy?
I would imagine our new automatic wheels builder will have this issue also?
This is due to my including the generated C files so users don't need Cython...
Should I be building them against older numpy?
Is there a compatibility flag I can include to build against the older API but with newer numpy?
I don't know about numpy API internals, but I can see there are a lot of API versions. Not sure if they have to match or they are forward-compatible.
If adding cython as a dependency helps, that would be great to have that as an extra, so anybody in this situation could just install TA-Lib[cython]
.
I have an environment where we run tests with
tox
with pinned dependencies (normally they are listed in a dynamically generatedtest-requirements.txt
and then added asdeps = -rtest-requirements.txt
in thetox.ini
.setup.py
has the dependencies listed without version constraints.Started recently, running these tests fail with:
It seems that
ta-lib
is compiled with various (the pinned,1.22.4
and the most recent1.23.3
) versions and used intermixed during the tests, but I can't see why. If I remove the version constraint fromtest-requirements.txt
, it works, but we have other packages which depend onnumpy==1.22.4
, so this is not a usable solution here. If I add the version constraint tosetup.py
, I get the same error.Sample
tox.ini
:Requirements file (just to reproduce, not the full one):
setup.py's requirements list:
Originally I had a simple
TA-Lib
, but switched to the archive in order not to install binaries (first I thought this is the problem). And ideas how this could be solved along with keeping the pinned versions?