Jayce Slesar

@kevinjqliu what do you think about something like this... ```py from unittest.mock import MagicMock import pytest from pyiceberg.catalog import Catalog from tests.conftest import BUCKET_NAME HIVE_CATALOG_NAME = "hive" HIVE_METASTORE_FAKE_URL = "thrift://unknown:9083"...

Would like to get all the open catalog PR's merged in if possible!!!! A lot of view stuff is open, rest stuff, ideally also supporting pagination/laziness changes in favor of...

Could define a `BaseVersion` class or something that downstream classes could inherit from in order to dish out versions of functions as expected/store constants? Might be too much to start...

Some loose ideas in terms of any rust integration: Fancy CI work to enable testing python bindings from the rust repo directly against tests from this one (when/where it makes...

> a meta question, wydt of moving the orphan file function to its own file/namespace, similar to how to use `.inspect`. > > i like the idea of having all...

@Fokko we probably also want pyiceberg to have some idea about https://iceberg.apache.org/spec/#delete-formats right? Is it currently aware of those files?

> @jayceslesar I believe the merge-on-read delete files (positional deletes, equality deletes, and deletion vectors) are returned by the all-files. The only part that's missing is the partition statistics files....

Going to get around adding tests for both types of FileIO... @Fokko @kevinjqliu anything else you think we need here?

thank you!

Bonus idea: what if `make notebook` or some other CLI entry point spun up pyspark + catalog configured via pyiceberg.yaml so users could immediately start querying _their_ data?