11–20 of 78 posts
Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.
You could pretty easily re-write your comment and say "Look at the trails Debian + apt have blazed. That's the right move."
Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.
This isn't very big news, in that virtualenv already provides pip in each new env, and you should not be using pip outside virtualenv -- unless it's to install virtualenv!
(Edit: Not that I don't like virtualenv when it's appropriate, but it really bugs me the wrong way when people just throw out generalizations like that)
Glorious day! As a person who went to PyCon and experienced first-hand the state of Python packaging, this is excellent news. Good luck to the Python devs in the days to come.
Yes! and with pip you can uninstall packages while with easy_install you can't
Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.
Isn't virtualenv going to be bundled too?
Nice reminder that pip is a dev tool and should be used as such. It makes sense to be included in Python.
This isn't very big news, in that virtualenv already provides pip in each new env, and you should not be using pip outside virtualenv -- unless it's to install virtualenv!
This isn't very big news, in that virtualenv already provides pip in each new env, and you should not be using pip outside virtualenv -- unless it's to install virtualenv!
This isn't very big news, in that virtualenv already provides pip in each new env, and you should not be using pip outside virtualenv -- unless it's to install virtualenv!
We're not all building web apps in python - virtualenv is not universally useful. (Edit: Not that I don't like virtualenv when it's appropriate, but it really bugs me the wrong way when people just throw out generalizations like that)