I'm not sure I agree that setting up a private repository is that hard. Devpi does an excellent job for open source stuff, or otherwise if you use Artifactory inside your company that also has similar plugin.
On Tue, Jan 29, 2019 at 1:30 PM Jan Musílek <jan.musi...@nic.cz> wrote: > Nick Coghlan wrote: > > So URL specifiers replaced the part of dependency links that we > > actually wanted to keep: letting projects *temporarily* depend on VCS > > repos and other URLs while waiting for a release containing the > > feature that they needed, while focusing on abstract dependencies > > outside those cases (and deliberately eliminating the ability to add > > arbitrary new repositories to the dependency resolution process). > > Thank you for the explanation! This makes a lot of sense for public > packages. > > However, when you work with private packages, it's not as straightforward. > You can setup your own warehouse, but that's a lot of overhead for small > personal projects. What would you recommend to use in this case? > > Cheers, > Jan > -- > Distutils-SIG mailing list -- distutils-sig@python.org > To unsubscribe send an email to distutils-sig-le...@python.org > https://mail.python.org/mailman3/lists/distutils-sig.python.org/ > Message archived at > https://mail.python.org/archives/list/distutils-sig@python.org/message/PRLJLJVQ3AOAYU4I3HZ6SWB6HKNCQF3P/ >
-- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/JJFCEXT7GO5XU2GMIJISMMQJEGIM4JCF/
