<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I appreciate all the energy going into what I thought was the least
interesting part of the changes!<br>
<br>
I went into the cheeseshop to see how the .py suffix correlated to
project structure, and found that the last release of coverage is there
announced as "Coverage 2.85", so I guess I'll just go with "Coverage
3.0" and be done with it.<br>
<br>
Did anyone try any of the new stuff? :)<br>
<br>
--Ned.<br>
<br>
Ben Finney wrote:
<blockquote cite="mid:87k552pq4g.fsf@benfinney.id.au" type="cite">
<pre wrap="">Lukas Linhart <a class="moz-txt-link-rfc2396E" href="mailto:bugs@almad.net"><bugs@almad.net></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">On Thursday 30 April 2009 05:42:32 Robert Collins wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">not actually a Python source file but a distribution name, are to
be avoided. Can't this just be named “Coverage”?
</pre>
</blockquote>
<pre wrap="">or perhaps 'python-coverage' which is clear, specific, and happens
to fit the package naming convention for many linux distributions
:).
</pre>
</blockquote>
<pre wrap="">IMHO, python- is redundand for python package name. This prefix should
be part of packager's job (and it's also different in various
distributions, what would be python-coverage in debian or
devel/python-coverage in arch will be dev-python/coverage in gentoo).
</pre>
</blockquote>
<pre wrap=""><!---->
As a co-maintainer of the ‘python-coverage’ package in Debian, I agree
with this — naming it correctly in the context of Debian is part of my
job :-) It's quite normal and unproblematic for a library to be packaged
by a name different from (usually more specific than) its canonical
name.
The name by which the project refers to itself, though, is important to
get right. I think that the name “coverage” (or “Coverage”) makes
the most sense. Certainly the *package* name, as imported in Python,
should be just ‘coverage’; and the project name should match that to
prevent programmers going mad.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ned Batchelder, <a class="moz-txt-link-freetext" href="http://nedbatchelder.com">http://nedbatchelder.com</a>
</pre>
</body>
</html>