[TIP] Coming changes to unittest2 plugins
holger at merlinux.eu
Mon Sep 27 10:31:37 PDT 2010
On Mon, Sep 27, 2010 at 18:09 +0100, Michael Foord wrote:
> On 27/09/2010 18:05, holger krekel wrote:
>> "dotted object addresses" look simple but they are really hiding
>> complexity (also due to Python's complicated import system).
>> This is also indicated by the fact that distutils2.util.resolve_name
>> has 20 lines of code (and easily gives meaningless errors, btw) whereas
>> the "a.b:C" notation requires a brain-dead simple 2-liner to resolve.
> But we should optimize for the user and not for the framework - right?
> As the users here are Python developers, using the Python syntax for
> specifying objects seems 'nicer'.
My point is that the apparent "niceity" involves some evil magic (*) and
can easily give strange error conditions to a developer. Note that i am
not only talking about unittest2 plugins here lbut a more general
distutils2 context, anyway.
(*) where "evil magic" is measured in calls / dealings with
the python import system :)
More information about the testing-in-python