summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix typos and remove trailing spacesKian-Meng Ang2022-04-101-1/+1
|
* update install requires to drop quotesZiyang Liu2021-11-171-1/+1
|
* Support Python 3.10Waylan Limberg2021-11-161-1/+2
| | | Fixes #1124.
* Remove download_url from setup.py (#1164)Waylan Limberg2021-07-301-1/+0
| | | | This is an old, outdated key which is simply moved into `project_urls`. As it offers no value, it is being removed. Fixes Python-Markdown#1163.
* Replace links to freewisdom.orgWaylan Limberg2021-02-061-2/+2
| | | | | | | | | Yuri's site (freewisdom.org) has gone offline. I have linked to his GitHub profile instead. Also, the developer's email address (markdown@freewisdom.org) has been replaced with a new address (python.markdown@gmail.com). The new address simply forwards all incoming messages to the project developer (@waylan) and deletes the messages.
* Add PY39 support and drop PY35 (#1026)Waylan Limberg2020-10-061-2/+2
| | | | Python 3.5 reached end-of-life on 2020-09-12 and Python 3.9 was released on 2020-10-05.
* Add Markdown text processing classifier to setupÁlvaro Mondéjar2020-08-241-1/+2
|
* Add project urlsWaylan Limberg2020-05-211-0/+5
|
* Use README.md for long_description.Waylan Limberg2020-05-181-21/+3
| | | | | | | | With `long_description_content_type="text/markdown"` it is now possible to use Markdown text in the `long_description` meta-data field. Make sure the latest tools (setuptools, wheel, twine) are installed before deploying. See https://dustingram.com/articles/2018/03/16/markdown-descriptions-on-pypi/ for details.
* Fix importlib-metadata requirement name for Python < 3.8Dmitry Shachnev2020-05-111-1/+1
|
* Avoid importing packaging or pkg_resources for version validation (#948)Ran Benita2020-04-271-1/+1
| | | | | | | | | | | | | | Importing the `pkg_resources` module has high memory and startup time cost. A recent change in 102e01c already avoided it for loading extensions, but it's still used for validating that __version__ is correctly formatted. It is possible to avoid it by installing the `packaging` package, but that adds a dependency for something quite trivial. Instead, remove the validation and add tests which check the output is as expected. Since `setuptools` is no longer required at runtime, remove it from `install_required`.
* Load entry_points once using importlib.metadata.Waylan Limberg2020-04-181-1/+1
| | | | This should be more performant. Fixes #942.
* Add support for Python 3.8 (#867)Hugo van Kemenade2019-10-241-0/+1
| | | Related to #760.
* Drop support for Python 2.7 (#865)Hugo van Kemenade2019-10-241-10/+2
| | | | | | | * Python syntax upgraded using `pyupgrade --py3-plus` * Travis no longer uses `sudo`. See https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration See #760 for Python Version Support Timeline and related dicussion.
* Document PyPy support in setup.pyjohnthagen2019-09-131-0/+2
|
* Separate Markdown parsing in HTML to separate extension (#859)Isaac Muse2019-09-041-0/+1
| | | | | Move Markdown parsing from the extra extension to a separate extension called md_in_html.
* Use https:// links where availableJon Dufresne2019-06-121-2/+2
|
* Comply with PEP517 (#824)Dmitry Shachnev2019-05-151-1/+20
| | | | | | | | Add pep517check environment to tox Split version info into a separate file, load it using importlib Fixes #823.
* Remove references to mailing list.Waylan Limberg2019-03-041-3/+2
| | | | Fixes #793.
* Drop Python3.4 Support (#796)Waylan Limberg2019-03-041-2/+1
| | | Python is dropping support for PY3.4 on 2019-03-16. Therefore we are dropping support as well. See #760.
* Improve CI / testing (#754)Daniel Hahler2018-11-151-0/+6
| | | | | | | | | | | | | | | | | | | | * Use "testing" extras_require This centralized testing requirements and allows for `pip install -e .[testing]` etc. pytidylib is kept separate according to https://github.com/Python-Markdown/markdown/pull/754/files#r233561159. * Travis: simplify installation of deps * Travis: use xenial by default, trusty for py34 * Travis: codecov: use flags * Travis: only install aspell for checkspelling job * Remove coverage version restriction
* Up version to 3.1.dev0 (#736)Waylan Limberg2018-10-211-4/+3
| | | | | | | | Update version format to be PEP 440 compliant in preparation for #732. Add `pyproject.toml` file and configure tox to use it. Define requirement for `setuptools>=36` which validates and normalizes the version format.
* 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
View Lorry Controller Status