From: Maxime Devos <maximedevos@telenet.be>
To: "(unmatched-parenthesis" <paren@disroot.org>, 53445@debbugs.gnu.org
Subject: [bug#53445] [PATCH 2/3] gnu: Add python2-i3ipc
Date: Sat, 22 Jan 2022 15:30:09 +0100 [thread overview]
Message-ID: <88b8764fafd047f5e27bde554728619e7ba361a7.camel@telenet.be> (raw)
In-Reply-To: <20220122114722.21774-2-paren@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
(unmatched-parenthesis via Guix-patches via schreef op za 22-01-2022 om
11:47 [+0000]:
> * gnu/packages/wm.scm(python2-i3ipc): New variable.
> ---
> gnu/packages/wm.scm | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/gnu/packages/wm.scm b/gnu/packages/wm.scm
> index 975247bf07..c791bcf44e 100644
> --- a/gnu/packages/wm.scm
> +++ b/gnu/packages/wm.scm
> @@ -561,6 +561,9 @@ (define-public python-i3ipc
> (synopsis "An improved Python library to control i3wm and sway")
> (description "This package provides an improved Python library to control i3wm and sway.")
> (license license:bsd-3)))
> +
> +(define-public python2-i3ipc
> + (package-with-python2 python-i3ipc))
Python 2 has reached EOL since two years, can we avoid introducing new
python2 packages? See, e.g.,
<https://mail.gnu.org/archive/html/guix-devel/2018-12/msg00545.html>.
Greetings,
Maxme.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-22 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 11:47 [bug#53444] [PATCH 1/3] gnu: Add python-i3ipc (unmatched-parenthesis via Guix-patches via
2022-01-22 11:47 ` [bug#53445] [PATCH 2/3] gnu: Add python2-i3ipc (unmatched-parenthesis via Guix-patches via
2022-01-22 14:30 ` Maxime Devos [this message]
2022-01-24 14:32 ` bug#53445: " zimoun
2022-01-22 11:47 ` [bug#53444] [PATCH 3/3] gnu: Add i3-autotiling (unmatched-parenthesis via Guix-patches via
2022-09-25 20:26 ` bug#53444: [PATCH 1/3] gnu: Add python-i3ipc Björn Höfling
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=88b8764fafd047f5e27bde554728619e7ba361a7.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53445@debbugs.gnu.org \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.