FWIW we are using quite a bit of the internal api. My plan was to go over this
once we cut over to the new warehouse uris. Of note might be the fact that
pip-tools is a core dependency we bundle in pipenv and the current maintainer
is a pipenv maintainer as well. For our specific case we have
On 15 April 2018 at 07:31, Donald Stufft wrote:
>
> On Apr 14, 2018, at 4:57 PM, Matthew Brett wrote:
>
> Is the suggestion to use the `_internal` import, or carry a copy of
> the pep425tags code myself, that I have to keep up to date with the
>
> On Apr 14, 2018, at 4:57 PM, Matthew Brett wrote:
>
> Is the suggestion to use the `_internal` import, or carry a copy of
> the pep425tags code myself, that I have to keep up to date with the
> internal pip copy? That would also involve me copying the `glibc`
> part
Hi,
On Sun, Oct 22, 2017 at 8:52 AM, Elvis Stansvik
wrote:
> 2017-10-21 14:34 GMT+02:00 Paul Moore :
>> On 21 October 2017 at 12:15, Nick Coghlan wrote:
>>> (Note: this is entirely speculative, and I have no idea how hard it
> On Oct 21, 2017, at 10:30 PM, Nick Coghlan wrote:
>
> However, none of that impacts the question of whether `pip.main()` runs code
> in the current process or implicitly runs it in a subprocess - `pip` doesn't
> import the modules it installs either way, so it will all
On 22 October 2017 at 04:03, xoviat wrote:
> Nick:
>
> That's generally a good idea, but one significant problem that can occur
> is that the Python import system will cache certain libraries, people will
> run "pip install," and then they will expect such libraries to be
>
On 21 October 2017 at 12:15, Nick Coghlan wrote:
> (Note: this is entirely speculative, and I have no idea how hard it would
> be, so please read it as the question it's intended to be)
No problem - I don't know myself how hard some of this would be, either ;-)
> Do you know
On 21 October 2017 at 20:03, Paul Moore wrote:
> Likely the biggest problems will be for people who call into the pip
> resolver and build APIs, as I don't know of any alternatives out
> there. But they were *definitely* breaking anyway, as we've made major
> changes to that
While I understand that pip itself has to be very careful about edge cases and
all the pathological things you can do in setup.py, as a higher-level tooling
author my priorities are on the happy path UX and speed is a big factor there.
So yes, using PackageFinder is potentially inaccurate, but
> On Oct 20, 2017, at 9:30 AM, Paul Moore wrote:
>
> On 20 October 2017 at 14:26, Matthew Brett wrote:
>> Thanks for the heads-up.
>>
>> Will y'all be doing a PyPI pre-release so we can test with `pip
>> install --pre -U pip`?
>
> We've not yet
On 20 October 2017 at 14:55, Jannis Gebauer wrote:
> Thanks for the heads-up, Paul.
>
> I’m currently using `pip.get_installed_distributions` and as far as I can
> see that has moved into `_internal`, too:
>
On 20 October 2017 at 14:26, Matthew Brett wrote:
> Thanks for the heads-up.
>
> Will y'all be doing a PyPI pre-release so we can test with `pip
> install --pre -U pip`?
We've not yet decided on that. Traditionally I don't think we have
done so, but I'm inclined to think
12 matches
Mail list logo