ledger-autosync: fix build with Python 3.12 and don't propagate ledger and hledger

[dotlambda]

Description of changes

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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

[emilazy]

What do we need 3.11 for here? Upstream doesn’t actually mention nose at all, so I was hoping we could keep this running on 3.12 and move it over to pytestCheckHook.

[dotlambda]

What do we need 3.11 for here?

for imp: https://github.com/egh/ledger-autosync/blob/v1.0.3/ledgerautosync/cli.py#L24

[dotlambda]

Upstream doesn’t actually mention nose at all

True. I dropped the nose dependency.

[emilazy]

Sorry, should have read more closely…

Seems reasonable (albeit unfortunate) to me, but since upstream uses pytest, can we at least drop the nose use here?

Edit: Ah, you’re ahead of me!

[dotlambda]

The alternative to using python311Packages would be applying egh/ledger-autosync@b7a2a18 and egh/ledger-autosync@453d92a.

[emilazy]

Perhaps we should just bump to the current Git HEAD. The conversion to pytest was actually after the latest release, and upstream was planning on cutting a release in July. That hasn’t yet happened, but there’s been a lot of clean‐up and fixes since, so if upstream thought it was ready for release I say we should just bump.

(I was looking at these packages a while ago but paged out most of the memories…)

[DamienCassou]

Perhaps we should just bump to the current Git HEAD

I think this makes sense given the state of the project. I'm fine merging the PR as it is though.

What do you say @dotlambda?

[dotlambda]

Let's give upstream a little more time to cut a release before we use the git HEAD.

[DamienCassou]

Changes are great, thank you for your work. I'm fine merging that or waiting for upstream to release or using git HEAD.