Hi Julian (2023.03.05_10:47:08_+)
> the NEWS file for python3.11. The
> /usr/lib/python3.11/EXTERNALLY-MANAGED file is not mentioned there
It was mentioned, but I've expanded on that in 3.11.2-5, and even more
in the next upload:
https://salsa.debian.org/cpython-team/python3/-/blob/master/de
(sorry for replying to a random message, I am not subscribed to the list)
I don't use `sudo pip`, too risky. I used to use pip to install packages
with the implicit --user option (for things not available via apt). And I
am aware of --break-system-packages, I used it the first time pip
complai
FWIW, I am one of those power users that develop python applications and
prefer the simplicity of a single environment. In my personal experience,
installing using `sudo pip` (or user pip, which I don't do at all) is not a
frequent operation for users that choose to manage a single environment.
Per
On Fri, Mar 03, 2023 at 04:22:11PM -0500, Jorge Moraleda wrote:
> Jeremy, Thank you for your quick reply!
>
> I did not know about `sudo pip install --break-system-packages foo` or `sudo
> rm
> /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly I only knew about this issue
> what I have read on th
On 2023-03-03 16:22:11 -0500 (-0500), Jorge Moraleda wrote:
> I did not know about `sudo pip install --break-system-packages
> foo` or `sudo rm /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly
> I only knew about this issue what I have read on this discussion).
[...]
They come from a reading of th
Jeremy, Thank you for your quick reply!
I did not know about `sudo pip install --break-system-packages foo` or
`sudo rm /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly I only knew about
this issue what I have read on this discussion). This is very helpful and
it really changes my outlook on this
On 2023-03-03 15:29:09 -0500 (-0500), Jorge Moraleda wrote:
> Would it be hard to support both philosophies?
>
> I would like to suggest a couple of configuration options that by default
> disallow using pip outside a virtual environment but that users with root
> privilege can modify by editing a
Hi all,
On Fri, Mar 03, 2023 at 04:10:50PM +0100, Marc Glisse wrote:
> Hello,
>
> I recently reported
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032283 , and Dmitry
> suggested discussing it on this mailing list.
>
> Virtual environments work by adding some version of Python (possibly ju
Would it be hard to support both philosophies?
I would like to suggest a couple of configuration options that by default
disallow using pip outside a virtual environment but that users with root
privilege can modify by editing a config file (probably somewhere in /etc)
and that would enable using
On 2023-03-03 18:44:19 + (+), Danial Behzadi دانیال بهزادی wrote:
> You just want to install sphinx via pip in the virtual environment
> too. Each venv should be atomic and isolated which means not
> depended to system packages.
However a venv can be made to use system packages if you use
You just want to install sphinx via pip in the virtual environment too. Each
venv should be atomic and isolated which means not depended to system packages.
Hello,
I recently reported
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032283 , and Dmitry
suggested discussing it on this mailing list.
Virtual environments work by adding some version of Python (possibly just
a symlink to the system one) at the beginning of PATH. Debian policy for
12 matches
Mail list logo
