Closed franz101 closed 1 year ago
The discussion of the issue can be found here: https://github.com/vaexio/vaex/issues/2283
@JovanVeljanoski @maartenbreddels
This fixes the reading file error: https://colab.research.google.com/drive/1EG9898VtmO19FwfZKd_LJzqkz_YVWwlE?usp=sharing#scrollTo=S-T0Wjd3B_YU
Here is an example of the fix: https://colab.research.google.com/drive/1HNtACZhFteXlqrpFQR3wGtnPuropRx1j?usp=sharing
The reason is due to pkg_resources unable to find file openers without kernel restart: https://git.smhi.se/climix/climix/-/merge_requests/165/diffs
Ok, just to make it clear I understand.
importlib.metadata
which is fasterMan, I can't believe this is all so flakey, importlib_metadata==4.0
seems to work, 3.0 doesn't seem to have the groups argument.
Actually it is not about the speed here. In Google colab after a fresh installation without a restart, pkg_resources entrypoints are an empty list. Therefore it won't even try any openers and fail.
I agree can't believe how bad python handles lazy loads and has API changes across releases.
Many thanks for helping us sort out this mess! :)
its my first large open source project contribution. happy to contribute where I can. ❤️
Many thanks :)
This is a hot fix for the IO read issues caused by using the legacy pkg_resources.iter_entry_points
legacy
pkg_resources.iter_entry_points
is replaced withimportlib.metadata.entry_points