Am Fri, May 29, 2026 at 07:55:13AM +0200 schrieb Sergio Pastor Pérez: > Just as a clarification before the example, if Python would start to > depend on some library which is fully vibe-coded, we will still consider > it as a core software that needs to be packaged. I propose to use all > package dependencies as a metric, not only direct.
This is not my argument. My argument, in reply to Maxim that we can always take out a package later, is that we need to be careful *now* and avoid LLM contributions as much as possible. Taking out a package is much more difficult than not adding it or not updating it. My stance would rather be: If Python becomes crazily vibe coded, we do not update it for the time being. How sustainable this will be in the long term remains to be seen. Maybe there will be a fork from the last non-LLM version. Maybe we can remove it. Maybe we eventually will have to bite the bullet and update it nevertheless (which would then require another GCD to make the exception). So my suggestion is rather the opposite of yours: Be rather strict on not allowing vibe coded software. Andreas
