| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All file-based tests are now defined as unittest test cases via a
metaclass which walks a directory and builds a unittest for each pair
of test files.
To run the tests just run `python -m unittest discover tests`. Or use
tox as the tox config has been updated to run the new tests and all nose
specific code has been removed.
The test generator tools have been removed as well. If any changes or
additions need to be made to tests, they should be implemented using
the new framework rather than with the file-based tests. Eventually,
only the PHP and pl tests should remain as file-based tests.
|
| |
|
|
|
|
| |
* Install deps.
* Ensure test fails if deps are missing.
* Update dictionary for recent docs changes.
|
| | |
|
| |
|
|
| |
That way py32 tests can still be run locally. Just not on the CI server.
|
| |
|
| |
Pip version 8 dropped support for Python 3.2 and by testing it we are getting errors (related to pip, not Markdown) on that version only. Removing the Py32 tests for now so our automated tools continue to work.
|
| |
|
| |
The `downloadcache` config value is deprecated by tox and the related `--download-cache` flag is removed on pip version 8.0 (deprecated in 6.0). With this change tests should run with the lasted versions of all tools (they do not without it).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
This should make it easier to install test deps even when not using tox.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
PyTidyLib Python 3 issues have been fixed in 0.2.3 release
|
| | |
|
| |\ |
|
| | | |
|
| |/
|
|
| |
Looks like we need to write some more tests. Only 76% covered.
|
| | |
|
|
|
Also scrapped fabfile.py and replaced it with a much
simpler makefile. Tox does most of the stuff that was
in fabfile.py anyway.
Now that everything runs in all supported python versions
without using 2to3, we don't need to wait for tox to
support it.
|
