public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocstrings/
Date: Tue, 11 Mar 2025 08:47:39 +0000 (UTC)	[thread overview]
Message-ID: <1741682849.cd4f24e12bd0b893e1cb570801bfecd26581ba71.mgorny@gentoo> (raw)

commit:     cd4f24e12bd0b893e1cb570801bfecd26581ba71
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 11 06:29:42 2025 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Tue Mar 11 08:47:29 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd4f24e1

dev-python/mkdocstrings: Bump to 0.29.0

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/mkdocstrings/Manifest                   |  1 +
 dev-python/mkdocstrings/mkdocstrings-0.29.0.ebuild | 54 ++++++++++++++++++++++
 2 files changed, 55 insertions(+)

diff --git a/dev-python/mkdocstrings/Manifest b/dev-python/mkdocstrings/Manifest
index 8fd2eb31177f..4df82747e632 100644
--- a/dev-python/mkdocstrings/Manifest
+++ b/dev-python/mkdocstrings/Manifest
@@ -1,2 +1,3 @@
 DIST mkdocstrings-0.28.2.tar.gz 5691916 BLAKE2B c1593205307285760f1d58db99e022b6ba43db1ab69ee024b109e98918407c1f256fedcddbab7778540cacb94764cdd7d5c042f39651554635fc68aa5727ebfc SHA512 946056f9ad179b58792756caf18f5881c2d24d05fc3adb24efe7fb8af7b44d68c648002098d4ff8b766ee6c9099bd918319df325fc5cb9854d47278c571f52ff
 DIST mkdocstrings-0.28.3.tar.gz 104109 BLAKE2B bbeba5319fd0912a214f0e8f7759abb7948ee1da6890472037f68a79f658bbdd29e32988e885e379cec05f61a616315f5baf1c575e460e0a774876929dc26bb8 SHA512 6d9e280aef8d8c35eb583a739b7f47b75fdc97ad093c91309ebfda3b6a1d9dcf31da7872d17eb00de3d731247f1f0396524f90d8db85519632dcdebae2f38bac
+DIST mkdocstrings-0.29.0.tar.gz 1212185 BLAKE2B 003f90c69a4b98f1f9049ed4fa74b165b7ed7a78b1bdf3cb8efa127a6115a3b26adca43d5787d9661b99b532d06cc9edf1d40efd97eed1a5c0c5d92d3e48627b SHA512 5a2ea61f59cf517482e18541aaabe6f284f2af43d9e8712e2096401bfba071f824f4c65f64d94ff57a09a8d625983655cae1466900ae6756e532ea2eb1c8755c

diff --git a/dev-python/mkdocstrings/mkdocstrings-0.29.0.ebuild b/dev-python/mkdocstrings/mkdocstrings-0.29.0.ebuild
new file mode 100644
index 000000000000..67ef3b74756c
--- /dev/null
+++ b/dev-python/mkdocstrings/mkdocstrings-0.29.0.ebuild
@@ -0,0 +1,54 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=pdm-backend
+PYTHON_COMPAT=( pypy3 pypy3_11 python3_{10..13} )
+
+inherit distutils-r1 pypi
+
+DESCRIPTION="Automatic documentation from sources, for MkDocs"
+HOMEPAGE="
+	https://mkdocstrings.github.io/
+	https://github.com/mkdocstrings/mkdocstrings/
+	https://pypi.org/project/mkdocstrings/
+"
+
+LICENSE="ISC"
+SLOT="0"
+KEYWORDS="~amd64 ~arm64 ~riscv"
+
+RDEPEND="
+	>=dev-python/jinja2-2.11.1[${PYTHON_USEDEP}]
+	>=dev-python/markdown-3.6[${PYTHON_USEDEP}]
+	>=dev-python/markupsafe-1.1[${PYTHON_USEDEP}]
+	>=dev-python/mkdocs-1.6[${PYTHON_USEDEP}]
+	>=dev-python/mkdocs-autorefs-1.4[${PYTHON_USEDEP}]
+	>=dev-python/pymdown-extensions-6.3[${PYTHON_USEDEP}]
+"
+BDEPEND="
+	test? (
+		dev-python/markdown-exec[${PYTHON_USEDEP}]
+		dev-python/mkdocs-material[${PYTHON_USEDEP}]
+		>=dev-python/mkdocstrings-python-1.16.2[${PYTHON_USEDEP}]
+		dev-python/sphinx[${PYTHON_USEDEP}]
+	)
+"
+
+# mkdocstrings documentation generation requires several currently
+# unpackaged mkdocs extensions and plug-ins, and this test
+# makes use of mkdocs configuration
+EPYTEST_DESELECT=(
+	tests/test_plugin.py::test_disabling_plugin
+	# WTF, it tries to unlink installed files from installed package?!
+	tests/test_handlers.py::test_extended_templates
+	# Needs unpackaged mkdocs-callouts, mkdocs-literate-nav, and possibly more
+	tests/test_inventory.py::test_sphinx_load_mkdocstrings_inventory_file
+	# Internet
+	tests/test_inventory.py::test_load_inventory
+)
+
+distutils_enable_tests pytest
+
+export PDM_BUILD_SCM_VERSION=${PV}


             reply	other threads:[~2025-03-11  8:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  8:47 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-09  3:35 [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocstrings/ Michał Górny
2025-03-09  3:35 Michał Górny
2025-02-25  8:14 Michał Górny
2025-02-25  7:51 Michał Górny
2025-02-25  7:51 Michał Górny
2025-02-15  7:01 Michał Górny
2025-02-15  7:01 Michał Górny
2025-02-04  4:28 Michał Górny
2024-11-08 20:27 Michał Górny
2024-10-13  3:10 Michał Górny
2024-09-07  6:26 Michał Górny
2024-09-07  6:26 Michał Górny
2024-09-02  3:02 Michał Górny
2024-07-26  1:57 Michał Górny
2024-07-06 18:09 Michał Górny
2024-06-28 11:38 Michał Górny
2024-06-17  2:52 Michał Górny
2024-05-06 15:29 Michał Górny
2024-04-28  2:37 Michał Górny
2024-04-20  5:40 Michał Górny
2024-04-05 18:52 Michał Górny
2024-04-03  5:31 Michał Górny
2024-02-28  4:03 Michał Górny
2023-12-30 18:30 Michał Górny
2023-11-23 20:33 Michał Górny
2023-11-22 12:43 Andrew Ammerlaan
2023-11-14 20:06 Michał Górny
2023-10-26  0:31 Marek Szuba
2023-09-02 14:11 Michał Górny
2023-08-23 21:06 Marek Szuba
2023-06-18 11:56 Michał Górny
2023-06-04  6:51 Michał Górny
2023-05-11 21:44 Marek Szuba
2023-05-11 10:56 Marek Szuba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1741682849.cd4f24e12bd0b893e1cb570801bfecd26581ba71.mgorny@gentoo \
    --to=mgorny@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox