Migrate py37 programs to py3 #103742
Migrate py37 programs to py3 #103742
Conversation
@@ -937,7 +937,7 @@ in | |||
|
|||
iamy = callPackage ../tools/admin/iamy { }; | |||
|
|||
azure-cli = callPackage ../tools/admin/azure-cli { python = python37; }; | |||
azure-cli = callPackage ../tools/admin/azure-cli { python = python3; }; |
SuperSandro2000
Nov 23, 2020
Member
Using python3 in the package is probably more straight forward.
Using python3 in the package is probably more straight forward.
When trying to build this with nixpkgs-review I get several thousands rebuilds. Not sure what went wrong here. |
@SuperSandro2000 azure-cli has its own package set.. maybe redundant with other azure-* packages by the way @jonringer Do you know why there is a special python-package set ? |
because the azure-cli lags 1-6 weeks behind most of the python azure sdk, or sometimes uses pre-releases for certain packages. azure-cli would essentially be unusable without it. |
azure-cli was kept at python37 originally because aiohttp didn't support it for the longest time |
ok good to know |
Result of 4 packages failed to build:
manim download over 3000 tex packages. Not trying this one. Other are currently building manually to get some logs. Edit: rebuild everything except mannim and it worked. |
abfbb84
into
NixOS:master
Motivation for this change
Some programs in nixpkgs were using explicitly python37, and they also work with latest branch, so here are some "migrations" that seem correct.
I started the binaries they look ok
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)