-
Notifications
You must be signed in to change notification settings - Fork 11
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
--output_file does not work properly #2
Comments
Hello @marade. Thanks for pointing this out. Could you please share the error log with me to have a better idea of how to fix this? |
sequence.gb is a file downloaded from GenBank today: $ genovi -o genovi/blah -i sequence.gb -s complete |
Hi @marade. I apologize for the delay in replying. I have committed an update related to the handling of relative paths. It is not yet included in the installable version of GenoVi, but you can find it in the Github repo. It will soon be added to a new version which will include other improvements. Please do let us know if you have further quesitons. |
Sounds good @arodel21. Thanks! |
I tried using GenoVi again and found that relative paths still don't work. I see there's a commit related to this here: The code for this commit is not nearly sufficient to address the problem. I'd like to emphasize that GenoVi is fundamentally broken when it comes to handling paths. I'll recommend again extensive use of Pathlib Path().absolute() or os.path.abspath() so that you can handle relative paths correctly. |
Specifying an output directory with a relative path causes errors, e.g. this fails:
$ mkdir genovi
$ genovi -o genovi/blah ...
Parsing path input with Pathlib Path(args.outfile).absolute() or os.path.abspath(args.outfile) would fix this.
The text was updated successfully, but these errors were encountered: