On Mon, Oct 12, 2015 at 02:16:58PM -0700, Jeff Quast wrote:
> 
> > On Oct 12, 2015, at 2:03 PM, Paul Hargreaves 
> > <paul.hargrea...@technowizardry.co.uk> wrote:
> > 
> > Likely this is because BSD is still at 3.4:
> > $ python3 --version
> > Python 3.4.3
> 
> I maintain a FreeBSD build slave, and 3.5 is most certainly available as of a 
> few weeks ago, I just reviewed my “history” output there. You may issue 
> commands:
> 
> $ sudo pkg update
> $ sudo pkg add python35
> 
> FreeBSD ships pip as a package. I suggest not to install it through freebsd, 
> but rather using get-pip.py(*).
> 
> $ sudo python3.5 get-pip.py

Why not 'sudo python3.5 -m ensurepip'?  It's basically get-pip.py,
included in the standard library since 3.4.

> (*)As pip updates itself, and installs and updates all other python packages, 
> I am against the operating system managing anything but the python 
> interpreter by principal.
> 
> For example, when attempting to perform a “pkg" upgrade of all installed 
> python packages through freebsd, it will downgrade pip and many others as it 
> “uninstalls” something pip may have later upgraded without its knowledge, 
> producing bad state in the site-packages folder.

Marius Gedminas
-- 
Colorless green ideas sleep furiously.

Attachment: signature.asc
Description: Digital signature

_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality

Reply via email to