| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Note that we install coverage<4.0 in travis because test-requirements.txt is
installing the same in the tox environments. The .coverage file format
changed in 4.0.
|
|
|
|
|
|
|
|
| |
Travis-CI no longer has all supported Python versions installed by default.
Each version needs to be set via the `python` setting. However, we don't
want a matrix where every Python version runs with every `TOXENV`.
Therefore, we now manually define the matrix so that the Python version
is properly matched with the TOXENV.
|
|
|
| |
Travis should checkout aspell-en (issue #521)
|
|
|
|
| |
That way py32 tests can still be run locally. Just not on the CI server.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| | |
|
|/
|
|
| |
Looks like we need to write some more tests. Only 76% covered.
|
|
|
| |
Add install of libtidy dependancy. Forgot about that.
|
|
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.
|