--
You received this message because you are subscribed to the Google Groups "h5py" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h5py+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/h5py/33fc7022-eaff-432c-8103-30a799cf3a72%40googlegroups.com.
Hi,Since there isn't a top-level `hdf5plugin` directory in the wheel, I'm having problems getting everything to work under bazel.inflating: hdf5plugin-2.0.0b0.data/platlib/hdf5plugin/test.py
inflating: hdf5plugin-2.0.0b0.data/platlib/hdf5plugin/__init__.py
inflating: hdf5plugin-2.0.0b0.data/platlib/hdf5plugin/_version.py
inflating: hdf5plugin-2.0.0b0.data/platlib/hdf5plugin/plugins/libh5bshuf.so
inflating: hdf5plugin-2.0.0b0.data/platlib/hdf5plugin/plugins/libh5lz4.so
inflating: hdf5plugin-2.0.0b0.data/platlib/hdf5plugin/plugins/libh5blosc.so
inflating: hdf5plugin-2.0.0b0.dist-info/RECORD
inflating: hdf5plugin-2.0.0b0.dist-info/METADATA
inflating: hdf5plugin-2.0.0b0.dist-info/WHEEL
inflating: hdf5plugin-2.0.0b0.dist-info/top_level.txtWhat's the reason for not having a top-level hdf5plugin directory? How does python find the right place to import the package from?If I manually edit my sys.path entry for hdf5plugin to include `+ '/hdf5plugin-2.0.0b0.data/platlib'` then it seems to work, but that's too hacky to check in to my work repo.Thanks,Eli
On Mon, Oct 21, 2019 at 4:43 AM Thomas Vincent <thomas...@esrf.fr> wrote:
--Dear all,We've just released hdf5plugin v2.0.0 (https://github.com/silx-kit/hdf5plugin), that provides a generic way to enable blosc, bitshuffle and lz4 compression filters for h5py.It's available on pypi: https://pypi.org/project/hdf5plugin/Changelog since previous release:
- Added compression support for Linux and macOS
- Added blosc filter
- Added helper class (Blosc, Bitshuffle and LZ4) to ease providing compression arguments to h5py
- Added tests
- Updated documentation
- Building from source through setup.py
- No longer use the plugin mechanism via HDF5_PLUGIN_PATH environment variable
Best,Thomas
You received this message because you are subscribed to the Google Groups "h5py" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h5...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to h5py+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/h5py/08a47328-8079-4e03-9f0b-38a513d6d990%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/h5py/CAOvn4qh%3DSrvmDP3wP8Q17aogCtExr0ctgnh74yHhheh%2BeMriSg%40mail.gmail.com.
Sigh, I'm not surprised that Bazel isn't interacting with wheels properly. It's pretty apparent that the people who wrote the python support modules weren't familiar with the python ecosystem (a lot of NIH syndrome, not supporting virtualenvs, leaking system packages into what's supposed to be a hermetic build system, not knowing that unzipping a wheel isn't the same as installing it, etc.).To more directly answer the question: Bazel takes over the construction of the environment that it's build/run targets operate in, and that includes unzipping wheels and putting the resulting directories on the PYTHONPATH. There is no virtualenv to install the packages into, since the python that gets invoked is just the underlying system python. I suspect that the moment we need a wheel that actually needs to compile something during installation, we'll be stuck.In any case, thank you for looking into this. I appreciate your spending time on it, when it's clear that Bazel is at fault. Having looked at and made local tweaks to Bazel for other issues, I don't see a clean way to fix this without a major overhaul to how Bazel builds python environments (but I'm far from a guru, so maybe I'm missing something).Cheers,Eli
On Tue, Nov 5, 2019 at 9:37 AM Thomas Kluyver <tak...@gmail.com> wrote:
Just to highlight: the wheel format, unlike eggs, is not meant to support importing from the package directly without installing it. It happens to work in many cases, but it's not something you should rely on in general:
To view this discussion on the web visit https://groups.google.com/d/msgid/h5py/08a47328-8079-4e03-9f0b-38a513d6d990%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "h5py" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h5...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/h5py/CAOvn4qh%3DSrvmDP3wP8Q17aogCtExr0ctgnh74yHhheh%2BeMriSg%40mail.gmail.com.
I suspect that the moment we need a wheel that actually needs to compile something during installation, we'll be stuck.