dev-python/bracex: new package

Package-Manager: Portage-2.3.96, Repoman-2.3.21
Signed-off-by: Alessandro Barbieri <lssndrbarbieri@gmail.com>

dev-python/bracex/Manifest

@@ -0,0 +1 @@
+DIST bracex-2.0.0.tar.gz 24223 BLAKE2B bbf24e000bc7c2e1055e5a1a9b685c9b44ff49c2678b4b3bc43f9643277d8fba5e721b905f4f133903ef894a37633e1aa07dfd19ebd5396514dd15603bef3887 SHA512 0d8c8334dc6c3546413d5af8f3e10756c9b4a20f2462dff548fca3832968095fbddee9d2e10528960e0739ffacbb2fc475c042764148a45d5134f902b449df7f

dev-python/bracex/bracex-2.0.0.ebuild

@@ -0,0 +1,38 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_6 )
+#DISTUTILS_USE_SETUPTOOLS=rdepend
+
+inherit distutils-r1
+
+DESCRIPTION="Bash style brace expansion for Python"
+HOMEPAGE="
+	https://github.com/facelessuser/bracex
+	https://pypi.org/project/bracex
+"
+SRC_URI="https://github.com/facelessuser/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="doc"
+
+RDEPEND=""
+DEPEND="
+	${RDEPEND}
+	doc? (
+		dev-python/mkdocs-git-revision-date-localized-plugin[${PYTHON_USEDEP}]
+		dev-python/mkdocs_pymdownx_material_extras[${PYTHON_USEDEP}]
+		dev-python/pyspelling[${PYTHON_USEDEP}]
+	)
+"
+
+distutils_enable_tests pytest
+
+python_compile_all() {
+	use doc && mkdocs build || die
+	default
+}

dev-python/bracex/metadata.xml

@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+
+<pkgmetadata>
+  <maintainer type="person">
+    <email>lssndrbarbieri@gmail.com</email>
+    <name>Alessandro Barbieri</name>
+  </maintainer>
+  <upstream>
+    <remote-id type="github">facelessuser/bracex</remote-id>
+    <remote-id type="pypi">bracex</remote-id>
+  </upstream>
+  <longdescription lang="en">
+    Why Bracex over other solutions?
+
+    Bracex actually follows pretty closely to how Bash processes braces. It is not a 1:1 implementation of how Bash handles braces, but generally, it follows very closely. Almost all of the test cases are run through Bash first, then our implementation is compared against the results Bash gives. There are a few cases where we have purposely deviated. For instance, we are not handling Bash's command line inputs, so we are not giving special meaning to back ticks and quotes at this time.
+  </longdescription>
+</pkgmetadata>