Skip to content
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

Abstracting out File IO #57

Open
mortonjt opened this issue Mar 6, 2016 · 0 comments
Open

Abstracting out File IO #57

mortonjt opened this issue Mar 6, 2016 · 0 comments
Labels

Comments

@mortonjt
Copy link
Collaborator

mortonjt commented Mar 6, 2016

Looking over all of the bfillings commands, most of the inputs and outputs are filepaths. This is a bit cumbersome, since it is requiring the user specify every input and output filepath if they wanted access the python API.

I think it would be much more preferable to abstract out the file IO and pass around iterators of Sequence objects. This would ultimately save time and trouble bookkeeping.

If we go down this route, we'd need to consider where will temporary files be stored/created. This would definitely be useful to have around for debugging purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant