unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: 37705@debbugs.gnu.org
Subject: bug#37705: python-scikit-learn fails tests
Date: Fri, 11 Oct 2019 21:29:05 +0200	[thread overview]
Message-ID: <8736fzhyim.fsf@elephly.net> (raw)
In-Reply-To: <ea1e7eaa20741962db698209047a71349d9d1d53.camel@gmail.com>


Jesse Gibbons <jgibbons2357@gmail.com> writes:

> On Fri, 2019-10-11 at 10:42 -0600, Jesse Gibbons wrote:
>> I need python-scikit-learn for an ai project.
>>
>> "guix build python-scikit-learn"
>> ...
>> build of /gnu/store/wymxdfygbzij8hbz4gqkrwnb3jkicx76-python-scikit-learn-
>> 0.20.3.drv failed
>> View build log at '/var/log/guix/drvs/wy/mxdfygbzij8hbz4gqkrwnb3jkicx76-
>> python-scikit-learn-0.20.3.drv.bz2'.
>>
>>
>> log tarball attached.
>>
>> I'm working on fixing it, but help would be appreciated.
> update:
> python-scikit-learn is outdated. It can be updated to 0.20.4
> I am testing the build right now. I will send a patch if it builds.
>
> I think we can also discuss what to do about python-scikit-learn dropping
> python2 support beginning with 0.21; there is a thread on guix-devel titled
> "the upcoming Great Python2 Purge™" we can revive. I would hate for guix
> packages to fall too far behind.

What I’ve done in the past when upgrading the science packages beyond
the versions that support Python 2 is to make the Python 2 variant
independent and freeze at the old version.  As soon as there are no more
packages depending on these old versions they should be removed.


--
Ricardo

  reply	other threads:[~2019-10-11 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 16:42 bug#37705: python-scikit-learn fails tests Jesse Gibbons
2019-10-11 18:32 ` Jesse Gibbons
2019-10-11 19:29   ` Ricardo Wurmus [this message]
2019-10-11 19:27 ` bug#37433: " Ricardo Wurmus
2019-10-11 19:48   ` bug#37705: " Jesse Gibbons
2019-10-12 15:07     ` bug#37433: 37433 fixed Jesse Gibbons

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=8736fzhyim.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=37705@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    /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).