On Tue, Jul 31, 2018 at 7:44 AM Nathaniel Smith <
njs@pobox.com> wrote:
On Mon, Jul 30, 2018 at 3:13 PM, Paul Moore <p.f.moore@gmail.com> wrote:
> On 30 July 2018 at 23:01, David Cournapeau <cournape@gmail.com> wrote:
>> Hi,
>>
>> I see that there is almost no mention of private packages index in the
>> packaging guide, and no recommendation on what to use.
>>
>> Currently googling for private packages mostly return obsolete (and not very
>> practical) recommendations based on dependency links.
>>
>> In 2018, what would be the recommended practices for teams that develop
>> private packages that depend on each other ?
>
> That's a very good point, and I think it would be a really useful
> addition to the packaging guide. I believe the most commonly
> recommended approach is to use a local,devpi instance as a private
> index, but in terms of development workflow around that basis, I don't
> really know that there's much in the way of a consensus. (I should say
> that I don't work in an environment like this myself, so my comments
> are based purely on what I've heard, not on personal experience).
A tricky aspect here is that this niche has been colonized by
commercial projects like Artifactory, Gemfury, etc., and I'm not sure
we want to get into recommending one commercial product versus another
(or that we even have any effective way to compare them).
Right, I would not expect us to do anything besides maybe mentioning proprietary solutions.
But for OSS solutions, there are multiple options, and it is not clear which ones are appropriate for which usage. E.g. do you need multi index support, do you need upload support, etc. ?
Would it make sense to start such a document as a PR ?
David
-n
--
Nathaniel J. Smith -- https://vorpus.org