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

Add option to pin packages considered unsafe in pip-compile #377

Merged
merged 5 commits into from
Jul 9, 2016

Conversation

alekzvik
Copy link
Contributor

@alekzvik alekzvik commented Jul 8, 2016

Due to some specifics I had to include some version of pip in dependencies in several projects.
I am not sure it is needed for everyone, so I added a flag to have an option to enable that.

@nvie
Copy link
Member

nvie commented Jul 9, 2016

Can you remove the short option (-u) and rename this option (both internally and externally) to --allow-unsafe? Otherwise, looks good to me. Thanks!

@nvie nvie merged commit c5665f5 into jazzband:master Jul 9, 2016
@nvie
Copy link
Member

nvie commented Jul 9, 2016

Thanks!

@alekzvik
Copy link
Contributor Author

alekzvik commented Jul 9, 2016

Thank you for a great project.

@nvie, When do you plan to release this on PyPI?

@nvie
Copy link
Member

nvie commented Jul 12, 2016

I might roll a new version some evening this week.

@borgstrom
Copy link

@nvie Is there anything else holding up 1.7.1 from landing in PyPI with the addition of --allow-unsafe? I too have run into a situation where I want to include 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

Successfully merging this pull request may close these issues.

3 participants