According to the documentation[1], TestPyPI is a complete independent instance
from PyPI, and they don’t share databases at all. You need to register a
separate account there.
[1]: https://packaging.python.org/guides/using-testpypi/
--
Tzu-ping Chung (@uranusjr)
uranu...@gmail.com
Sent from my
On Mon, 20 Aug 2018 at 18:54, Thomas Kluyver wrote:
>
> On Mon, Aug 20, 2018, at 2:52 PM, Paul Moore wrote:
> > The various hooks take directory paths as arguments, and typically
> > return a filename (e.g., build_wheel). The returned filename is always
> > explicitly noted as being *a unicode
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
On Mon, Aug 20, 2018, at 2:52 PM, Paul Moore wrote:
> The various hooks take directory paths as arguments, and typically
> return a filename (e.g., build_wheel). The returned filename is always
> explicitly noted as being *a unicode string*. However, argumnents
> (metadata_directory in
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
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
I'm in the process of implementing PEP 517 for pip, and I've hit a
question. I'm pretty sure I know the answer, but I want to be clear,
as whatever the answer is will require some fixing up.
The various hooks take directory paths as arguments, and typically
return a filename (e.g., build_wheel).
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...
>
> >
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
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
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
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
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
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
Hi,
Can someone explain to me the relationship between pipenv and pip,
from the perspective of pipenv's maintainers?
For example, does pipenv currently reimplement anything that pip tries
to do, or does it simply call out to pip through the CLI or through
its internal API's? Does it have any
15 matches
Mail list logo
