You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry to keep on opening issues! Is there any way to check whether an IndexedBzip2File has had block offsets calculated yet or not? If it takes 8 hours to calculate them for my huge file, it's worth checking before running e.g. a seek(), and outputting a warning that this might take some time.
The text was updated successfully, but these errors were encountered:
:) I'm glad someone uses it and cares enough to give feedback. Initially, this project only started to keep the required C++ bz2 code base for ratarmount separate from the python-only tar mount script. That's why the indexed_bzip2 interface is still fairly limited.
Thanks. Incidentally, your code has sped up my workflow so that running my script (to parse Wikidata/Wikipedia files for https://www.onezoom.org) now takes under an hour with 64 processes, whereas it used to take 2 days. That's a huge difference, and makes my life so much easier. So I'm very grateful!
Sorry to keep on opening issues! Is there any way to check whether an IndexedBzip2File has had block offsets calculated yet or not? If it takes 8 hours to calculate them for my huge file, it's worth checking before running e.g. a
seek()
, and outputting a warning that this might take some time.The text was updated successfully, but these errors were encountered: