-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HiSAT2 with Python 3k #18911
Comments
@pvanheus can you please comment here? |
What’s the best course of action here? Shall I prep a PR enabling Py3k builds again? |
I updated the The CI tests seemed to pass. Testing functionality now, but I think that this may be fixed now..? 🤞 |
It's a slightly obscure test, but the nf-core/methylseq pipeline now runs with bismark using HiSAT2 on a python 3k environment inside a docker container! 😆 https://travis-ci.com/nf-core/methylseq/jobs/263630208 I'm happy with this, so will close this issue now. |
Hi all,
https://bioconda.github.io/contributor/guidelines.html states that "packaging is hard" - I agree! 😆 But one of the examples is:
Sure enough, the build recipe does run
2to3
:bioconda-recipes/recipes/hisat2/build.sh
Lines 5 to 20 in 9062056
However, the meta.yml file then skips python 3k builds:
bioconda-recipes/recipes/hisat2/meta.yaml
Line 13 in 9062056
So despite making the code python 3 compatible, HiSAT2 ends up being available for Python 2 only.
This skipped build was added by @pvanheus and @bgruening last year in #9973 - can you guys remember why? Do you think it's possible to add python 3 support back again?
Phil
The text was updated successfully, but these errors were encountered: