Navigation:
Browse pkgsrc
(this page) 2023-04-03 14:06:01 by Adam Ciarcinski | Files touched by this commit (3) |  |
Log message: py-markdown: updated to 3.4.3 version 3.4.3 (a bug-fix release). * Restore console script. version 3.4.2 (a bug-fix release). * Improve standalone * and _ parsing. * Consider `<html>` HTML tag a block-level element. * Officially support Python 3.11. * Switch from `setup.py` to `pyproject.toml`. |
| 2023-03-29 11:34:15 by Thomas Klausner | Files touched by this commit (96) |
Log message: *: use PYTHON_VERSION instead of _PYTHON_VERSION |
| 2022-11-09 14:14:32 by Joerg Sonnenberger | Files touched by this commit (223) |
Log message: Reset MAINTAINER |
| 2022-10-25 17:55:35 by Adam Ciarcinski | Files touched by this commit (3) | |
Log message:
py-markdown: updated to 3.4.1
Python-Markdown 3.4 Release Notes
Python-Markdown version 3.4 supports Python versions 3.7, 3.8, 3.9, 3.10 and
PyPy3.
Backwards-incompatible changes
The `tables` extension now uses a `style` attribute instead of an `align` \
attribute for alignment.
The [HTML4 spec][spec4] specifically deprecates the use of the `align` attribute
and it does not appear at all in the [HTML5 spec][spec5]. Therefore, by default,
the [tables] extension will now use the `style` attribute (setting just the
`text-align` property) in `td` and `th` blocks.
[spec4]: https://www.w3.org/TR/html4/present/graphics.html#h-15.1.2
[spec5]: \
https://www.w3.org/TR/html53/tabular-data.html#attributes-common-to-td-and-th-elements
[tables]: ../extensions/tables.md
The former behavior is available by setting the `use_align_attribute`
configuration option to `True` when enabling the extension.
For example, to configure the old `align` behavior:
```python
from markdown.extensions.tables import TableExtension
markdown.markdown(src, extensions=[TableExtension(use_align_attribute=True)])
```
Backslash unescaping moved to Treeprocessor.
Unescaping backslash escapes has been moved to a Treeprocessor, which enables
proper HTML escaping during serialization. However, it is recognized that
various third-party extensions may be calling the old class at
`postprocessors.UnescapePostprocessor`. Therefore, the old class remains in the
code base, but has been deprecated and will be removed in a future release. The
new class `treeprocessors.UnescapeTreeprocessor` should be used instead.
Previously deprecated objects have been removed
Various objects were deprecated in version 3.0 and began raising deprecation
warnings (see the [version 3.0 release notes] for details). Any of those objects
which remained in version 3.3 have been removed from the code base in version 3.4
and will now raise errors. The relevant objects are listed below.
[version 3.0 release notes]: release-3.0.md
| Deprecated Object | Replacement Object |
|----------------------------------------|-------------------------------------|
| `markdown.version` | `markdown.__version__` |
| `markdown.version_info` | `markdown.__version_info__` |
| `markdown.util.etree` | `xml.etree.ElementTree` |
| `markdown.util.string_type` | `str` |
| `markdown.util.text_type` | `str` |
| `markdown.util.int2str` | `chr` |
| `markdown.util.iterrange` | `range` |
| `markdown.util.isBlockLevel` | `markdown.Markdown().is_block_level`|
| `markdown.util.Processor().markdown` | `markdown.util.Processor().md` |
| `markdown.util.Registry().__setitem__` | `markdown.util.Registry().register` |
| `markdown.util.Registry().__delitem__` |`markdown.util.Registry().deregister`|
| `markdown.util.Registry().add` | `markdown.util.Registry().register` |
In addition, the `md_globals` parameter of
`Markdown.extensions.Extension.extendMarkdown()` is no longer recognized as a
valid parameter and will raise an error if provided.
New features
The following new features have been included in the 3.4 release:
* Some new configuration options have been added to the
[footnotes](../extensions/footnotes.md) extension:
* Small refactor of the `BACKLINK_TITLE` option; The use of `format()`
instead of "old" `%d` formatter allows one to specify text \
without the
need to have the number of the footnote in it (like footnotes on
Wikipedia for example). The modification is backward compatible so no
configuration change is required.
* Addition of a new option `SUPERSCRIPT_TEXT` that allows one to specify a
custom placeholder for the footnote itself in the text.
Ex: `[{}]` will give `<sup>[1]</sup>`, `({})` will give \
`<sup>(1)</sup>`,
or by default, the current behavior: `<sup>1</sup>`.
* The [Table of Contents](../extensions/toc.md) extension now accepts a
`toc_class` parameter which can be used to set the CSS class(es) on the
`<div>` that contains the Table of Contents.
* The CodeHilite extension now supports a `pygments_formatter` option that can
be set to a custom formatter class.
- If `pygments_formatter` is set to a string (ex: `'html'`), Pygments'
default formatter by that name is used.
- If `pygments_formatter` is set to a formatter class (or any callable
which returns a formatter instance), then an instance of that class is
used.
The formatter class is now passed an additional option, `lang_str`, to
denote the language of the code block. While Pygments' built-in
formatters will ignore the option, a custom formatter assigned to the
`pygments_formatter` option can make use of the `lang_str` to include the
code block's language in the output.
Bug fixes
The following bug fixes are included in the 3.4 release:
* Extension entry-points are only loaded if needed.
* Added additional checks to the `<pre><code>` handling of
`PrettifyTreeprocessor`.
|
| 2022-01-05 16:41:32 by Thomas Klausner | Files touched by this commit (289) |
Log message: python: egg.mk: add USE_PKG_RESOURCES flag This flag should be set for packages that import pkg_resources and thus need setuptools after the build step. Set this flag for packages that need it and bump PKGREVISION. |
| 2022-01-04 21:55:40 by Thomas Klausner | Files touched by this commit (1595) |
Log message: *: bump PKGREVISION for egg.mk users They now have a tool dependency on py-setuptools instead of a DEPENDS |
| 2021-11-01 22:43:46 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
py-markdown: update to 3.2.2.
# Python-Markdown 3.2 Release Notes
Python-Markdown version 3.2 supports Python versions 3.5, 3.6, 3.7, 3.8, and
PyPy3.
### Drop support for Python 2.7
Python 2.7 reaches end-of-life on 2020-01-01 and Python-Markdown 3.2 has dropped
support for it. Please upgrade to Python 3, or use Python-Markdown 3.1.
### `em` and `strong` inline processor changes
In order to fix issue #792, `em`/`strong` inline processors were refactored. This
translated into removing many of the existing inline processors that handled this
logic:
* `em_strong`
* `strong`
* `emphasis`
* `strong2`
* `emphasis`
These processors were replaced with two new ones:
* `em_strong`
* `em_strong2`
The [`legacy_em`](../extensions/legacy_em.md) extension was also modified with new,
refactored logic and simply overrides the `em_strong2` inline processor.
### CodeHilite now always wraps with `<code>` tags
Before, the HTML generated by CodeHilite looked like:
- `<pre><code>foo = 'bar'</code></pre>` if you **were \
not** using Pygments.
- `<pre>foo = 'bar'</pre>` if you **were** using Pygments.
To make the cases more consistent (and adhere to many Markdown specifications and
HTML code block markup suggestions), CodeHilite will now always additionally wrap
code with `<code>` tags. See #862 for more details.
This change does not alter the Python-Markdown API, but users relying on the old
markup will find their output now changed.
Internally, this change relies on the Pygments 2.4, so you must be using at least
that version to see this effect. Users with earlier Pygments versions will
continue to see the old behavior.
### `markdown.util.etree` deprecated
Previously, Python-Markdown was using either the `xml.etree.cElementTree` module
or the `xml.etree.ElementTree` module, based on their availability. In modern
Python versions, the former is a deprecated alias for the latter. Thus, the
compatibility layer is deprecated and extensions are advised to use
`xml.etree.ElementTree` directly. Importing `markdown.util.etree` will raise
a `DeprecationWarning` beginning in version 3.2 and may be removed in a future
release.
Therefore, extension developers are encouraged to replace
`from markdown.util import etree` with
`import xml.etree.ElementTree as etree` in their code.
## New features
The following new features have been included in the release:
* Some new configuration options have been added to the [toc](../extensions/toc.md)
extension:
* The `anchorlink_class` and `permalink_class` options allow class(es) to be
assigned to the `anchorlink` and `permalink` 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. (#776)
* The `permalink_title` option allows the title attribute of a `permalink` to be
set to something other than the default English string `Permanent link`. (#877)
* Document thread safety (#812).
* Markdown parsing in HTML has been exposed via a separate extension called
[`md_in_html`](../extensions/md_in_html.md).
* Add support for Python 3.8.
|
| 2021-11-01 22:06:35 by Thomas Klausner | Files touched by this commit (1) |
Log message: py-markdown: mark as not-for-python2.7 py-markdown3 does that. |
| 2021-10-26 13:23:42 by Nia Alarie | Files touched by this commit (1161) |
Log message: textproc: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes Unfetchable distfiles (fetched conditionally?): ./textproc/convertlit/distinfo clit18src.zip |
| 2021-10-07 17:02:49 by Nia Alarie | Files touched by this commit (1162) |
Log message: textproc: Remove SHA1 hashes for distfiles |
New packages: