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 to deploy ranged version for library #74

Closed
gsemet opened this issue May 27, 2017 · 1 comment
Closed

How to deploy ranged version for library #74

gsemet opened this issue May 27, 2017 · 1 comment

Comments

@gsemet
Copy link

gsemet commented May 27, 2017

Hello.

I differential python library to "application". A library ends up typically on pypi to be used by another application. One should never do a pip install thislibrary in production. Should comes from a pip install thisapplication that consequently install other apps and libraries.

For me, application should indeed have frozen dependencies, to ensure perfect reproduction. But libraries deployed on pypi should better be using "range" for acceptable version. For exemple, if two libraries depends on frozen version of another lib (say 1.0 and 2.0), there will be a conflict. Libraries dependencies are better described with range (I know my lib will work with this dependencies from version 1.0 to 3.0, or require a version >1.1, and so on).

Is it possible to do this with the pipfile and how? It is possible to describe this subtility in the documentation? "How to handle dependencies of a library or an application" ?

Thanks

@kennethreitz
Copy link
Contributor

Same way you do with pip.

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

2 participants