<br><br><div class="gmail_quote">2010/1/7 P.J. Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">At 09:20 PM 1/7/2010 +0100, Martin v. Löwis wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> 8614 *projects*, some of which have one or more *versions*, which in<br>
> turn may have one or more source or binary *distributions*.<br>
<br>
Instead of "version", I really like PyPI's term more: *releases*.<br>
</blockquote>
<br></div>
Not all versions are released versions, so I suppose it's actually:<br>
<br>
project -> version -> release -> distribution<div class="im"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As for projects: fine with me; PyPI would then be the Python Project<br>
Index.<br>
</blockquote>
<br></div>
+1.<div><div></div><div class="h5"><br></div></div></blockquote><div><br>+1 from me as well. It does remove ambiguity.<br><br>Michael<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="h5">
<br>
_______________________________________________<br>
Catalog-SIG mailing list<br>
<a href="mailto:Catalog-SIG@python.org" target="_blank">Catalog-SIG@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/catalog-sig" target="_blank">http://mail.python.org/mailman/listinfo/catalog-sig</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.ironpythoninaction.com/">http://www.ironpythoninaction.com/</a><br><br><br>