Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14970

Re: #!/usr/bin/python3 vs virtualenv

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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.
Personally, I use it only after searching in apt and confirming the package
is not there. Having to type --break-system-packages every time when I have
to do it is a good solution for me that I find completely reasonable.

Thank you!

On Sun, Mar 5, 2023 at 5:47 AM Julian Gilbey <julian@d-and-j.net> wrote:

> 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 this discussion). This is very helpful and it really
> changes
> > my outlook on this topic.
>
> The --break-system-packages option is noted in
> /usr/share/doc/python3.11/README.venv, and this file is mentioned in
> the NEWS file for python3.11.  The
> /usr/lib/python3.11/EXTERNALLY-MANAGED file is not mentioned there; I
> personally think that having to type --break-system-packages every
> time one installs a package via pip globally or on a per-user basis is
> safer, as it reminds you that you run risks doing so.
>
> Best wishes,
>
>    Julian
>

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

#!/usr/bin/python3 vs virtualenv Marc Glisse <marc.glisse@inria.fr> - 2023-03-03 16:30 +0100
  Re: #!/usr/bin/python3 vs virtualenv Danial Behzadi دانیال بهزادی <dani.behzi@ubuntu.com> - 2023-03-03 19:50 +0100
    Re: #!/usr/bin/python3 vs virtualenv Jeremy Stanley <fungi@yuggoth.org> - 2023-03-03 20:20 +0100
      Re: #!/usr/bin/python3 vs virtualenv Jorge Moraleda <jorge.moraleda@gmail.com> - 2023-03-03 21:30 +0100
        Re: #!/usr/bin/python3 vs virtualenv Jeremy Stanley <fungi@yuggoth.org> - 2023-03-03 21:50 +0100
          Re: #!/usr/bin/python3 vs virtualenv Jorge Moraleda <jorge.moraleda@gmail.com> - 2023-03-03 22:30 +0100
            Re: #!/usr/bin/python3 vs virtualenv Jeremy Stanley <fungi@yuggoth.org> - 2023-03-03 22:50 +0100
            Re: #!/usr/bin/python3 vs virtualenv Julian Gilbey <julian@d-and-j.net> - 2023-03-05 11:50 +0100
              Re: #!/usr/bin/python3 vs virtualenv Jorge Moraleda <jorge.moraleda@gmail.com> - 2023-03-05 13:00 +0100
              Re: #!/usr/bin/python3 vs virtualenv Stefano Rivera <stefanor@debian.org> - 2023-03-09 23:40 +0100
    Re: #!/usr/bin/python3 vs virtualenv Marc Glisse <marc.glisse@inria.fr> - 2023-03-05 14:20 +0100
  Re: #!/usr/bin/python3 vs virtualenv Dmitry Shachnev <mitya57@debian.org> - 2023-03-03 21:50 +0100

csiph-web