On Thu, May 30, 2013 at 10:41 +0200, Ronald Oussoren wrote: > On 29 May, 2013, at 20:36, holger krekel <hol...@merlinux.eu> wrote: > > > Hi Nick, > > > > On Mon, May 27, 2013 at 21:36 +1000, Nick Coghlan wrote: > >> After preliminary reviews by Donald and Daniel, I have now pushed the > >> first complete draft of the JSON-based metadata 2.0 proposal to > >> python.org > >> > >> PEP 426 (metadata 2.0): http://www.python.org/dev/peps/pep-0426/ > > > > After a first quick read i am wondering if i missed something > > with respect to test tools. There are some fields which specify > > dependencies required for running tests, but there is nothing that > > would tell which test runner to use, which test command to invoke, > > or am i missing something? > > > > Basically i am wondering how PEP426 could be useful/used by tox. > > best, > > There is something about testing in the metabuild hooks section, although > that appears to be targetted towards running tests for an installed > distribution. > > I'm not sure yet how useful that hook would be for my packages, as the test > suite isn't actually installed (it is in the sdist, but not in the output of > bdist_*).
That's indeed another issue. In order to run tests you sometimes need to install a test package for it. I'd like to add this to tox but have refrained so far because of the involved packaging activities. Ideally, building+package+upload should be able to create both the actual package and the test package in case someone wants to run the tests. That wouldn't easily work for models where tests are put into subdirectories unless maybe the new python3 namespaces are used. best, holger > Ronald > _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
