3 ms·

One reason for this proposal is to save manpower. Separating concerns doesn't help with that.

• kgwgk 7y ago
  It does save manpower for Python maintainers if reviewing non-core libraries becomes someone else’s problem.
  • anoncake 7y ago
    Either the reviewer is trusted and might as well review the libraries as part of the standard library or they are not trusted and reviews by them are useless.
• afiori 7y ago
  But keeping them together does not need a standard library, each python distribution could have a set of blessed packages, those packages could be "unblessed" without breaking applications using them
• lmm 7y ago
  If the two tasks require different skillsets (and they do) then separating them could easily mean more people are able and willing to help with one or the other.