Showing content from http://mail.python.org/pipermail/python-dev/attachments/20160506/fafa560e/attachment.html below:
<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, 5 May 2016 at 16:54 David Wilson <<a href="mailto:dw%2Bpython-dev@hmmz.org">dw+python-dev@hmmz.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is mostly just observational, and not meant primarily as criticism<br>
of the fabulous work of Donald and others (ignoring pypa, also the<br>
prompt, reliable, and skilled support responses common on such places as<br>
IRC), however I can't help but notice that PyPI governance seems to come<br>
under fire vastly more often than similar and much more popular<br>
packaging systems, and some choices that have been made particularly in<br>
recent years have caused a noticeable amount of dissent with what might<br>
be considered the typical developer.<br>
<br>
When a contributor to the core language is having repeat issues<br>
maintaining some basic element of the function of the packaging system,<br>
might it be fair to reflect on how changes to those functions are being<br>
managed?<br>
<br>
There are PEPs covering a great deal of the work done to PyPI recently,<br>
but, and I say this as someone who has bumped into friction with the<br>
packaging tooling in the relatively recent past, even I despite my<br>
motivations to the contrary, I have not read most of them. It seems the<br>
current process is observed by few, does not sufficiently address the<br>
range of traditional use cases that were possible in the past, and the<br>
first the common user learns of a change is when pip (after insisting it<br>
must be upgraded) fails to function as it previously did.<br>
<br>
The usual course then is some complaint, that leads to distutils-sig,<br>
which ultimately leads to pointing at some design work that was only<br>
observed by perhaps 50 people max that turns out had some edge cases<br>
that hurt in a common use case.<br>
<br>
Is there something to contemplate in here? I dislike posting questions<br>
instead of answers, but it seems apparent there is a problem here and it<br>
continues to remain unaddressed.<br></blockquote><div><br></div><div>This is whole thread is off-topic precisely because all of this is discussed -- in the open -- on distutils-sig and decided there. If people feel changes need to be made like broadcasting to a wider audience when a change occurs, then please bring it up on distutils-sig. But if people choose not to participate then they are implicitly delegating decision powers to those who do participate (which is totally fine and I'm not implying that  if people don't participate they are doing something wrong).</div></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4