| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Add better logic to admonitions to account for more complex list cases
Fixes #1004
|
|
|
|
| |
Fixes #897.
|
|
|
|
| |
Fixes #894.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Ignore empty braces. Braces must contain at least one non-whitepsace
character to be recognized as an attr list.
Attr lists for table cells must be at the end of the cell content and must
be seperated from the content by at least one space. This appears to be
a breaking change. However, it is consistent with the behavior elsewhere.
Fixes #898.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, we'd unescape both `>` and `>` to the same
string because we were running the & => & replacement first.
By changing the order of this replacement, we now convert:
`> >` => `> >`
as expected.
Fixes #988.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the Python stack comes within 100 frames of the recursion limit,
then the nesting limit of blockquotes is met. Any remaining text,
including angle brackets, are simply wrapped in a paragraph. To
increasing the nesting depth, increase Python's recursion limit.
However, be aware that each level of recursion will likely result in
multiple frames being added to the Python stack. Therefore, the
recursion depth and nesting depth are not one-to-one.
Performance is an concern here. However, the current solution seems like
a reasonable compromise. It doesn't slow things down too much, but also
avoids Markdown input resulting in an error. This is mostly only a concern
with contrived input anyway. For the average Markdown document, this will
likely never be an issue.
Fixes #799.
|
|
|
|
|
| |
Document the behavior of single terms and clarify other behaviors.
Addresses #964.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add `language-` prefix to output when syntax highlighting is
disabled for both codehilite and fenced_code extensions.
* Add `lang_prefix` config option to customize the prefix.
* Add a 'pygments' env to tox which runs the tests with Pygments
installed. Pygments is locked to a specific version in the env.
* Updated codehilite to accept any Pygments options.
* Refactor fenced code attributes.
- ID attr is defined on `pre` tag.
- Add support for attr_list extension, which allows setting arbitrary
attributes.
- When syntax highlighting is enabled, any pygments options can
be defined per block in the attr list.
- For backward compatibility, continue to support `hi_lines` outside
of an attr_list. That is the only attr other than lang which is allowed
without the brackets (`{}`) of an attr list. Note that if the brackets
exist, then everything, including lang and hl_lines, must be within
them.
* Resolves #775. Resolves #334. Addresses #652.
|
|
|
|
|
| |
Resolves issue that can occur with complex emphasis combinations.
Fixes #979
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are too many random arbitrary failures with this check. We still
want the check to run to ensure we don't introduce any new errors.
However, the random errors on external URLs are frustrating, especcially
when a different URL fails on each run. And then when the URL is checked
manually, it is clearly good.
If the tool provided a flag to limit the check to intenral URLs only (it
doesn't), we wouldn't use that anyway because we do want to know when an
extenral URL becomes invalid. Although, I suppose we could do two runs,
one intenral and one external and only allow the external to fail. But
that will have to wait until such a feature is added to the tool or we
find a better tool.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
* The build button/badge in the README now only points to push events so that an unmerged failing PR doesn't cause the build status to show as 'failing.'
* Restrict node setup to checklinks env.
|
|
|
| |
Point to GitHub workflow action rather than Travis.
|
|
|
|
|
| |
The latest version of flake8 added some new tests. This cleans up after
them.
|
|
|
|
| |
Closes #965.
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Also clean up dead links.
|
|
|
|
|
| |
* Move Patterns sections. Fixes #729.
* Rewrite tree processor docs. Fixes #949.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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`.
|
|
|
| |
Also Raise a `KeyError` when attempting to delete a nonexistent key from the extension registry.
|
| |
|
|
|
|
| |
This should be more performant. Fixes #942.
|
|
|
| |
Fixes #931.
|
|
|
|
|
| |
Not sure how tests didn't get run on this, but it was completely
breaking all tests. This reverts the change.
|
|
|
|
| |
`util` already provides the regex we need for all placeholders, and we're doing extra work parsing for the explicit union of all of them.
In documents with ~30000 placeholders, I get a ~5x speedup with this change.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed spellings :
1. shebang
2. identification
Added 'the' before 'said'
Fixed vertical line column size to 79
Fixed failing tests : Removed trailing spaces
|
| |
|
|
|
|
| |
Closes #913
|
| |
|
|
|
|
| |
Fixes #906.
|
| |
|
| |
|
|
|
| |
Resolves #892.
|
|
|
|
|
|
|
|
| |
cElementTree is a deprecated alias for ElementTree since Python 3.3.
Also drop the recommendation to import etree from markdown.util,
and deprecate markdown.util.etree.
|
|
|
|
|
|
| |
Note: this slightly changes existing behavior in that raw HTML tags are no
longer included in the HTML `.toc`. However, the fact that that worked before
was an oversight. The intention was always to strip all markup. Resolves #899.
|
|
|
|
|
| |
Addes a new `permalink_title` option to the TOC extension, which allows the title attribute of a permalink to be set to something other than the default English string "Permanent link".
Fixes #781.
|
|
|
|
|
|
|
|
|
| |
Two new configuration options have been added to the toc extension:
`anchorlink_class` and `permalink_class` which allows class(es) to be
assigned to the `anchorlink` and `permalink` HTML respectively. This
allows using icon fonts from CSS for the links. Therefore, an empty string
passed to `permalink` now generates an empty `permalink`. Previously
no `permalink` would have been generated. Based on #776.
|
|
|
|
|
|
|
|
| |
Tox has already been removed from `make test` and is no longer recommended
for testing in the contributing guide. Additionally, the extra tests it runs
(checking the spelling of documentation, etc) are of no value to end users.
As things are currently set us, tox is only used on the Travis CI server.
Given the above, there is no reason to include it in the release tarball.
Closes #808.
|
|
|
|
|
| |
Fixed #812.
|
|
|
|
|
|
| |
The slugify function will stript the STX and ETX characters from
placeholders for backslash excaped characters. Therefore, we need
to unescape any text before passing it to slugify. Fixes #864.
|
|
|
|
|
|
|
|
|
| |
Ensures anyone still using Python 2 gets a readable error message.
This does not specify a specific version number to remove the maintenance
burden of updating it with each future release. It will likely get removed
in the next few releases as it will have served its purpose by then.
Fixes #871.
|
|
|
|
|
|
| |
As per the Contributing Guide, this should have happened before we commited
various 3.2 related changes. In any event, version 3.2 is now officially in
development status.
|