RetroSearch Browse

Wed Mar 6 07:45:58 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-March/124623.html

On Tue, Mar 5, 2013 at 9:25 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Tue, Mar 5, 2013 at 5:02 PM, Lennart Regebro <regebro at gmail.com> wrote:
>> I don't care much what that mechanism is, but I think the easiest way
>> to get there is to tell people to extend distutils with a test command
>> (or use Distribute) and perhaps add such a command in 3.4 that will do
>> the unittest discover thingy. I remember looking into zope.testrunner
>> hooking into that mechanism as well, but I don't remember what the
>> outcome was.
>
> There is no easy way forward at this point in time. There just isn't.
> If people want to dispute that claim, please feel free to solve all
> the other problems distutils-sig is trying to tackle, so we can pay
> attention to this one.

I have to admit that of all the packaging problems out there, this is
one of the easiest ones. ;-)
That said, it's not easy.

> We'll get to this eventually - there are just several other more
> important things ahead of it in the queue for packaging and
> distribution infrastructure enhancements (and python-dev is not the
> group that will solve them).

To be honest I'm not sure distutils-sig is the right place for this.
It's really only a packaging problem because Setuptools has a "test"
command. :-)
Perhaps we can solve this outside distutils-sig so that distutils-sig
can concentrate on the harder problems?

//Lennart

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-March/124623.html below:

[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)