Skip to main content

Timeline for answer to Dealing with multiple Python versions and PIP by bwinton

Current License: CC BY-SA 4.0

Post Revisions

11 events
when toggle format what by license comment
Mar 28, 2025 at 0:45 history edited Peter Mortensen CC BY-SA 4.0
Active reading [<https://en.wikipedia.org/wiki/Python_%28programming_language%29>].
Feb 22, 2016 at 16:55 comment added llrs To call a module of python you should use python2.7 -m pip install PackageName
Apr 30, 2015 at 22:28 comment added raul Also, /path/to/pip is this: python2.{5,6}/Scripts/pip2.{5,6}
Mar 16, 2014 at 19:49 history edited bwinton CC BY-SA 3.0
corrected the minor mistake of what to do when pip wasn&#39;t installed in all the python versions.; Post Made Community Wiki
Mar 2, 2014 at 2:21 review Suggested edits
Mar 2, 2014 at 2:22
Mar 2, 2014 at 2:07 comment added RobotHumans I'm baffled that the problem with the importerror got more upticks than the solution to the same one comment above it.
Feb 7, 2014 at 8:36 comment added Marco Same as @Cerin "ImportError: No module named pkg_resources"
Oct 2, 2012 at 1:18 comment added Cerin "ImportError: No module named pkg_resources"
Apr 18, 2012 at 13:17 comment added Mike Vella For this to work on say python 3 you need to download pip and do "python3 setup.py install". Personally I find this solution to be not very nice. For a start I didn't even know the pip command wasn't a binary. This isn't a criticism of @bwinton, I'm just surprised there isn't a better way to do this.
May 11, 2010 at 19:38 vote accept David Wolever
Apr 8, 2013 at 19:04
May 11, 2010 at 16:43 history answered bwinton CC BY-SA 2.5