aboutsummaryrefslogtreecommitdiffstats
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* Remove Py32 tests from travis, not tox.Waylan Limberg2016-01-281-1/+0
| | | | That way py32 tests can still be run locally. Just not on the CI server.
* Switch Travis to new infrastructure for faster build.Waylan Limberg2015-11-171-4/+6
|
* Restict travis to non-experimental branches.Waylan Limberg2015-06-191-0/+4
|
* Add Docs spellchecking Test.Waylan Limberg2015-02-071-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Not sure this is the best way to go, but it works. I'm not crazy about running the spellcheck against the built docs, but aspell has a builtin option to easily ignore everything in `<code>` tags which greatly simplfies things. I looked at Doug Hellmans' sphinxcontrib-spelling package which does something similar for Sphinx. However, as Sphinx uses rST and the rST parser outputs a parse tree, Doug is essentially taking that parse tree and running the spellcheck on the appropriate parts (skipping code, etc.). He did a nice [writeup][5] of his development process if you are interested. As Python-Markdown's parse tree is represented as HTML (through ElementTree) I would have to use HTML anyway. And [PyEnchant][2] doesn't currently have good support for HTML. So I used [aspell][3], with inspiration from the [git-spell-check][4] hook. [1]: http://sphinxcontrib-spelling.readthedocs.org/en/latest/index.html [2]: https://pythonhosted.org/pyenchant/ [3]: http://aspell.net/ [4]: https://github.com/mprpic/git-spell-check [5]: http://doughellmann.com/2011/05/26/creating-a-spelling-checker-for-restructuredtext-documents.html
* Add offical support for PyPy.Waylan Limberg2015-01-101-0/+1
|
* Added flake8 to tox and travisWaylan Limberg2014-11-201-0/+1
|
* Refactored extension importing.Waylan Limberg2014-08-271-1/+0
| | | | | | | | | | | | | We now use importlib which means we no longer support Python 2.6. Also, this refactor properly imports third party extensions which reside at the root of PYTHONPATH. Previously, either `markdown.extensions.` or `mdx_` would be appended to any extension name that did not contain a dot, which required third party extensions to either be in submodules or use the old `mdx_` naming convention. This commit is also in preperation for #336. It will now be much easier to deprecate (and later remove) support for the old ways of handling extension names.
* Merge branch 'master' of github.com:waylan/Python-MarkdownWaylan Limberg2014-07-101-0/+1
|\
| * Add 3.4 to list of Python versions to test withDmitry Shachnev2014-06-111-0/+1
| |
* | Add Coverage (and Coveralls) support to tests.Waylan Limberg2014-07-101-0/+3
|/ | | | Looks like we need to write some more tests. Only 76% covered.
* Update .travis.ymlWaylan Limberg2014-03-241-0/+3
| | | Add install of libtidy dependancy. Forgot about that.
* Add .travis.yml fileWaylan Limberg2014-03-241-0/+10
Just uses the existing tox config as described in <http://borntyping.com/posts/tox-and-travis-ci.html>. This fixes #299. I took this route rather than @mitya57's suggestion because we get better test coverage with tox's config (more dependencies are installed) and I can't see mirroring that here when we can just reuse it.