-
Notifications
You must be signed in to change notification settings - Fork 14
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
Please document dependency version requirements. #38
Comments
I have been ruining into the same problem, and I highly recommend to create a virtual environment to run some of the sub program of diploSHIC. Here is the workflow I've done:
|
It is possible for it all to work in a single venv, but it was non-trivial to work out. The following works on Python 3.8 and I believe also 3.9:
I've used this on several machines with Pop OS 20.04 and 21.04, which are basically the same as the Ubuntu's with the same version numbers. |
hey @molpopgen and @jdaron -- i'm currently working on #39 which cleans up these issues and will provide a clean |
reopening this issue as @molpopgen points out #39 doesn't provide a sufficient fix to the issues here |
i'd encourage you guys to check out the new pip package and confirm that it works on your systems. it should be able to be installed on a clean virtual environment simply with so far i've been able to confirm that this install works on a mac systems and linux |
Dear Andrew, RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd |
Aha-- this is important. The error is due to something being compiled against the numpy C API. This API is fickle. @andrewkern -- you probably have to pin the package to the exact numpy versions used, else the wheels will be very fragile. |
hi @jdaron -- yes I think this is a conda issue. in likelihood you have conflicting package versions in that old environment. can you try this again in a clean (brand new) conda install? i.e.,
|
I've been running the whole diploshic workflow in a virtual env and everything run smoothly, thanks a lot for making those updates. |
awesome-- great to hear. @molpopgen is this working on your systems too now? |
Haven't had time to test. Will try to in a few days. |
hey @molpopgen -- should we close this issue? |
No -- setup.py doesn't address this issues. There's no version numbers pinned/ranges pinned for tensorflow/keras. Also, the version numbers for this package make it difficult/impossible to realistically used. Adding a 3 to 0..3333 when bumping is still the same semver, so a user has a hard time pinning to anything other than exact versions. |
This package is currently rather difficult to get working due to tf/keras issues.
Installing current versions leads to import errors when training:
This is for the following versions in a clean venv:
Google searches suggest that the import error is fixed by installing earlier versions of tf. However, pip seems to reject that now:
The solution to this is to provide a
requirements.txt
that you have verified to work.The text was updated successfully, but these errors were encountered: