From: Phil Beadling <phil@beadling.co.uk>
To: help-guix <help-guix@gnu.org>
Subject: python-pyarrow broken for parquet?
Date: Wed, 30 Jun 2021 19:35:21 +0100 [thread overview]
Message-ID: <CAOvsyQvEZHuDoaTnjWt8xDfOn2=2bd=XaLhKBGViv1JVeg3w=g@mail.gmail.com> (raw)
Hi all,
When trying to use the parquet module in pyarrow - it's not finding the
internal module. This is true for latest 4.0.1 and also the previous
version (shown below).
This is despite the fact that in the underlying apache-arrow package
parquet support is explicitly turned on as far as I can see:
https://github.com/guix-mirror/guix/blob/5ed105a8bb1a812975496dc3a091596355a0234c/gnu/packages/databases.scm#L3687
#:configure-flags
(list "-DARROW_PYTHON=ON"
"-DARROW_GLOG=ON"
;; Parquet options
"-DARROW_PARQUET=ON"
"-DPARQUET_BUILD_EXECUTABLES=ON".....
Any ideas how to resolve?
Thanks,
Phil.
$ guix environment --ad-hoc python python-pyarrow
The following derivation will be built:
/gnu/store/jvc3sbqs2nssr8gdvvyd0hgf5z80ra5b-profile.drv
building CA certificate bundle...
listing Emacs sub-directories...
building fonts directory...
building directory of Info manuals...
building database for manual pages...
building profile with 2 packages...
$ python3
Python 3.8.2 (default, Jan 1 1970, 00:00:01)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
*>>> import pyarrow.parquet*
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File
"/gnu/store/53issxa0jw7l2wb7xbhp1jp5j7a91dd9-profile/lib/python3.8/site-packages/pyarrow/parquet.py",
line 33, in <module>
import pyarrow._parquet as _parquet
*ModuleNotFoundError: No module named 'pyarrow._parquet'*
>>>
next reply other threads:[~2021-06-30 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 18:35 Phil Beadling [this message]
2021-07-02 11:01 ` python-pyarrow broken for parquet? zimoun
2021-07-02 15:34 ` phil
2021-07-05 12:13 ` Phil Beadling
2021-07-05 12:15 ` Phil Beadling
2021-07-28 18:10 ` Ricardo Wurmus
2021-07-28 20:37 ` Phil
2021-08-17 12:29 ` zimoun
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='CAOvsyQvEZHuDoaTnjWt8xDfOn2=2bd=XaLhKBGViv1JVeg3w=g@mail.gmail.com' \
--to=phil@beadling.co.uk \
--cc=help-guix@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.
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).