From: Pierre Langlois <pierre.langlois@gmx.com>
To: 41968@debbugs.gnu.org
Subject: [bug#41968] [PATCH 0/5] Update python-plotly and python-pandas
Date: Sat, 20 Jun 2020 20:22:50 +0200 [thread overview]
Message-ID: <87r1u9ha11.fsf@gmx.com> (raw)
Hi Guix!
Recently I wanted to use python-plotly and realized our package could do
with an update, but to do that I also had to update the python-pandas
package otherwise tests wouldn't pass.
So in the end I got 5 patches all together :-).
* gnu: deeptools: Deprecate in favor of python-deeptools.
deeptools and python-deeptools are the same package, I looked at
them since they depend on plotly. I thought I'd merge them as a
drive-by fix.
* gnu: python-pandas: Update to 1.0.5.
I also had to keep versions 0.25 for the python-biom-format package.
* gnu: Add python-retrying.
* gnu: Add python-xarray.
New dependencies.
* gnu: python-plotly: Update to 4.8.1.
I've also had to keep the version 2.4.1 around for the
python-deeptools package.
WDYT?
Thanks,
Pierre
next reply other threads:[~2020-06-20 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 18:22 Pierre Langlois [this message]
2020-06-20 18:28 ` [bug#41968] [PATCH 1/5] gnu: deeptools: Deprecate in favor of python-deeptools Pierre Langlois
2020-06-20 18:29 ` [bug#41968] [PATCH 2/5] gnu: python-pandas: Update to 1.0.5 Pierre Langlois
2020-06-20 18:30 ` [bug#41968] [PATCH 3/5] gnu: Add python-retrying Pierre Langlois
2020-06-20 18:30 ` [bug#41968] [PATCH 4/5] gnu: Add python-xarray Pierre Langlois
2020-06-20 18:31 ` [bug#41968] [PATCH 5/5] gnu: python-plotly: Update to 4.8.1 Pierre Langlois
[not found] ` <handler.41968.B.15926773811621.ack@debbugs.gnu.org>
2020-06-22 16:44 ` bug#41968: Acknowledgement ([PATCH 0/5] Update python-plotly and python-pandas) Pierre Langlois
2020-06-24 19:08 ` [bug#41968] " Marius Bakke
2020-06-26 3:20 ` Leo Famulari
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=87r1u9ha11.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=41968@debbugs.gnu.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 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).