| 24 Mar 2024 |
 latenighticecream | thank you ! I will need that :D | 15:31:39 |
| latenighticecream | Soo.. I'm kind of giving up. In the end I received the same LLVM library error as you showed before and am unable to get rid of it. drjit on its own works when built by hand, even with the sdf example you provided (mitsuba still produces the same error). But when I try to import sionna (the thing I actually need) said error appears. Unfortunately, it has already eaten way too much time without producing anything useful. But I learned a lot of nix on the way :)
So I'm now going back to the impure versions with pip + venvs inside a shell | 18:26:03 |
| latenighticecream | and thank you for your help nevertheless! | 18:28:02 |
| latenighticecream | * Soo.. I'm kind of giving up. In the end I received the same LLVM library error as you showed before and am unable to get rid of it. drjit on its own works when built by hand, even with the sdf example you provided (mitsuba still produces the same error). But when I try to import sionna (the thing I actually need) said error appears. Unfortunately, it already ate way too much time without producing anything useful. But I learned a lot of nix on the way :)
So I'm now going back to the impure versions with pip + venvs inside a shell | 18:33:07 |
| 26 Mar 2024 |
 nim65s | Hi there !
I have a question about https://github.com/nix-community/poetry2nix/blob/master/docs/edgecases.md#modulenotfounderror-no-module-named-packagename.
Why do we have to add eg. poetry-core in overrides/build-systems.json (or in a overridePythonAttrs / buildInputs) as dependency of a package which has [build-system] \n requires = ["poetry-core"] in its pyproject.toml ? Couldn't we autodetect that ? | 10:43:23 |
 K900 | Because we can't read pyproject.toml at eval time | 10:43:45 |
| K900 | Well, we can | 10:43:53 |
| K900 | But it would then mean we have to fetch the sources of the package at eval time | 10:44:04 |
| K900 | * But it would then mean we have to fetch the sources of the package at eval time | 10:44:07 |
| K900 | Which will slow down evaluation massively and is probably a bad idea | 10:44:16 |
| nim65s | ok, for now we only get metadata from pypi ? | 10:44:18 |
| K900 | We don't get metadata from anywhere | 10:44:58 |
| K900 | Except poetry2nix itself and nixpkgs | 10:45:02 |
| K900 | And the lock file | 10:45:09 |
| K900 | * And the lock file for your project | 10:45:13 |
| nim65s | oh, the required deps are found in the project currently being processed by poetry2nix, I see, it makes sense, thanks. | 10:46:43 |
| nim65s | But then, second question: as the author of one of the libs I'm using in one of my project (both are separate projects/git repos, in pure python, and packaged with poetry), can I provide a hint with the lib to avoid having to provide an override for it in the projects packaging ? | 10:48:51 |
| nim65s | maybe a [tool.poetry.group.poetry2nix.dependencies] poetry-core = "^1" or something similar ? | 10:49:49 |
| nim65s | Or should I simply add all my projects in overrides/build-systems.json ? | 10:50:46 |
| K900 | You can add your own overrides in your Nix expression | 10:51:22 |
| nim65s | This is what I did in a few projects to test poetry2nix, but it quickly adds up to a lot of copy-paste of the same 3 lines x number of libs in every project, which is not super nice to write, see, or maintain, so I was looking for another solution. | 10:55:54 |
| K900 | There is not really one currently | 10:56:40 |
| K900 | We could implement an optional, opt-in IFD mode | 10:56:54 |
| K900 | But that has to be optional and someone needs to actually do it | 10:57:10 |
| nim65s | ok, now everything is clear, thanks for your answers ! | 11:00:43 |
 @goodboy:matrix.org | anyone seen this new project yet? | 20:26:38 |
| @goodboy:matrix.org | https://github.com/astral-sh/uv | 20:26:40 |
| @goodboy:matrix.org | looks like it also has locking for deps | 20:27:23 |
| @goodboy:matrix.org | which i guess would make it possibly compat with nix? | 20:27:33 |
| K900 | In theory | 20:29:31 |
