From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Profanity Python dependency version uplift
Date: Mon, 04 May 2020 19:44:13 +0200 [thread overview]
Message-ID: <20200504174413.dH-5WxXU63ZY5Oj5l0EgaawjjNeMbTSw6Q_sgVxTwUU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21587@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/issues/21587#issuecomment-623606505
Comment:
> Apart from Python2 is EoL and it would be the only application on my PC requiring it, just personal preference. However, from [https://profanity-im.github.io/plugins.html](url) it confirms the Profanity can be complied with Python 2 or 3 and the plugins should run with either.
If you are using plugins and can confirm that it is working with python 3, then I have no objections. As mentioned, we could also consider disabling python by default if people aren't using the functionality (and still merge the v3 support).
> It would be very useful to have the OMEMO support.
It's by default built, and doesn't depend on python. I'd actually ask again if anyone is using it (I'd think OTR is more popular), and otherwise disable it by default.
> One question, for my curiosity, why is gtk mentioned on a CLI application?
Seems to be a dependency to the tray functionality [1], but I'd be all for disabling this by default.
[1] https://profanity-im.github.io/guide/latest/reference.html#tray
next prev parent reply other threads:[~2020-05-04 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 16:45 [ISSUE] " ErinVoid
2020-05-04 13:27 ` sgn
2020-05-04 13:29 ` sgn
2020-05-04 13:35 ` sgn
2020-05-04 13:54 ` ailiop-git
2020-05-04 17:23 ` ErinVoid
2020-05-04 17:44 ` ailiop-git [this message]
2020-05-04 23:07 ` sgn
2020-05-05 8:06 ` teldra
2020-05-05 8:33 ` ErinVoid
2020-05-05 16:39 ` [ISSUE] [CLOSED] " sgn
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=20200504174413.dH-5WxXU63ZY5Oj5l0EgaawjjNeMbTSw6Q_sgVxTwUU@z \
--to=ailiop-git@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).