Skip to content

Conversation

@joverlee521
Copy link
Contributor

Description of proposed changes

Add min_version in the shared remote_files.smk so that individual workflows that import it don't have to remember to add the version check.

Based on feedback from @victorlin in mpox
nextstrain/mpox#339 (comment)

Checklist

  • Checks pass
  • If adding a script, add an entry for it in the README.

Add `min_version` in the shared `remote_files.smk` so that individual workflows 
that import it don't have to remember to add the version check. 

Based on feedback from @victorlin in mpox
<nextstrain/mpox#339 (comment)>
Copy link
Member

@victorlin victorlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for considering! This is a small suggestion but also a new way of doing things in nextstrain/shared, so I'm curious what others think.

I think it's analogous to something like Augur's pandas version constraints, which are declared in package metadata and checked by pip/conda at install time. Since nextstrain/shared is installed by simply copying the contents of the repo with no checks, the only way to check dependency versions is at run time such as in this PR.

In addition to this, individual phylogenetic workflows can still declare and check their own minimum Snakemake versions in Snakefile.

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

Successfully merging this pull request may close these issues.

3 participants