Skip to content

Install pip by default? #1

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

Closed
samalba opened this issue Jul 15, 2014 · 5 comments · Fixed by #2
Closed

Install pip by default? #1

samalba opened this issue Jul 15, 2014 · 5 comments · Fixed by #2

Comments

@samalba
Copy link

samalba commented Jul 15, 2014

Would it make sense to include pip by default?

@tianon
Copy link
Member

tianon commented Jul 15, 2014

For python:3, it's included in upstream Python already, so:

$ docker run --rm python:3 pip --version
pip 1.5.6 from /usr/local/lib/python3.4/site-packages (python 3.4)

Do you mean we should include it in the python:2 image manually after we build Python?

@samalba
Copy link
Author

samalba commented Jul 15, 2014

right, I am using python:2

No big deal though, I just added the following in my dockerfile:

run curl https://bootstrap.pypa.io/get-pip.py | python

@tianon
Copy link
Member

tianon commented Jul 15, 2014

I think the thing we need to be cognitive of is whether this is something all users of this image would likely want, and I think the answer to that here is probably a resounding "yes", because let's be honest, Python without Pip is pretty irritating. :)

@tianon
Copy link
Member

tianon commented Jul 15, 2014

I'll send a PR to fix this shortly.

@samalba
Copy link
Author

samalba commented Jul 15, 2014

awesome

tianon pushed a commit that referenced this issue Dec 31, 2015
Adjust whitespace for better symmetry between Dockerfiles and cut image size in half by keeping fetch and compile in the same layer so the Python source goes away properly
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 a pull request may close this issue.

2 participants