From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-gmpy2: restore package
Date: Tue, 12 Oct 2021 21:32:49 +0200 [thread overview]
Message-ID: <20211012193249.V-H0rdQlr3ZaEoK8_LWnBydkW7IQsUpGW7cPsPOhh0A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33481@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/33481#issuecomment-941356325
Comment:
> I think the commit should be "remove python3-gmpy2" instead and the commit body should mention the package has been restored. Makes it clearer IMO.
Done.
> Since ahesford was on the fence, I think `mpmath` should depend on `gmpy2`. It's a very reasonable default, and most people installing `mpmath` will have a huge python suite of scientific computing stuff already installed, so the size difference should be negible.
Should we also make it depend on python3-matplotlib, as that enables plotting, as in
```
>>> from mpmath import *
>>> plot([cos,sin],[-4,4])
```
Note installing python3-matplotlib also improves plotting in sympy.
I almost miss the "recommends" and "suggests" entries in debian packages.
next prev parent reply other threads:[~2021-10-12 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 15:29 [PR PATCH] " tornaria
2021-10-11 15:31 ` [PR PATCH] [Updated] " tornaria
2021-10-11 15:52 ` ahesford
2021-10-11 15:57 ` [PR PATCH] [Updated] " tornaria
2021-10-11 16:01 ` tornaria
2021-10-11 18:43 ` tornaria
2021-10-11 21:00 ` [PR PATCH] [Updated] " tornaria
2021-10-12 18:57 ` ericonr
2021-10-12 19:19 ` [PR PATCH] [Updated] " tornaria
2021-10-12 19:32 ` tornaria [this message]
2021-10-12 19:52 ` ericonr
2021-10-12 20:11 ` tornaria
2021-10-13 18:38 ` [PR PATCH] [Closed]: " ahesford
2021-10-13 18:39 ` ahesford
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=20211012193249.V-H0rdQlr3ZaEoK8_LWnBydkW7IQsUpGW7cPsPOhh0A@z \
--to=tornaria@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).