Hi Ralf,
On Sun, Dec 27, 2009 at 23:41 +0100, [email protected] wrote:
> holger krekel <[email protected]> writes:
>
> > Hi Ralf,
> >
> > very cool! Just needs some fixing for Python3.
> > I just gave your write access on bitbucket py-trunk - would you care
> > to add bin-for-dist/generate_standalone_pytest.py?
>
> just added it.
great, thanks. MIT-licensing is fine for you, btw?
> > (if in doubt i can do the python3 fixing)
>
> please do so. I can certainly get it working with python 3, but I'm not
> quite sure what's best practice. One thing that needs to be fixed is the
> relative "import defaultconftest" that I introduced. I just do not know
> how to workaround the py.apipkg magic.
It's not about apipkg, it's about importing the defaultconftest.py starting
from its file location which, it being part of a zip-file, does not work.
This loading-by-filename is done for uniformity with loading other
conftest.py files. However, i guess here we can instead just always import
py.impl.test.defaultconftest by python import path.
> > And do you think it makes sense to honour "py.XYZ" symlinks pointing
> > to 'py.test' which would make the other tools available without
> > duplication?
>
> in case anyone uses those (or even the standalone py.test): yes.
not sure either how many people use py.cleanup/py.lookup etc.
I am sure, though, that people are interested in the standalone py.test
version, i have been asked for it a number of times. Actually I guess
some maintainers would appreciate a
py.test --genscript=mytest [options] [paths]
which generate a custom "mytest" standalone script to be
shipped with a package or offered for download for users
to run tests in their environment.
cheers,
holger
_______________________________________________
py-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/py-dev
