public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/manhole/
Date: Sun, 29 Mar 2020 09:29:08 +0000 (UTC)	[thread overview]
Message-ID: <1585474143.31bf152ba6cc3ebc667013e190e26a6d415b1c78.Alessandro-Barbieri@gentoo> (raw)

commit:     31bf152ba6cc3ebc667013e190e26a6d415b1c78
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Sun Mar 29 09:17:09 2020 +0000
Commit:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Sun Mar 29 09:29:03 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=31bf152b

dev-python/manhole: new package

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

 dev-python/manhole/Manifest             |  1 +
 dev-python/manhole/manhole-1.6.0.ebuild | 47 +++++++++++++++++++++++++++++++++
 dev-python/manhole/metadata.xml         | 20 ++++++++++++++
 3 files changed, 68 insertions(+)

diff --git a/dev-python/manhole/Manifest b/dev-python/manhole/Manifest
new file mode 100644
index 0000000..2d8dd7f
--- /dev/null
+++ b/dev-python/manhole/Manifest
@@ -0,0 +1 @@
+DIST manhole-1.6.0.tar.gz 30111 BLAKE2B e6cffb465d72d579d3c901b5f163248ea28f3a208d2b487207a4f2d949994b7b778808b19a3bde0047bc71c2fe1865a12f9dcc5ac4f5407745879c8648df6c89 SHA512 179a87529e371c4480b6ab0ad6cc6cc9e3942f4be339cacaf1f1b100e447b8b1f2903a03879e9df3376c86ced4421aa5a16d934c9b250f91715b28d03dca000a

diff --git a/dev-python/manhole/manhole-1.6.0.ebuild b/dev-python/manhole/manhole-1.6.0.ebuild
new file mode 100644
index 0000000..37db2bb
--- /dev/null
+++ b/dev-python/manhole/manhole-1.6.0.ebuild
@@ -0,0 +1,47 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{6,7} )
+
+inherit distutils-r1
+
+MYPN="python-${PN}"
+
+DESCRIPTION="Debugging manhole for python application"
+HOMEPAGE="
+	https://github.com/ionelmc/python-manhole
+	https://pypi.org/project/python-manhole
+"
+SRC_URI="https://github.com/ionelmc/${MYPN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+LICENSE="BSD-2"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+RDEPEND=""
+DEPEND="
+	${RDEPEND}
+	test? (
+		dev-python/eventlet[${PYTHON_USEDEP}]
+		dev-python/gevent[${PYTHON_USEDEP}]
+		dev-python/process-tests[${PYTHON_USEDEP}]
+		dev-python/pytest-travis-fold[${PYTHON_USEDEP}]
+		dev-python/requests[${PYTHON_USEDEP}]
+		www-servers/uwsgi[${PYTHON_USEDEP}]
+	)
+"
+
+S="${WORKDIR}/${MYPN}-${PV}"
+
+python_prepare_all() {
+	#no coverage
+	#sed -i 's|--cov-report term-missing||' setup.cfg || die
+	#sed -i 's|nocover: false|nocover: true|' setup.cfg || die
+	distutils-r1_python_prepare_all
+}
+
+distutils_enable_tests pytest
+distutils_enable_sphinx docs \
+				dev-python/sphinx-py3doc-enhanced-theme \
+				dev-python/sphinxcontrib-napoleon

diff --git a/dev-python/manhole/metadata.xml b/dev-python/manhole/metadata.xml
new file mode 100644
index 0000000..e407498
--- /dev/null
+++ b/dev-python/manhole/metadata.xml
@@ -0,0 +1,20 @@
+<?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>
+  <longdescription>
+Manhole is in-process service that will accept unix domain socket connections and present the stacktraces for all threads and an interactive prompt. It can either work as a python daemon thread waiting for connections at all times or a signal handler (stopping your application and waiting for a connection).
+
+Access to the socket is restricted to the application's effective user id or root.
+
+This is just like Twisted's manhole. It's simpler (no dependencies), it only runs on Unix domain sockets (in contrast to Twisted's manhole which can run on telnet or ssh) and it integrates well with various types of applications.
+  </longdescription>
+  <upstream>
+    <remote-id type="github">ionelmc/python-manhole</remote-id>
+    <remote-id type="pypi">manhole</remote-id>
+  </upstream>
+</pkgmetadata>


             reply	other threads:[~2020-03-29  9:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29  9:29 Alessandro Barbieri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-29 13:21 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/manhole/ Andrew Ammerlaan
2020-04-01 20:55 Alessandro Barbieri
2020-04-02 23:04 Alessandro Barbieri
2020-04-03 10:40 Andrew Ammerlaan
2020-06-09 14:00 Andrew Ammerlaan
2020-06-09 14:00 Andrew Ammerlaan
2020-09-24 12:17 Andrew Ammerlaan
2021-05-03 23:33 Anna Vyalkova
2021-05-25 10:37 Anna Vyalkova
2021-05-26 12:03 Anna Vyalkova
2021-08-14  2:00 Anna Vyalkova
2021-10-03 22:55 Alessandro Barbieri
2021-10-18 12:07 Anna Vyalkova
2021-10-23 14:04 Anna Vyalkova
2021-11-29 10:37 Anna Vyalkova
2021-12-06 16:10 Anna Vyalkova
2022-06-05  6:16 Anna Vyalkova
2022-10-17 12:12 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2022-10-17 12:12 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2022-10-23 21:04 Anna Vyalkova
2022-11-17 21:22 Anna Vyalkova
2024-05-25 12:41 Julien Roy

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=1585474143.31bf152ba6cc3ebc667013e190e26a6d415b1c78.Alessandro-Barbieri@gentoo \
    --to=lssndrbarbieri@gmail.com \
    --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