At 04:49 AM 12/18/2010 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
2010-12-18 00:16:52 P.J. Eby napisaÅ(a):
> At 05:26 PM 12/17/2010 -0500, Barry Warsaw wrote:
> >Something bugs me about virtualenv, distribute, development, and
testing. I
> >figure I'm probably doing something wrong and that y'all will be
able to set
> >me straight.
> >
> >I'm working on a new tool called pkgme[1]. It uses distribute
and recommends
> >using virtualenv for development. After activating the
virtualenv you can do
> >'python setup.py develop' and do convenient in-place editing so that your
> >changes to the source show up immediately in the running
environment. So far
> >so good.
> >
> >However, when I want to run the test suite, it does the equivalent of a
> >'python setup.py build' and then runs the tests out of the
> >build/lib.{platform}-{version} directory.
>
> Really? That sounds wrong. "python setup.py test" should run the
> tests against the *source* tree, with in-place extension builds.
Modules are sometimes transformed by 2to3 during building
(transformed versions
are placed in build/lib*). Running tests (with Python 3) against the
source tree
would cause syntax errors etc.
Ah, so this issue is specific to distribute, then, not setuptools.
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
