From: get-state <mazin@getstate.dev>
To: 74057@debbugs.gnu.org
Cc: "Wiktor Żelazny" <wz@freeshell.de>,
=guix-patches@gnu.org, get-state <mazin@getstate.dev>,
"Lars-Dominik Braun" <lars@6xq.net>,
"Marius Bakke" <marius@gnu.org>,
"Munyoki Kilyungi" <me@bonfacemunyoki.com>,
"Sharlatan Hellseher" <sharlatanus@gmail.com>,
"Tanguy Le Carrour" <tanguy@bioneland.org>,
jgart <jgart@dismail.de>
Subject: [bug#74057] [PATCH v2 1/1] gnu: Add python-green.
Date: Fri, 1 Nov 2024 04:35:55 +0300 [thread overview]
Message-ID: <fb85e245bccdcb3b2a66beb454d3abc716cbd6e3.1730424294.git.mazin@getstate.dev> (raw)
In-Reply-To: <cover.1730424294.git.mazin@getstate.dev>
From: Wiktor Żelazny <wz@freeshell.de>
* gnu/packages/python-check.scm (python-green): New variable.
Change-Id: I554e8a635ff51413c79e3834fc1b88b34bbda84b
Signed-off-by: get-state <mazin@getstate.dev>
---
gnu/packages/python-check.scm | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/gnu/packages/python-check.scm b/gnu/packages/python-check.scm
index ba66b081a5..3d181c8f7e 100644
--- a/gnu/packages/python-check.scm
+++ b/gnu/packages/python-check.scm
@@ -3003,3 +3003,27 @@ (define-public python-vulture
dead code. Also, code that is only called implicitly may be reported as
unused.")
(license license:expat)))
+
+(define-public python-green
+ (package
+ (name "python-green")
+ (version "4.0.2")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (pypi-uri "green" version))
+ (sha256
+ (base32 "1cd62nbn5dvlpnsyplp6cb24wd230san8dpm6pnl99n2kwzpq1m4"))))
+ (build-system pyproject-build-system)
+ ;; python-coverage both in requirements.txt and requirements-dev.txt
+ (propagated-inputs (list python-colorama python-coverage python-lxml
+ python-unidecode))
+ (native-inputs (list python-black python-django python-mypy
+ python-testtools))
+ (home-page "https://github.com/CleanCut/green")
+ (synopsis "Clean, colorful, fast python test runner")
+ (description
+ "@code{green} is a python test runner which in addition to
+being clean, colorful and fast describes itself as powerful, traditional,
+descriptive, convenient, thorough, embedded, modern, portable and living.")
+ (license license:expat)))
--
2.46.0
next prev parent reply other threads:[~2024-11-01 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 10:31 [bug#74057] [PATCH] gnu: Add python-green Wiktor Żelazny
2024-11-01 1:35 ` [bug#74057] QA for 74057 get-state
2024-11-01 1:27 ` get-state
2024-11-01 1:35 ` get-state [this message]
2024-11-01 13:58 ` [bug#74057] [PATCH v2 1/1] gnu: Add python-green Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb85e245bccdcb3b2a66beb454d3abc716cbd6e3.1730424294.git.mazin@getstate.dev \
--to=mazin@getstate.dev \
--cc=74057@debbugs.gnu.org \
--cc==guix-patches@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.org \
--cc=wz@freeshell.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).