[TIP] pytest news: plugins, pycon, release-separation
Kumar McMillan
kumar.mcmillan at gmail.com
Sun Feb 22 19:35:06 PST 2009
On Sat, Feb 21, 2009 at 5:09 AM, holger krekel <holger at merlinux.eu> wrote:
> Hi folks,
>
> some good news. as those glimpsing at pytest svn-commits know
> i am heavily working on a new plugin architecture. I am
> really happy about it as those also following me on my
> brand-new twitter account (hpk42) might guess.
Hi Holger.
This is great news! At the last PyCon Jason, Titus, Brian and I were
talking about how it would be cool if nose and py.test could share the
same plugin interface -- that way, in theory, all current nose plugins
(http://nose-plugins.jottit.com/) would work in py.test and visa
versa.
I took a look a quick look at your code but I couldn't find the core
plugin code. Do you plan to make a nose-compatible interface? The
nose interface is documented here:
http://www.somethingaboutorange.com/mrl/projects/nose/doc/plugin_interface.html
>
> * new plugins for managing setup/teardown of application state,
> using a turns-out-to-work-great new mechanism
> which i guess nosetests might imitate at some point :)
well, it has piqued my interest :) There are a lot of problems with
unittest setup / teardown, especially when running tests in parallel.
Where do I look to see the new mechanism?
-Kumar
>
> Regarding the next release i consider doing the following:
>
> * open two google-code projects "pytest" and "pylib"
> with their svn repos remaining at codespeak (where
> many projects share one respository - i prefer that)
>
> * move current py/test/ to its own "pytest/" root project
> and depend on the py lib for install.
>
> * aim to do two alpha releases,
> pytest-1.0 alpha and py lib 1.0 alpha (containing the rest)
>
> What do you think? I am unfamiliar with commoditized
> code hosting and consider using google code. I'd probably
> like to also have an issue tracker for pytest. Any
> comments/recommendations? Would someone be up
> for co-admining such a project?
>
> Meanwhile i am finishing up the pytestplugins branch
> for merge to trunk, stay tuned :)
>
> cheers & have fun,
> hope to meet some of you at Pycon,
> holger
>
> --
> collaborative expert contracting: http://merlinux.eu
> PyPy Python/Compiler tool chain: http://codespeak.net/pypy
> pylib py.test/greenlets/svn APIs: http://pylib.org
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>
More information about the testing-in-python
mailing list