[TIP] Coming changes to unittest2 plugins
holger at merlinux.eu
Mon Sep 27 12:08:43 PDT 2010
On Mon, Sep 27, 2010 at 18:50 -0000, exarkun at twistedmatrix.com wrote:
> On 06:36 pm, holger at merlinux.eu wrote:
>> On Mon, Sep 27, 2010 at 17:51 -0000, exarkun at twistedmatrix.com wrote:
>>> On 05:09 pm, holger at merlinux.eu wrote:
>>>> On Mon, Sep 27, 2010 at 16:17 -0000, exarkun at twistedmatrix.com wrote:
>>>>> But this difference doesn't matter. If someone wants to specify a
>>>>> method of an inner class to be used as a plugin - great! As far
>>>>> as I
>>>>> can tell, unittest2 doesn't care. The : doesn't add anything.
>>>> In context of generic distutils2 entry point-like specification we
>>>> are not only talking about plugins but also command line main()
>>>> functions etc.
>>> Where, again, the difference does not matter.
>> It does if you want more or something else than loading a live object.
> Yes? And do main points or unittest or distutils plugins want more than
packaging meta data is for consumption of tools. For example, i want to
write one that converts a newstyle setup.cfg into an oldstyle setup.py.
> And even if you do, then once you have the live object, you can
> do whatever else you want with it.
no doubt. And what if i can't get at a live object because i am
on the wrong platform or am missing a dependency?
More information about the testing-in-python