beancount-exporter 3.0.0 caps beancount<3.0.0, blocking installs alongside Beancount 3.x #10

Hi! Thanks for maintaining this — bh format and the broader beanhub tooling have been really useful in my ledger setup.

I ran into a small dependency snag I wanted to flag, in case it's an oversight rather than intentional.

What I noticed

beancount-exporter==3.0.0 declares its Beancount dependency as beancount>=2.3.5, <3.0.0:

$ curl -s https://pypi.org/pypi/beancount-exporter/3.0.0/json | jq -r '.info.requires_dist[]'
beancount<3.0.0,>=2.3.5
beancount-data<4.0.0,>=3.0.0
click<9.0.0,>=8.0.4
pgcopy-standalone<2.0.0,>=1.6.0
orjson<4.0.0,>=3.9.10; extra == "pgcopy"

That <3.0.0 cap means beancount-exporter can't be installed alongside Beancount 3.x, which is now the active major series for most of the ecosystem (Fava, beangulp, beanquery, beanprice, redstreet's importers/plugins, etc.).

Where it bit me

beanhub-cli >= 3.1.0 picked up beancount-exporter>=3.0.0 as a direct dependency, which transitively makes beanhub-cli 3.1.x uninstallable on Beancount 3.x. The uv resolver spells it out:

beanhub-cli==3.1.1 → beancount-exporter>=3.0.0 → beancount<3.0.0,>=2.3.5

Concretely: I'm on beancount==3.2.2 and trying to upgrade beanhub-cli from 3.0.1 to 3.1.1. The workaround is staying on 3.0.1 (which doesn't pull in beancount-exporter at all), so I'm not blocked — just a bit stuck on the older release.

Possible directions

If beancount-exporter already works against Beancount 3 (the bits it touches — parsing, loading, options — haven't changed all that much), relaxing the cap to beancount>=2.3.5 (or <4.0.0) would do it.

If there's a real incompatibility behind the cap, it'd be helpful to know — a note in the README, or maybe a separate 3.x-compatible track, would let downstream packages like beanhub-cli target the right version on purpose.

Either way, thanks again for your work on this — happy to provide more details if anything's unclear.

Environment

• Python 3.14
• beancount==3.2.2
• Trying to install beanhub-cli==3.1.1 (transitively pulls beancount-exporter==3.0.0)