-
Notifications
You must be signed in to change notification settings - Fork 10
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
Non-absolute paths don't resolve #8
Comments
After looking into this, I think it would suffice to change within uLTRA lines 61-69 to
That is, removing the unnecessary line This would solve the issue of requiring an absolute path within the program and it doesn't require any change in the call to the program. Would this be good? |
I think so - but the verdict really is if it can run the nf-core unit tests. Not whether I like it or not. I can help with running some tests if you'd like. (or just pull down the test-module yourself and maybe replace the containers line to something local where you have your changes in) |
I implemented the change proposed above and I uploaded it as a new version of uLTRA to PyPI (v0.0.4.1 https://pypi.org/project/ultra-bioinformatics/). Let me know if this resolves the issue. |
Tested and validated 👍 |
Super, thanks! I'll close this then. |
Hi! We're trying to implement this package in nf-core modules, and it's stumbling on paths not being able to resolve, unless absolute. So basically, one have to do
\$(pwd)/$gtf
instead of just e.g../$gtf
. Makes it a little less clean to implement, any chance you could help with making the next version robust to this?It seems that this place is (one of) the offending lines. I'm thinking one could put in the
\$(pwd)/$gtf
logic inside the repo here, to keep it clean in the nf-core implementation. Would also help with general portability of code. I'm thinking just addingos.path.abspath
around the path calls would be enough:ultra/uLTRA
Lines 63 to 64 in a6b6fb0
The text was updated successfully, but these errors were encountered: