<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
(sorry, first message was mis-sent.)<br>
<br>
holger krekel wrote:
<blockquote cite="mid:20091125091522.GA29390@trillke.net" type="cite">
<pre wrap="">Hi Ned, Ross, David,
On Tue, Nov 24, 2009 at 07:45 -0500, Ned Batchelder wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So I want to make sure that these plug-ins play well with those (future)
improvements to coverage. I know this is a bit much to ask at this
point.
</pre>
</blockquote>
<pre wrap=""><!---->
A config file would help to eliminate tons of command line options from the
plugins and ease coverage moving on consistently.
</pre>
<pre wrap="">Question: do you want to generally package the nose/py.test plugin
code with the coverage package?
Currently nose comes with a builtin coverage plugin (where David
just recently posted an update) and i guess this would need
to change?!
</pre>
</blockquote>
This is the interesting inter-package question. Originally, I thought
that shipping the plugin with coverage made the most sense, since it
was adding new features and switches faster than the nose plugin API
was changing. But once we get to configuring coverage through a
side-channel (the config file), the plug-in command-line interface
immediately becomes stable: "--with-coverage" takes care of it.<br>
<br>
Having nose ship the plug-in solves the question of what to do with the
old nose plug-in, but doesn't help with the gap between finishing the
plug-in and the next release of nose. Likely what will happen is the
plug-in will become part of the coverage.py kit, *and* it will be added
into the next version of nose. In the gap, there will be a few emails
along the lines of "install nose first, then install coverage.py, and
everything will work fine."<br>
<blockquote cite="mid:20091125091522.GA29390@trillke.net" type="cite">
<pre wrap="">cheers,
holger
</pre>
</blockquote>
Opinions?<br>
<br>
--Ned.<br>
</body>
</html>