On Tue, 29 Jan 2019 at 23:29, 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?
I mostly just use "-f /some/filesystem/path" to add a directory containing built packages to the normal dependency resolution process. (It does mean the install process has to be explicit about where the extra packages are going to be allowed to come from, but that's kinda the point of the change) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia -- 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/KIVWJCVEL4F3EVQOC3YJDIPJM6XZM5GE/
