On Wed, Feb 24, 2021 at 07:59:55PM -0800, Christopher Barker wrote:
> I used to do that — for years. But it really did cause problems.
>
> The trick is that you have, say, your 57 apps all working. Then you need to
> update a package for one. As soon as you update, you have to go test your
> 57
Is there a tool that (1) detects import name collisions; and (2) attempts
to read package metadata and package file checksums (maybe from the ZIP
'manifest')?
In order to:
- troubleshoot module shadowing issues
- $PATH
- sys.path
- `python -m site`
- incomplete and overlapping
On Thu, 25 Feb 2021 at 19:22, Mike Miller wrote:
> Mr. Random had an interesting point to start this thread, that over-reliance
> on
> venvs may have slowed fixes and improvements on the standard tools and
> distributions. I suspect there is some truth to the assertion.
Arguably, your claim
On 2021-02-24 19:59, Christopher Barker wrote:
I used to do that — for years. But it really did cause problems.
The trick is that you have, say, your 57 apps all working. Then you need to
update a package for one. As soon as you update, you have to go test your 57
apps, and if one of them is
> > I have currently 57 apps installed via pipx on my laptop, and the 57
> > environments take almost 1 GB already.
That is a lot! But give conda a try: conda uses hard links, so no wasted
space when packages are the same.
I never understood the fear around version conflicts.
I don’t know
On 2021-02-24 02:52, Stéfane Fermigier wrote:
> I have currently 57 apps installed via pipx on my laptop, and the 57
> environments take almost 1 GB already.
I never understood the fear around version conflicts. Perhaps it has to do with
the decline of sys-admin skills over the years? So,
I accidentally removed Python-Ideas from the recipient list while posting this
reply.
On Wed, Feb 24, 2021, at 09:16, Random832 wrote:
> On Wed, Feb 24, 2021, at 06:27, Christian Heimes wrote:
> > Separate directories don't prevent clashes and system breakage. But they
> > provide an easy way to
On Wed, 24 Feb 2021 at 13:12, Antoine Pitrou wrote:
>
> On Wed, 24 Feb 2021 13:47:40 +0100
> Stéfane Fermigier wrote:
> > The 3rd solution is probably the best of the 3, but the sharing mechanism
> > still needs to be specified (and, if needed, implemented) properly.
>
> I wouldn't want to
On Wed, 24 Feb 2021 13:47:40 +0100
Stéfane Fermigier wrote:
> On Wed, Feb 24, 2021 at 12:42 PM Paul Moore
> wrote:
>
> > On Wed, 24 Feb 2021 at 10:55, Stéfane Fermigier
> > wrote:
> > > There is probably a clever way to reuse common packages (probably via
> > clever symlinking) and
On Wed, Feb 24, 2021 at 1:47 PM Stéfane Fermigier wrote:
>
> So IMHO the best way to implement solution 3 would be by using some
> variant of the approach popularized by Nix (repository of immutable
> packages + links to each virtualenv).
>
Another benefit of this kind of approach, besides
On Wed, Feb 24, 2021 at 12:42 PM Paul Moore wrote:
> On Wed, 24 Feb 2021 at 10:55, Stéfane Fermigier wrote:
> > There is probably a clever way to reuse common packages (probably via
> clever symlinking) and reduce the footprint of these installations.
>
> Ultimately the problem is that a
On Wed, 24 Feb 2021 at 10:55, Stéfane Fermigier wrote:
> There is probably a clever way to reuse common packages (probably via clever
> symlinking) and reduce the footprint of these installations.
Ultimately the problem is that a general tool can't deal with
conflicts (except by raising an
On 24/02/2021 11.52, Stéfane Fermigier wrote:
> I love pipx and I'm glad it exists at this point because it make
>
> The main issue is that each virtualenv takes space, lots of space.
>
> I have currently 57 apps installed via pipx on my laptop, and the 57
> environments take almost 1 GB
On Wed, Feb 24, 2021 at 11:43 AM Henk-Jaap Wagenaar <
wagenaarhenkj...@gmail.com> wrote:
>
>>
> I've been using pyenv (on MacBooks to be fair, not Linux/Debian) and been
> quite happy with that, and it basically does what Jonathan does manually:
> clone the github repo and build python from
I love pipx and I'm glad it exists at this point because it make
The main issue is that each virtualenv takes space, lots of space.
I have currently 57 apps installed via pipx on my laptop, and the 57
environments take almost 1 GB already.
~ cd .local/pipx/venvs/
~/.l/p/venvs ls
On Wed, 24 Feb 2021 at 10:18, Antoine Pitrou wrote:
> On Tue, 23 Feb 2021 20:29:52 -0500
> Jonathan Goble wrote:
> >
> > I can't speak for distributors or maintainers [1], but I can speak for
> > myself as a user. I run Debian testing (currently bullseye as that is
> > preparing for release) as
16 matches
Mail list logo
