<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5Crob%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5Crob%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5Crob%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:1;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:variable;
mso-font-signature:0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;}
a:link, span.MsoHyperlink
{mso-style-noshow:yes;
mso-style-priority:99;
color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-noshow:yes;
mso-style-priority:99;
color:purple;
mso-themecolor:followedhyperlink;
text-decoration:underline;
text-underline:single;}
p
{mso-style-noshow:yes;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;}
span.EmailStyle17
{mso-style-type:personal;
mso-style-noshow:yes;
mso-style-unhide:no;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:11.0pt;
font-family:"Courier New";
mso-ascii-font-family:"Courier New";
mso-hansi-font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-size:10.0pt;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: "Courier New";">I'm at a decision point of investing in plugin development for either nose or unittest2 (under Python 2.6). What's the current status of unittest2 plugin extensibility? Is it ready (even if in beta) or should I stick with nose?</span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: "Courier New";"><br></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: "Courier New";">Thanks.</span></p><p class="MsoNormal">
<span style="font-size: 10pt; font-family: "Courier New";">- Rob<br></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: "Courier New";"><br></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size: 10pt; font-family: "Courier New";"> </span></a></p>
<span style=""></span>
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: "Tahoma","sans-serif";">From:</span></b><span style="font-size: 10pt; font-family: "Tahoma","sans-serif";"> <a href="mailto:testing-in-python-bounces@lists.idyll.org">testing-in-python-bounces@lists.idyll.org</a>
[mailto:<a href="mailto:testing-in-python-bounces@lists.idyll.org">testing-in-python-bounces@lists.idyll.org</a>] <b>On Behalf Of </b>Michael
Foord<br>
<b>Sent:</b> Thursday, March 04, 2010 5:30 PM<br>
<b>To:</b> Kumar McMillan<br>
<b>Cc:</b> TIP<br>
<b>Subject:</b> Re: [TIP] unittest2 and the future of nose</span></p>
<p class="MsoNormal"> </p>
<p><span style="font-size: 10pt;">On 04/03/2010 21:14, Kumar McMillan wrote:<br>
> On Thu, Mar 4, 2010 at 2:51 PM, jason
pellerin<<a href="mailto:jpellerin@gmail.com">jpellerin@gmail.com</a>> wrote:<br>
><br>
>> Fact: unittest2 is coming:<br>
>> <a href="http://www.voidspace.org.uk/python/articles/unittest2.shtml">http://www.voidspace.org.uk/python/articles/unittest2.shtml</a><br>
>><br>
>> ... indeed, it's already here (just not yet in stdlib). It does test<br>
>> discovery (though not by default), can support test functions (though<br>
>> not by default), will eventually support a better form of<br>
>> parameterized tests than nose does, and also will eventually support<br>
>> at least class and module-level fixtures.<br>
>><br>
> ...<br>
><br>
>> Which means it's not going to happen unless enough of you folks are<br>
>> interested and have time to commit.<br>
>><br>
>> What do you think?<br>
>><br>
><br>
> My gut reaction to all this is that unittest2 probably replaces most<br>
> of Nose's functionality besides plugin support. I say gut reaction<br>
> because I would need to think about it harder and dig into unittest2<br>
> deeper to be sure.<br>
><br>
<br>
Right - unittest extensibility is the *really* big wart on unittest that<br>
I would like to address. That means some kind of plugin / extensibility<br>
mechanism that doesn't suck. It needs a lot of thinking about and quite<br>
a bit (but not too much) talking about.<br>
<br>
> That said, one HUGE win for unittest2 would be if it could support<br>
> Nose's plugin API.<br>
<br>
I doubt unittest(2) will support *specifically* the Nose plugin API. We<br>
need to work out the best, and idiomatic, way of extending unittest.<br>
That does mean making sure that the major use cases of nose plugins are<br>
possible.<br>
<br>
[snip...]<br>
> The only part of Nose that is not implemented as a plugin that is not<br>
> scheduled to be supported by unittest2 (yet) is config file support (I<br>
> think?). You can turn on any command line option in a config file<br>
> which is really crucial for projects that depend on a lot of plugins:<br>
> <a href="http://somethingaboutorange.com/mrl/projects/nose/0.11.1/usage.html">http://somethingaboutorange.com/mrl/projects/nose/0.11.1/usage.html</a><br>
><br>
><br>
<br>
Yup. As soon as you want to support both test discovery (or even the<br>
running of individual test modules) plus an extensibility system (where<br>
individual modules are able to *depend* on particular extensions being<br>
used) then you also need to have *some* way of specifying what<br>
extensions are needed. Still an open issue, I don't know what the answer<br>
is, but I am aware it is an issue.<br>
<br>
Michael<br>
<br>
<br>
> Kumar<br>
><br>
> _______________________________________________<br>
> testing-in-python mailing list<br>
> <a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
> <a href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a><br>
><br>
<br>
<br>
--<br>
<a href="http://www.ironpythoninaction.com/">http://www.ironpythoninaction.com/</a><br>
<a href="http://www.voidspace.org.uk/blog">http://www.voidspace.org.uk/blog</a><br>
<br>
READ CAREFULLY. By accepting and reading this email you agree, on behalf of
your employer, to release me from all obligations and waivers arising from any
and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap,
clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and
acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in perpetuity, without
prejudice to my ongoing rights and privileges. You further represent that you
have the authority to release me from any BOGUS AGREEMENTS on behalf of your
employer.<br>
<br>
<br>
<br>
_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a></span></p>