Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #97143 > unrolled thread
| Started by | Zachary Ware <zachary.ware+pylist@gmail.com> |
|---|---|
| First post | 2015-09-26 13:59 -0500 |
| Last post | 2015-09-26 13:59 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Failed to upgrade pip in fresh 2.7 install Zachary Ware <zachary.ware+pylist@gmail.com> - 2015-09-26 13:59 -0500
| From | Zachary Ware <zachary.ware+pylist@gmail.com> |
|---|---|
| Date | 2015-09-26 13:59 -0500 |
| Subject | Re: Failed to upgrade pip in fresh 2.7 install |
| Message-ID | <mailman.182.1443294025.28679.python-list@python.org> |
On Sat, Sep 26, 2015 at 1:13 PM, <paul.hermeneutic@gmail.com> wrote: > After a fresh install of Python 2.7 32-bit and 64-bit, upgrading pip > using pip fails. Am I doing this incorrectly? Any suggestions? This is a limitation of Windows: you can't replace the executable that you're currently running. To work around this, do "python -m pip install --upgrade pip" instead. If you have the Python Launcher for Windows installed (included with Python 3.3+), you can use in place of 'python' in that command, and be very sure about which python's pip is being upgraded. -- Zach
Back to top | Article view | comp.lang.python
csiph-web