| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #601. Merged in 6f87b32 from the md3 branch and did a lot of cleanup.
Changes include:
* Removed old docs build tool, templates, etc.
* Added MkDocs config file, etc.
* filename.txt => filename.md
* pythonhost.org/Markdown => Python-Markdown.github.io
* Markdown lint and other cleanup.
* Automate pages deployment in makefile with `mkdocs gh-deploy`
Assumes a git remote is set up named "pages". Do
git remote add pages https://github.com/Python-Markdown/Python-Markdown.github.io.git
... before running `make deploy` the first time.
|
| |
|
| |
|
| |
|
|
|
|
| |
This fixes warnings with pycodestyle ≥ 2.1, see PyCQA/pycodestyle#400.
|
| |
|
| |
|
|
|
|
|
|
| |
Got all but a couple files in the tests (ran out of time today).
Apparently I have been using some bad form for years (although a few
things seemed to look better before the update). Anyway, conformant now.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
'https://pythonhosted.org/Markdown/'. The former redirects to the latter anyway. Might as well point to the actual destination.
|
|
|
|
| |
and use it in our docs
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The most notable changes are the use of unicode_literals
and absolute_imports. Actually, absolute_imports was the
biggest deal as it gives us relative imports. For the first
time extensions import markdown relative to themselves.
This allows other packages to embed the markdown lib in a
subdir of their project and still be able to use our
extensions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also refactored the version info to force PEP 386 compliance and to avoid
the need to change the version in both the source and setup.py
|
| |
|
| |
|
|
|
|
| |
so that there's no text breakage on PyPI page
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The documentation uses features of Python-Markdown that are not supported on
GitHub and it's better to get a source view of the docs anyway. For example,
that way comments and bug reports can reference a specific line of a file.
Of course, it makes sense for Github to render the README, so that is left
with the `.md` file extension.
|
| |
|
|
|
|
|
|
| |
This is not a full Sphinx implementation. Just a limited implementation
which converts our markdown source filed to work with the default css for
Sphinx so it looks like Pythons docs.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the file system.
|
| |
|
| |
|
|
|
|
| |
editors on the console. Let's keep lines under 80 characters in length.
|
|
|
|
| |
build_docs would be the one that wasn't 2to3'ed, thus causing a syntax error).
|
|
|
|
| |
docs. Still need to add the data to the docs themselves. That will come when I update the docs.
|
|
|
|
| |
still does not install docs on the system. It just writes html to the temp build dir.
|
|
|
|
| |
docs (should) now validate as xhtml - assuming they parse correctly. I suspect the docs need some updating though.
|
|\ |
|
| |
| |
| |
| | |
and 3.x in the setup script. Now the script actually can run 2to3 automaticaly when run under Python 3.x. Thanks for the report Virgil Dupras.
|
|/
|
|
| |
(converts text files to html) in the build dir. It does not install them on the system.
|
| |
|
|
|
|
| |
it should have been for some time now. Also updated classifiers to correctly represent the Python versions we support. Removed 2.3 and added 2.7.
|
|
|
|
| |
only officially support Python 3.1+ in the Python 3 series (we still support 2.4, 2.5 & 2.6 in the Python 2 series). If you really must use Python 3.0, we suggest using Python 3.1's 2to3 tool. See comment in source and Ticket 66 for more.
|
|
|
|
| |
because 'markdown' conflicts with the perl implementation. 'markdown_py' will at least still work with tab completion when the user types 'markdown'.
|
|
|
|
| |
all dependencaies for the lib are present, so we can't actuly import the lib until after we check for dependencies - which means we can't import version in the setup script. Grrr. We'll have to remember to update the version number in both places from now on. Sigh.
|
|
|
|
| |
version < 2.5. Since Cheetah just added a dependency on Markdown (in 2.2.2) we've received numerious complaints from people trying to easy_install Cheetah on older pythons.
|