| 26 Mar 2024 |
 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 |
| K900 | I haven't looked closely at the lockfile format | 20:29:37 |
| nim65s | from astral, nice ! | 21:12:43 |
