-
Notifications
You must be signed in to change notification settings - Fork 16
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
WHy can't we use biopython > 1.67 h #24
Comments
At the time we started the project it was biopython 1.67. When a new version came out we realised there was an incompatibility due to the fact they have deprecated and removed sub_features. |
Exactly 1.67? So I would have to downgrade my system to run your tool? |
You could give a try to version >1.68. If it works we can just exclude version 1.68. |
I agree conda envs are a solution to this, but |
I agree. For our defence we use it just a little, few core methods so it guess it should not be any big difference even after many years. |
Well, we got by by installing on a machine that was rather "clean", python-wise, so installation went through and everything worked. So, thank you for publishing your work. I'll keep in mind that conda would be another way. As much as I like Python as a language, the ecosystem really is a mess. ;) |
What is the ETA for version 2? |
Early 2019 :). We have re-developed the core of the tool to make it faster and add parallelisation, but since then we haven't had time to implement and test the numerous parameters we have in version 1. |
…e it compatible for biopython >1.67. Fix #24
…-gff>0.6.4. Specify numpy<1.16.5 in install_requires because it is the last version compatible with python 2.7
Thanks @Juke34 ! |
The text was updated successfully, but these errors were encountered: