This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.moore
Recipients cgohlke, eryksun, larry, paul.moore, skrah, steve.dower, tim.golden, zach.ware
Date 2015-09-09.08:31:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Maybe we can special-case pip uninstalling it from the site-packages folder? *Paul* - any thoughts?

Sorry, I've been following this thread but it's been moving pretty fast, so I'm probably replying too late to be helpful now :-(

One alternative thought I had was to bundle vcruntime140.dll in a separate wheel, which other wheels can depend on. Then we get pip's usual dependency resolution to handle ensuring that the runtime is present.

It's possible to special-case vcruntime, what I'd do is modify distutils to omit vcruntime140.dll from the RECORD file - then nothing (pip, distlib, other install tools) views the vcruntime file as being "owned" by a particular package. I'm not overly keen on that solution, though, as it's clearly a hack and would be a maintainability issue going forward. But it does keep the code changes isolated to the core, rather than needing pip/setuptools changes.
Date User Action Args
2015-09-09 08:31:26paul.mooresetrecipients: + paul.moore, larry, tim.golden, cgohlke, skrah, zach.ware, eryksun, steve.dower
2015-09-09 08:31:25paul.mooresetmessageid: <>
2015-09-09 08:31:25paul.moorelinkissue25027 messages
2015-09-09 08:31:21paul.moorecreate