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

How do we feel about dependencies? #7

Open
Zulko opened this issue Feb 12, 2020 · 2 comments
Open

How do we feel about dependencies? #7

Zulko opened this issue Feb 12, 2020 · 2 comments

Comments

@Zulko
Copy link
Contributor

Zulko commented Feb 12, 2020

Few dependencies is a nice trait in a library. Biopython's only dependency seems to be Numpy.

I am asking because Plateo depends on a few heavy libraries (the core can be standalone, but dealing with spreadsheets is easier with Pandas/xlrd), and I expect other modules may depend on at least Biopython and a few others.

@neilswainston
Copy link
Contributor

neilswainston commented Feb 14, 2020 via email

@zoltuz
Copy link

zoltuz commented Feb 16, 2020

I agree, being mindful about the dependencies will pay dividends in the long run for sure. But as long as they are pip installable it should be fine.

Alternatively, we can put a script together which creates/updates a (docker) container that encapsulates all (not just python) dependences.
https://docs.docker.com/compose/gettingstarted/

Recently, Netflix released its in-house software called Metaflow. One of the features of Metaflow is the capability to run/test out the python code on different external library versions to weed out dependency related issue (in their case, mostly in the result of the computation, e.g. output of a data science model).
https://docs.metaflow.org/metaflow/dependencies

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

No branches or pull requests

3 participants