Closed thp closed 11 years ago
Thanks!
I've merged b6ea220ed849df8fbbc631d288f381e897638bf5 unmodified, but I did make some changes to 46f13f5a064cd1ec75eb2a0c03b1504e7d021a41. The resulting commit is 12d42b6e5b531648f16e6e69cd12f51cabc7d56c.
requirements-test.txt
as its not just "travis-related" but quite common when using virtualenvsREADME.md
(for syntax-highlighting on Github), but with your contents (ie w/o build status)
Add more tests from
gpodder-core
, remove Travis-CI related trash (the requirements list is small enough to put into.travis.yml
direcly, and putting the CI status indicators - while probably very hip these days - into the README file is not really useful, especially if we're going to use theREADME
file as long description in thesetup.py
.As we use
nose
for running our tests, we don't have to use the Java-style vintageunittest
module and requestdoctest
s manually, but actually all of that can be done using nose and--with-doctest
.If you want to have the Travis CI icons/status indicators somewhere, put it on a wiki page, e.g. on wiki.gpodder.org, or we can also add a special podcastparser page to the gpodder.org webpage. Or on readthedocs?