| 8 Jan 2025 |
 laurynasp | Thanks - I will try it out tomorrow | 02:28:46 |
 @hexa:lossy.network | cuda cache? https://nix-community.org/cache/ | 14:08:27 |
 @qbit:tapenet.org | isn't there a buildPythonPackage like thing that's exposed from in buildHomeASsistantComponent (or some other HA .. entry point..)? | 20:53:55 |
| @qbit:tapenet.org | getting: ```
The Python derivation 'python3.13-firstof9/openevse-2.1.45' depends on a Python derivation
named 'python3.12-python-openevse-http-0.1.61', but the two derivations use different versions
of Python:
'python3.13-firstof9/openevse-2.1.45' uses /nix/store/acxvfb890g9jawlxsj7zs8marxxvzrrs-python3-3.13.1
'python3.12-python-openevse-http-0.1.61' uses /nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8
| 20:54:23 |
| @qbit:tapenet.org | * getting:
The Python derivation 'python3.13-firstof9/openevse-2.1.45' depends on a Python derivation
named 'python3.12-python-openevse-http-0.1.61', but the two derivations use different versions
of Python:
'python3.13-firstof9/openevse-2.1.45' uses /nix/store/acxvfb890g9jawlxsj7zs8marxxvzrrs-python3-3.13.1
'python3.12-python-openevse-http-0.1.61' uses /nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8
| 20:54:35 |
| @hexa:lossy.network | heh | 20:54:57 |
| @hexa:lossy.network | is that something you have downstream? | 20:55:27 |
| @hexa:lossy.network | use home-assistant.python | 20:55:39 |
| @qbit:tapenet.org | ya: https://github.com/qbit/xin/blob/main/pkgs/openevse.nix | 20:55:45 |
| @qbit:tapenet.org | swoot, ty | 20:59:52 |
| @qbit:tapenet.org | Jan 08 14:05:05 pwntie xin-ci-start[1947828]: error: future-1.0.0 not supported for interpreter python3.13 | 21:06:06 |
| * @qbit:tapenet.org cries python tears | 21:06:11 |
| @hexa:lossy.network | it is not 😄 | 21:07:09 |
| @hexa:lossy.network | man | 21:07:12 |
| @hexa:lossy.network | future is a python2 compat thing | 21:07:16 |
| 9 Jan 2025 |
 Sandro 🐧 | Fyi https://github.com/NixOS/nixpkgs/issues/372194 | 06:00:36 |
| @hexa:lossy.network | we're on 3.13 already | 12:02:04 |
 @rick:matrix.ciphernetics.nl | Also the channel advanced today so home assistant 2025.1.1 is available in nixos-unstable 🥳 | 13:04:04 |
| Sandro 🐧 | In reply to @hexa:lossy.network
we're on 3.13 already But only recently | 13:10:14 |
| @hexa:lossy.network | but four days ahead of this issue | 13:10:41 |
| @hexa:lossy.network | actually more like a week | 13:11:03 |
| @hexa:lossy.network | couldn't happen before home-assistant adopted pydantic>=2.0 | 13:11:40 |
| @hexa:lossy.network | which happend in 2025.1.0 | 13:11:44 |
| @qbit:tapenet.org | seems this is coming from the icloud component | 14:18:11 |
| @qbit:tapenet.org | … while calling the 'addErrorContext' builtin
at /nix/store/hbkwsrx232yhi5n7s7pvl40hcaha64vk-source/pkgs/development/interpreters/python/python-packages-base.nix:91:33:
90| pythonPath = [ ]; # Deprecated, for compatibility.
91| requiredPythonModules = builtins.addErrorContext "while calculating requiredPythonModules for ${drv.name or drv.pname}:" (
| ^
92| requiredPythonModules drv.propagatedBuildInputs
… while calculating requiredPythonModules for python3.13-pyicloud-1.0.0:
| 14:19:03 |
| @qbit:tapenet.org | qbit@europa[0]:~/src/nixpkgs(master)% git describe
24.11-pre-105574-g3bc03725b89f
qbit@europa[0]:~/src/nixpkgs(master)% nix build .#python313Packages.pyicloud
error:
… while evaluating the attribute 'drvPath'
at /nix/store/3yrq2rssqls4mgra67i9ja5wfzh2vkqn-source/lib/customisation.nix:416:7:
415| // {
416| drvPath =
| ^
417| assert condition;
… while evaluating the attribute 'drvPath'
at /nix/store/3yrq2rssqls4mgra67i9ja5wfzh2vkqn-source/lib/customisation.nix:416:7:
415| // {
416| drvPath =
| ^
417| assert condition;
… while evaluating 'strict' to select 'drvPath' on it
at /builtin/derivation.nix:1:552:
(stack trace truncated; use '--show-trace' to show the full trace)
error: future-1.0.0 not supported for interpreter python3.13
qbit@europa[1]:~/src/nixpkgs(master)%
| 14:21:30 |
| @hexa:lossy.network | future can most likely be stripped out | 14:30:30 |
| @qbit:tapenet.org | ok, if python3Packages.pyicloud builds without futures is it safe to assume it's completely removable? (seems like it would) | 14:33:34 |
| @hexa:lossy.network | most likely | 14:34:31 |
| @hexa:lossy.network | but needs work | 14:34:33 |
