[issue28846] Add a ProviderKey to the installer bundle

Steve Dower added the comment: This bloated into a couple of extra build/installer fixes, including *finally* fixing the sys._mercurial bug (I hope). I can also now merge fairly cleanly between 3.5 and 3.6 again, so I'm happy for a while :) -- resolution: -> fixed stage: needs patch -

[issue28846] Add a ProviderKey to the installer bundle

Roundup Robot added the comment: New changeset 68530c0a1487 by Steve Dower in branch '3.5': Issue #28846: Various installer fixes https://hg.python.org/cpython/rev/68530c0a1487 New changeset 5171bd86a36f by Steve Dower in branch '3.6': Issue #28846: Various installer fixes https://hg.python.org/

[issue28846] Add a ProviderKey to the installer bundle

Ned Deily added the comment: Sounds good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28846] Add a ProviderKey to the installer bundle

New submission from Steve Dower: Currently the installer bundles for 3.5 and later have an automatically generated dependency provider key. This makes it difficult for other installers to correctly depend on the bundle. For example, Visual Studio 2017 has an option to install CPython 3.5, but