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

Install Cornice from PyPi #35

Merged
merged 1 commit into from
Oct 7, 2015
Merged

Install Cornice from PyPi #35

merged 1 commit into from
Oct 7, 2015

Conversation

tsauerwein
Copy link
Member

Cornice 1.1.0 was released last week, which includes Cornices/cornice#309, so that we no longer need to install from the GitHub repository.

With release 1.1.0 we no longer need to install from the Git repo.
@elemoine
Copy link
Contributor

elemoine commented Oct 7, 2015

LGTM.

tsauerwein pushed a commit that referenced this pull request Oct 7, 2015
@tsauerwein tsauerwein merged commit f7bfda9 into master Oct 7, 2015
@tsauerwein tsauerwein deleted the cornice_1.1.0 branch October 7, 2015 11:32
@asaunier
Copy link
Member

asaunier commented Oct 7, 2015

By the way, would it be relevant to fix the "requires" versions?

@tsauerwein
Copy link
Member Author

@asaunier
Copy link
Member

asaunier commented Oct 7, 2015

Yes
The current way is great to get up-to-date depencies but we don't really control what version will be installed.

@tsauerwein
Copy link
Member Author

Ah I see, you mean to set a fixed version for all dependencies? That would make sense.

@elemoine
Copy link
Contributor

elemoine commented Oct 7, 2015

It makes sense. The dependency versions should be set in the requirements.txt file as opposed to setup.py.

@asaunier asaunier mentioned this pull request Oct 7, 2015
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