Opened at 2020-07-08T14:47:39Z
Closed at 2020-07-08T18:56:42Z
#3338 closed task (fixed)
Disable nix build until transition to Python 3 is done
| Reported by: | itamarst | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | unknown | Version: | n/a |
| Keywords: | review | Cc: | |
| Launchpad Bug: |
Description
nixpkgs typically only has a single version of Python packages.
Newer versions won't support Python 2, for example the txaio in today's version doesn't support Python 2 (as packaged, anyway).
Older snapshots aren't always going to include what we want, e.g. future 0.18.2 isn't available in 19.09 snapshot.
So in order to use nix, tahoe-lafs would have to maintain its own package snapshot. This seems like more work than it's worth, so I suggest disabling nix until the Python 3 port is done. At that point nixpkgs' "only include the latest package" approach becomes feasible again.
Change History (4)
comment:1 follow-up: ↓ 2 Changed at 2020-07-08T14:50:42Z by itamarst
comment:2 in reply to: ↑ 1 Changed at 2020-07-08T14:52:10Z by exarkun
Replying to itamarst:
Counter-argument: Jean-Paul tells me large proportion of Tahoe-LAFS devs use Nix.
Just to make sure this is completely clear, *I* use Nix and this makes a large proportion since there are so few Tahoe-LAFS developers. :)
comment:3 Changed at 2020-07-08T17:23:43Z by exarkun
- Keywords review added
comment:4 Changed at 2020-07-08T18:56:42Z by exarkun
- Resolution set to fixed
- Status changed from new to closed
Merged in https://github.com/tahoe-lafs/tahoe-lafs/commit/834c7b4d062763b4702473e82b86b1d203fcba18 - not sure why the automation didn't kick in :/ I did get slightly creative with my message, I guess. :(
Counter-argument: Jean-Paul tells me large proportion of Tahoe-LAFS devs use Nix.