;
> Sent from Mail for Windows 10
>
> From: Chris Jerdonek
> Sent: 21 August 2018 19:58
> To: Tzu-ping Chung
> Cc: distutils sig
> Subject: Re: [Distutils] Re: pipenv and pip
>
> On Tue, Aug 21, 2018 at 4:02 AM, Tzu-ping Chung wrote:
> >
> > Pipe
// e: d...@danryan.co
From: Brett Cannon [mailto:br...@python.org]
Sent: Tuesday, August 21, 2018 1:22 PM
To: Paul Moore
Cc: Distutils
Subject: [Distutils] Re: pipenv and pip
Since this ties into what's being discussed, I'll mention that on pypa-dev I
created an outline of where I saw h
mailto:pradyu...@gmail.com]
> Sent: Tuesday, August 21, 2018 1:26 PM
> To: Tzu-ping Chung
> Cc: Dan Ryan; DistUtils Mailing List
> Subject: Re: [Distutils] Re: pipenv and pip
>
> Hey!
>
> On Tue, Aug 21, 2018 at 7:51 PM Tzu-ping Chung
> wrote:
> >
> >
for Windows 10
>
>
>
> From: Dan Ryan
> Sent: 21 August 2018 22:03
> To: Tzu-ping Chung
> Cc: Chris Jerdonek; distutils sig
> Subject: Re: [Distutils] Re: pipenv and pip
>
>
>
> There was a specific bug related to pipenv-only functionality which is why
> the vcs re
Since this ties into what's being discussed, I'll mention that on pypa-dev
I created an outline of where I saw holes in library support and specs in
order to be able to re-constitute pip just from libraries (mostly for the
wheel case): https://groups.google.com/forum/#!topic/pypa-dev/91QdZ1vxLT8 .
://github.com/sarugaku/resolvelib
Sent from Mail for Windows 10
From: Dan Ryan
Sent: 21 August 2018 22:03
To: Tzu-ping Chung
Cc: Chris Jerdonek; distutils sig
Subject: Re: [Distutils] Re: pipenv and pip
There was a specific bug related to pipenv-only functionality which is why the
vcs ref is obtained. Pip
Thanks for the feedback, and sorry for the disturbance.
TP
Sent from Mail for Windows 10
From: Chris Jerdonek
Sent: 21 August 2018 19:58
To: Tzu-ping Chung
Cc: distutils sig
Subject: Re: [Distutils] Re: pipenv and pip
On Tue, Aug 21, 2018 at 4:02 AM, Tzu-ping Chung wrote:
>
> Pipenv main
On Tue, 21 Aug 2018 at 12:04, Tzu-ping Chung wrote:
>
> Hi,
>
> Dan and I had been doing most of the maintenance work for Pipenv recently,
> and as Dan mentioned,
> we have been working on some related projects that poke into pip internals
> significantly, so I feel I
> should voice some opinion
a the World Wide Web, visit
> https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
> or, via email, send a message with subject or body 'help' to
> distutils-sig-requ...@python.org
>
> You can reach the person managing the list at
> distutils-sig-ow.
> distutils-sig-ow...@python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Distutils-SIG digest..."Today's Topics:
>
> 1. Re: pipenv and pip (Dan Ryan)
> 2. Re: pipenv and pip (Dan Ryan)
>
> F
On Mon, Aug 20, 2018 at 2:52 AM Wes Turner wrote:
> What stable API would be worth maintaining in pip for others to use?
>
Just to be clear, nothing in my comments was meant to suggest maintaining a
stable API. There are other kinds of things pip could do to make it easier
for pipenv that don’t
How would I (said library) maintain compatibility? I’m pretty clever. The shim
library doesn’t actually do anything besides provide import paths. If I shim
something that didn’t exist, it shims None for any pip versions where it
doesn’t exist. So for example if you are running pip 9 and you imp
The truth is that it’s basically impossible to gauge bugs in pip vs bugs in our
patches to it which are often a lot more likely — reproductions of edge cases
can be impossible but there are specific things I know we broke (like parsing
certain kinds of extras, previously) — mostly bugs land in p
I actually maintain a separate library for parsing requirements which relies
mainly on packaging and which provides a backing implementation for moving
between requirements files and Pipfile format. It relies on some pip internals
(InstallRequirement specifically) for avoiding rework. As of rece
On Mon, Aug 20, 2018, 7:45 AM Paul Moore wrote:
> On Mon, 20 Aug 2018 at 13:21, Wes Turner wrote:
> >
> > Something as simple as reading a requirements.txt file into JSON must
> either reimplement or wrongly import from pip._internal.
>
> Or copy pip's code and maintain it locally...
>
> > Anywa
On Mon, 20 Aug 2018 at 13:21, Wes Turner wrote:
>
> Something as simple as reading a requirements.txt file into JSON must either
> reimplement or wrongly import from pip._internal.
Or copy pip's code and maintain it locally...
> Anyways,
> Tool authors reimplementing in particular the requireme
Something as simple as reading a requirements.txt file into JSON must
either reimplement or wrongly import from pip._internal.
Anyways,
Tool authors reimplementing in particular the requirements.txt
functionality shouldn't be necessary.
On Monday, August 20, 2018, Paul Moore wrote:
> On Mon, 20
On Mon, 20 Aug 2018 at 12:25, Wes Turner wrote:
>
> On Monday, August 20, 2018, Paul Moore wrote:
>> I know "security by obscurity" doesn't work, but I'm happier if
>> details of this library *aren't* widely known - it's not something I'd
>> want to encourage people using, nor is it supported by
On Monday, August 20, 2018, Paul Moore wrote:
> On Mon, 20 Aug 2018 at 10:54, Wes Turner wrote:
> >
> > What stable API would be worth maintaining in pip for others to use?
>
> That's probably the sort of question that can only be usefully
> answered by projects like pipenv identifying the funct
On Mon, 20 Aug 2018 at 10:54, Wes Turner wrote:
>
> What stable API would be worth maintaining in pip for others to use?
That's probably the sort of question that can only be usefully
answered by projects like pipenv identifying the functionality they
need and proposing something. Which is of cou
What stable API would be worth maintaining in pip for others to use?
"[Distutils] Announcement: Pip 10 is coming, and will move all internal
APIs"
https://groups.google.com/forum/m/#!topic/pypa-dev/JVTfS6ZdAuM
On Monday, August 20, 2018, Chris Jerdonek wrote:
> Thanks. Is the state of affairs
Thanks. Is the state of affairs as you described them what you're
planning for the future as well, or do you anticipate any changes
worthy of note?
Also, are any of the bugs filed in pipenv's tracker due to bugs or
rough spots in pip -- is there a way to find those, like by using a
label? It would
Sure I can grab that— we patch pip because we use some internals to handle
resolution and we have some bugs around that currently. They aren’t upstreamed
because they aren’t actually present in pip, only in pipenv. Pipenv crosses
back and forth across the virtualenv boundary during the process.
23 matches
Mail list logo
