python312Packages.beancount3: init at 3.0.0

[alapshin]

Added package for beancount3
Update fava to version 1.30 which supports both beancount2 and beancount3.
Add package for beangulp as a replacement for beancount.ingest

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[SharzyL]

I am not using v3 currently. How is it working with existing tools now?

[alapshin]

I am not using v3 currently. How is it working with existing tools now?

I used v3 for the last 6 months, and it works ok for me. However, I don't use any custom importers based on beancount.ingest which is the main breaking change, and input my expenses by hand. Until recently, Fava didn't support v3, but now it does: beancount/fava#1831

Overall, I think it is in good enough shape for everyday use, but it depends on your setup.

[SharzyL]

It would be nice to have v3 in nixpkgs. But since there are major incompatibilities between v2 and v3, and v2 is still widely used, I would like to keep both v2 and v3 in nixpkgs, i.e. beancount and beancount3. Otherwise users may find their tools broken after an upgrade. When v2 is marked as deprecated, we can add warnings in nixpkgs and later replace beancount with beancount3.

[alapshin]

Ok, makes sense. I reworked PR: added separate package for beancount3 and support for building fava with either version. This way user can specify beancount = beancount3 via overlay and use it everywhere.

[SharzyL]

It is very cumbersome to override python3Packages to build fava with beancount3 due to the strange design in python3Packages. Can we just build fava with beancount3? May this cause compatibility issues?

[alapshin]

Would it help if, instead of accepting python3Packages, the package accepted beancount dependency directly? I think this wouldn't work since package uses buildPythonApplication

It is possible to build Fava either with v2 or v3, but as far as I understand depending on version used Fava uses different approach for importers under the hood

https://github.com/beancount/fava/blob/main/CHANGES

For importers, this sticks to beancount.ingest on v2 and used beangulp for v3.
Due to changes related to duplicate detection, duplicate detection is not
automatically done by Fava here but can still be manually specified as hooks.

Also, I'm not sure if it is a good idea to mix-match beancount version between different packages (fava, beanprice, beanquery, beangulp, etc.).