Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #197405
| From | Grant Edwards <grant.b.edwards@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Pip installs to unexpected place |
| Date | 2025-04-15 18:07 -0400 |
| Message-ID | <mailman.11.1744754828.3008.python-list@python.org> (permalink) |
| References | <CAApdmf2J69WgkR159sBSkxN0=mYoNmHZYboBmpPi+LdA-YBNpg@mail.gmail.com> <CAN06=CxPNLHtr_sdgphR2jrN1V+WbB8wZDJdbvfEDb-MYtmPHA@mail.gmail.com> <bbe32f47-13d2-459c-af22-4e0e37834091@tompassin.net> <4ZcdYR5WnWznV1q@mail.python.org> |
On 2025-04-15, Thomas Passin via Python-list <python-list@python.org> wrote: > On Linux, at least, it's standard for pip to install into the user's > site-packages location if it's not invoked with admin privileges - even > without --user. Pip will emit a message saying so. Well, that used to be > true but nowadays Pip wants you to use the --break-system-packages flag > if you want to insist on installing into the system's Python install, > even if it's going to go into --user. I've always been a little baffled by that message when installing with --user. How can that possibly break system stuff?
Back to comp.lang.python | Previous | Next | Find similar
Re: Pip installs to unexpected place Grant Edwards <grant.b.edwards@gmail.com> - 2025-04-15 18:07 -0400
csiph-web