Re: Broken pip

2018-08-31 Thread Michael F. Stemper
On 2018-08-29 16:02, Thomas Jollans wrote: > On 08/29/2018 09:05 PM, Michael F. Stemper wrote: >>> Also, PLEASE use Python 3. Still using Python 2 today is like still >>> using Windows XP in early 2013. >> I'm using the default version for the current release of my >> OS (Ubuntu 16.04 LTS): >> My

Re: Broken pip

2018-08-29 Thread Thomas Jollans
On 08/29/2018 09:05 PM, Michael F. Stemper wrote: I can certainly see a use case for user-specific versions of modules, and even user-specific presence of modules. For instance, at school, different researchers might need to have specific modules for their work. Possibly one person is doing some

Re: Broken pip

2018-08-29 Thread Michael F. Stemper
On 2018-08-29 03:10, Thomas Jollans wrote: > On 2018-08-28 20:10, Michael F. Stemper wrote: >> I'm trying to upgrade my pip on Ubuntu 16.04. I appear to have >> buggered things up pretty well. (Details follow) Any suggestions >> on how to undo this and get everything back to proper operation? >> >>

Re: Broken pip

2018-08-29 Thread Sivan Greenberg
I used to get into that sort of lib chaos but then a few years ago I stopped doing any python outside of virtualenv(s). My 2c is use it always, use it more and then you’re free to use pip as the only pkg manager for the project, with the occasional caveat that sometimes you require non python libs

Re: Broken pip

2018-08-29 Thread Thomas Jollans
On 2018-08-28 20:10, Michael F. Stemper wrote: > I'm trying to upgrade my pip on Ubuntu 16.04. I appear to have > buggered things up pretty well. (Details follow) Any suggestions > on how to undo this and get everything back to proper operation? > > Based on the information that I found at: >

Re: Broken pip

2018-08-28 Thread Gregory Ewing
Chris Angelico wrote: On 2018-08-28 13:19, Larry Martell wrote: source .bashrc I'm not sure what the point of it is, but maybe it's ensuring that your $PATH is set correctly. The installation you just did might have edited your .bashrc file (to modify PATH etc.), so it ensures that your curre

Re: Broken pip

2018-08-28 Thread Michael F. Stemper
On 2018-08-28 13:45, Chris Angelico wrote: > On Wed, Aug 29, 2018 at 4:37 AM, Michael F. Stemper > wrote: >> On 2018-08-28 13:19, Larry Martell wrote: >>> On Tue, Aug 28, 2018 at 2:10 PM, Michael F. Stemper >>> wrote: I'm trying to upgrade my pip on Ubuntu 16.04. I appear to have bugge

Re: Broken pip

2018-08-28 Thread Chris Angelico
On Wed, Aug 29, 2018 at 4:37 AM, Michael F. Stemper wrote: > On 2018-08-28 13:19, Larry Martell wrote: >> On Tue, Aug 28, 2018 at 2:10 PM, Michael F. Stemper >> wrote: >>> >>> I'm trying to upgrade my pip on Ubuntu 16.04. I appear to have >>> buggered things up pretty well. (Details follow) Any s

Re: Broken pip

2018-08-28 Thread Michael F. Stemper
On 2018-08-28 13:19, Larry Martell wrote: > On Tue, Aug 28, 2018 at 2:10 PM, Michael F. Stemper > wrote: >> >> I'm trying to upgrade my pip on Ubuntu 16.04. I appear to have >> buggered things up pretty well. (Details follow) Any suggestions >> on how to undo this and get everything back to proper

Re: Broken pip

2018-08-28 Thread Larry Martell
On Tue, Aug 28, 2018 at 2:10 PM, Michael F. Stemper wrote: > > I'm trying to upgrade my pip on Ubuntu 16.04. I appear to have > buggered things up pretty well. (Details follow) Any suggestions > on how to undo this and get everything back to proper operation? > > Based on the information that I fo