Maciej Fijalkowski writes: > On Thu, Mar 27, 2014 at 10:11 AM, Stephen J. Turnbull > <step...@xemacs.org> wrote:
> > Maybe. That depends on if you care about the convenience of folks who > > have to get new modules past Corporate Security, but it's easier to > > get an upgrade of the whole shebang. I don't think it's ever really > > been resolved whether they're a "typical case that won't go away" or a > > special group whose special needs should be considered. > > > > Steve > > And random pieces of C included in the standard library can be > shuffled under the carpet under the disguise of upgrade or what are > you suggesting? CPython doesn't do stuff like that; C code in CPython gets careful review, and can hardly be called "random". PyPI packages do do stuff like that. Not all of them by far, but to tell the difference you need to review line-by-line. So I'm simply saying (as Nick did) that it is often easier to get changes past a corporate bureaucracy if they are certified by inclusion in CPython (not to exclude PyPy or Jython, but the corporate consideration is about a specific distribution), than if it's a random package on PyPI. _______________________________________________ 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
