lance.Dataset has no way to get the commit timestamp of the version it is holding

Open a dataset at any version and nothing tells you when that version was committed:

ds = lance.dataset(uri, version=n)
ds.version        # the int
                  # ...and no way to the timestamp

The value isn't missing, it's discarded. Dataset::version() builds
Version { version, timestamp, metadata } from the manifest that's already in memory -
no IO - and the binding keeps one field:

fn version(&self) -> PyResult<u64> {
    Ok(self.ds.version().version)
}

metadata (the manifest summary: total_rows, total_fragments, total_files_size) goes the
same way.

The only thing in pylance that surfaces a timestamp at all is versions(), which lists and
reads every manifest in the table's history on every call, so you can filter down to the one
you were already holding. It also carries a // TODO: this API should support pagination.

The same field is dropped for other versions: read_version_transaction(v) returns
{version, timestamp, transaction}, but only the wrapper below it is bound:

pub async fn read_transaction_by_version(&self, version: u64) -> Result<Option<Transaction>> {
    Ok(self.read_version_transaction(version).await?.transaction)
}

and reading the transaction already read that version's manifest.

Would exposing both be reasonable?

Read Dataset::version() and the Python binding fn version() first; compare them with read_version_transaction(v) and versions() to trace the already-loaded timestamp and metadata. Done means the held version exposes its commit timestamp and manifest metadata without rereading table history, with the corresponding binding API available.