<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 15, 2016 at 1:51 AM, Steve Dower <span dir="ltr"><<a href="mailto:steve.dower@python.org" target="_blank">steve.dower@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1py" class="a3s aXjCH m155eb9d494e80358">This is why I listed a set of restrictions to help prevent that:<br>
<br>
* 140 chars (flexible, but short enough to prevent rants)</div></blockquote></div><br><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Did you mean to write "provoke" instead of "prevent"? If we can learn one thing from Twitter it's that such limit favors short and brutish comments over the more nuanced and thoughtful ones - that take way more character space of course.<br><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">I don't get what all this fuss is about about comments on PyPI. Such feature seems unnecessary. There are plenty of ways to assess how well maintained a package is. If a package maintainer wants comments or feedback there's the url/long_description fields.<br></div><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div><span style="font-family:trebuchet ms,sans-serif"><span style="color:rgb(51,51,51)"><br><font size="2"><span style="color:rgb(51,51,51)">Thanks,</span><br><span style="color:rgb(153,153,153)">-- Ionel</span></font></span><font size="2"><font style="color:rgb(153,153,153)"> Cristian Mărieș, <a href="http://blog.ionelmc.ro" target="_blank">http://blog.ionelmc.ro</a><br></font></font></span></div></div></div></div></div></div></div>
</div></div>