On Mar 22, 2014, at 8:55 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
> Moving the affected modules out of the standard library proper and > bundling the critical ones along with pip instead is indeed another > alternative. However, that approach introduces additional issues of > its own - I'll cover some of them in the next PEP update, but it would > be good to have someone explicitly trying to make the case that a PyPI > backport would be simpler for the overall ecosystem than my suggested > approach. FWIW pip as of right now has a policy of no C dependencies outside of the stdlib. CPython isn’t our only target and C dependencies don’t work very well on PyPy (if at all) and it makes the situation much more difficult on platforms where there are no compiler toolchains (Windows). ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
