aboutsummaryrefslogtreecommitdiffstats
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* smart_emphasis keyword > legacy_em extension.Waylan Limberg2018-07-311-1/+1
| | | | | | | | | The smart_strong extension has been removed and its behavior is now the default (smart em and smart strong are the default). The legacy_em extension restores legacy behavior (no smart em or smart strong). This completes the removal of keywords. All parser behavior is now modified by extensions, not by keywords on the Markdown class.
* Consistent copyright headers.Waylan Limberg2018-07-271-0/+22
| | | | Fixes #435.
* Add support for PY37 and PYPY3.Waylan Limberg2018-07-241-2/+2
|
* Moved enable_attributes keyword to extension: legacy_attrs.Waylan Limberg2018-07-241-0/+1
| | | | | | | If you have existing documents that use the legacy attributes format, then you should enable the legacy_attrs extension for those documents. Everyone is encouraged to use the attr_list extension going forward. Closes #643. Work adapted from 0005d7a of the md3 branch.
* Refactor Extension loading (#627)Waylan Limberg2018-01-121-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Deprecated naming support is removed: * Removed special treatment for modules in `markdown.extensions` * Removed support for `mdx_` prefixes. Support for Entry Point names added: Support for "short names" are now implemented with entry points. Therefore all the users who call extension names as `toc` will not get errors as the builtin extensions all have entry points defined which match the old "short names" for modules in `markdown.extensions`. The benefit is that any extension can offer the same support without requiring the user to manually copy a file to that location on the file system (way to many extension authors have included such instructions in their installation documentation). The one odd thing about this is that we have been issuing a DeprecationWarning for short names and now they are fully supported again. But I think it's the right thing to do. Support for using dot notation is not removed. After all, it was never deprecated. And we shouldn't "force" entry points. There are plenty of reasons why users may not want that and not all of them can be resolved by using class instances instead. All of the following ways to load an extension are valid: # Class instance from markdown.extensions.toc import TocExtension markdown.markdown(src, extensions=[TocExtension()] # Entry point name markdown.markdown(src, extensions=['toc']) # Dot notation with class markdown.markdown(src, extensions=['markdown.extensions.toc:TocExtension']) # Dot notation without class markdown.markdown(src, extensions=['markdown.extensions.toc'])
* Moved core to core.pyWaylan Limberg2018-01-111-28/+14
| | | | | | __version__ is now in __init__.py (as is should be) and the core is defined in core.py. Other than version, __init__.py is just a dummy which imports the pieces we make public.
* Restore code to use markdown_py as the console script name.Dmitry Shachnev2017-12-101-1/+6
|
* Build and upload wheels for releases.Waylan Limberg2017-12-081-1/+1
| | | | Update install docs.
* Switch to setuptools.Waylan Limberg2017-12-081-51/+19
| | | | Use console_scripts entry_point instead of manually built script.
* Switch docs to MKDocs (#602)Waylan Limberg2017-12-061-154/+4
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* Update builds with py35 and py36 supportfacelessuser2017-11-171-0/+2
|
* Adjust for new PyPI changesWaylan Limberg2017-08-171-2/+2
|
* GitHub/waylan => GitHub/Python-Markdown orgWaylan Limberg2017-08-171-1/+1
|
* Add blank lines after toplevel function definitions.Dmitry Shachnev2016-11-181-0/+2
| | | | This fixes warnings with pycodestyle ≥ 2.1, see PyCQA/pycodestyle#400.
* flake8ifyMarc Abramowitz2014-12-091-8/+12
|
* Updated author emailWaylan Limberg2014-11-301-2/+2
|
* Flake8 cleanup (mostly whitespace).Waylan Limberg2014-11-201-55/+72
| | | | | | 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.
* 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.
* 'http://packages.python.org/Markdown/' => ↵Waylan Limberg2014-08-211-4/+4
| | | | 'https://pythonhosted.org/Markdown/'. The former redirects to the latter anyway. Might as well point to the actual destination.
* Add new "permalink" option to toc extensionDmitry Shachnev2013-09-251-1/+2
| | | | and use it in our docs
* Use smarty extension when building docsDmitry Shachnev2013-07-261-1/+1
|
* Added Python 3.3 to list of supported versions and removed 2.5.Waylan Limberg2013-03-061-1/+1
|
* Now using universal code for Python 2 & 3.Waylan Limberg2013-02-271-9/+0
| | | | | | | | | | 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.
* Build_docs script now uses new Admonition extension.Waylan Limberg2013-02-121-1/+1
|
* Support disabling documentation build via --no-build-docs.Michał Górny2013-01-131-1/+12
|
* No longer support python 2.5Waylan Limberg2013-01-101-7/+1
|
* Fixed #169. The new version stuff now works in python 2 & 3.Waylan Limberg2012-12-181-3/+12
|
* Upped version to 2.3.dev.Waylan Limberg2012-12-051-2/+16
| | | | | 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
* Upped version to 2.2.1.Waylan Limberg2012-11-041-2/+1
|
* Remove unneeded linkDmitry Shachnev2012-09-091-1/+0
|
* setup.py: Add `long_description` attribute to `data`Dmitry Shachnev2012-09-091-0/+22
| | | | so that there's no text breakage on PyPI page
* Fixed #115. Make sure all file objects are closed.Waylan Limberg2012-07-121-2/+5
|
* Updated version to 2.2.0.alpha.2.2.0.alphaWaylan Limberg2012-05-041-8/+8
|
* Point to docs hosted with PyPI rather than Yuri's missing site.Waylan Limberg2012-03-071-3/+3
|
* Rename docs/*.md => docs/*.txtWaylan Limberg2012-03-071-1/+1
| | | | | | | | | 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.
* Fixed a few minor redering bugs in docs.Waylan Limberg2012-03-071-8/+12
|
* Refactored Docs to use Sphinx styled template.Waylan Limberg2012-03-011-17/+42
| | | | | | 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.
* Release 2.1.1. A bugfix release.2.1.1.finalWaylan Limberg2012-01-221-1/+1
|
* Version 2.1.0-Final2.1.0.finalWaylan Limberg2011-11-241-1/+2
|
* Release 2.1.0-Beta2.1.0.betaWaylan Limberg2011-10-101-1/+1
|
* Added support to build_docs command to copy non markdown files unmodified.Waylan Limberg2011-08-231-0/+4
|
* Update build_docs script for the *.txt -> *.md change in docs.Waylan Limberg2011-08-231-9/+1
|
* The build_docs command now uses extra and toc extensions and a template on ↵Waylan Limberg2011-08-041-31/+14
| | | | the file system.
* Set version to '2.1.0.alpha'.2.1.0.alphaWaylan Limberg2011-08-031-1/+1
|
* setup.py: Replaced file(.) with open(.) as Python 3 doesn't have file(.)Henri Wiechers2011-01-211-1/+1
|
* Fixed line length of previous commit. Some of us still use (and prefer) text ↵Waylan Limberg2011-01-091-2/+2
| | | | editors on the console. Let's keep lines under 80 characters in length.
* Fixed setup.py to work with python 3.x (The imported markdown module in ↵Virgil Dupras2011-01-091-4/+8
| | | | build_docs would be the one that wasn't 2to3'ed, thus causing a syntax error).
* Added the mechanism for simple unstlyed navigation menu to the generated ↵Waylan Limberg2010-08-201-11/+30
| | | | docs. Still need to add the data to the docs themselves. That will come when I update the docs.
* Made the build_docs command a subcommand of build in setup script. This ↵Waylan Limberg2010-08-201-5/+12
| | | | still does not install docs on the system. It just writes html to the temp build dir.
* Added a simple unstyled template to the build_docs script. The generated ↵Waylan Limberg2010-08-201-2/+35
| | | | docs (should) now validate as xhtml - assuming they parse correctly. I suspect the docs need some updating though.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-12 19:15:11 +0000