From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Leo Famulari <leo@famulari.name>
Cc: 44275@debbugs.gnu.org
Subject: [bug#44275] [PATCH] gnu: Add python-pydub.
Date: Thu, 29 Oct 2020 15:39:08 +0100 [thread overview]
Message-ID: <20201029143908.ay6nvhik5brjws7g@rafflesia> (raw)
In-Reply-To: <20201029141427.GB8956@jasmine.lan>
Le 10/29, Leo Famulari a écrit :
> On Thu, Oct 29, 2020 at 09:26:57AM +0100, Tanguy Le Carrour wrote:
> > […]
> > > It would be good if store references to these programs could be "baked in" to
> > > the pydub code, rather than propagated. Can you take a look at how they
> > > are called and see if that is feasible? Often there is only one location
> > > that must be patched.
> > […]
> > `python-scipy` is a different problem, though. This module is not listed
> > as a requirement, but… it's required at run time. Event if I don't see the
> > point of having SciPy loaded when you want to manipulate audio. But that's
> > a different matter!
>
> Okay, I will take a look at the scipy thing today.
Great, thanks!
If it was up to me, I would remove altogether everything that is
related to `scipy`, meaning the `pydub/scipy_effects.py` file. But it
wouldn't be the same software any more, would it? ^_^'
Regards,
--
Tanguy
next prev parent reply other threads:[~2020-10-29 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 8:56 [bug#44275] [PATCH] gnu: Add python-pydub Tanguy Le Carrour
2020-10-28 16:34 ` Leo Famulari
2020-10-29 8:26 ` Tanguy Le Carrour
2020-10-29 14:14 ` Leo Famulari
2020-10-29 14:39 ` Tanguy Le Carrour [this message]
2020-10-29 21:50 ` Leo Famulari
2020-10-30 9:19 ` Tanguy Le Carrour
2020-10-30 20:42 ` Leo Famulari
2020-10-29 9:09 ` [bug#44275] [PATCH v2] " Tanguy Le Carrour
2020-10-30 20:40 ` bug#44275: " Leo Famulari
2020-10-30 21:10 ` [bug#44275] " Tanguy LE CARROUR
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=20201029143908.ay6nvhik5brjws7g@rafflesia \
--to=tanguy@bioneland.org \
--cc=44275@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).