My company was recently in this situation, and it was definitely hard to
get information on non-self-hosted solutions for private packages. We
settled on packagecloud.io, but there are some definite pain points that I
think PyPA could productively document:
- Many tools do not support indices
Another +1 to the utility of a maintainer. I am also working on package
management and have found that venv is not a full replacement for
virtualenv--for example I don't believe the environment can be entered
programatically, while virtualenv provides activate_this.py which can be
exec'd. I'm sure
ut has some gaps in support I know about
(including packages that use setup_requires or pyproject.toml), and
probably many I do not. Thanks to everyone on this list who I discussed
dotlock and general package issues with at PyCon, and to anyone who tries
it out!
Sincerely,
Alex Becker
--
Distuti
en try to install into
a different virtualenv? Or do I have to re-architect my code to call pip in
the target virtualenv (which may require me forcing pip to be installed,
depending on what versions of python I choose to support)?
Sincerely,
Alex Becker
--
Distutils-SIG mailing list -- distuti
; your argument list to the path to the pip inside the virtualenv you're
> targeting.
>
> --Chris
>
> On Fri, Sep 14, 2018 at 12:15 AM, Alex Becker
> wrote:
> > As part of a package management tool, I'm trying to use pip to install
> > python packages into a virtual
may be more useful.
Most likely (someone more familiar with Warehouse could answer this)
Warehouse will select sha256 whenever it is available, so the simple API
may be just as good for you. But it's something to consider.
Best,
Alex Becker
On Tue, Feb 12, 2019 at 9:58 AM Paul Moore wrote
You can use a local PyPI mirror, e.g. devpi, and point your docker builds
at that, basically tricking docker by going through the (local) network
stack instead of the filesystem.
On Tue, May 7, 2019 at 8:12 AM Wes Turner wrote:
> What is the best way to build docker images without constantly
>
