Re: Making sudo pip Safe

Currently, pip3 --user installed stuff can be updated with: pip3 install --upgrade --user $(pip3 list --user -o | cut -f 1 --delim=' ') But that isn't obvious/discoverable On Mon, Dec 12, 2016 at 8:48 AM Petr Viktorin wrote: > On 12/12/2016 01:39 PM, Neal Becker wrote: >

Re: Making sudo pip Safe

On 12/09/2016 06:09 PM, Orion Poplawski wrote: On 12/07/2016 05:53 AM, Michal Cyprian wrote: Hello, there is a long-standing problem that `sudo pip install` cannot be safely used in Fedora. Many users don't know about this and break python packages on theirs systems. Packages installed using

Re: Python 3.6, Fedora, and the "C" locale

On 12/10/2016 02:56 PM, Nick Coghlan wrote: Hi folks, One of the minor irritations with running Python 3 applications in Fedora containers is that those containers still default to the "C" local by default - you have to force "C.UTF-8" or "en_US.UTF-8" in order to tell Python that it should use

Re: Making sudo pip Safe

On 12/12/2016 05:39 AM, Nick Coghlan wrote: On 11 December 2016 at 01:33, Donald Stufft wrote: On Dec 10, 2016, at 8:10 AM, Nick Coghlan wrote: P.S. For folks wondering what the problem with "--user" is on Debian/Ubuntu, as far as I know it's mainly the

Re: Making sudo pip Safe

> If setuptools setup.py had something along the lines of a > "--sys-install" switch that would force the installation to /usr > rather than /usr/local, I could see us easily adapting our macros to > just do that all the time. It might even be something that the Debian > guys would switch to, as

Re: Python 3.6, Fedora, and the "C" locale

On 12 December 2016 at 16:18, Thomas Spura wrote: > Zbigniew Jędrzejewski-Szmek schrieb am Mo., 12. Dez. > 2016, 02:59: >> To make things less hand-wavy: there are concrete examples where this >> would be known to help: containers as mentioned in the