| 16 Nov 2023 |
 dustee | :D | 09:28:51 |
| dustee | hmm how come poetry is not available in the shell, it looks like it should be there packages = [ pkgs.poetry ]; | 09:37:41 |
 K900 | It should be, yeah | 09:37:55 |
| dustee | also it seems to be building numpy repeatably every time i enter the shell | 09:39:02 |
| K900 | You're probably not letting it complete the build | 09:39:41 |
| dustee | well this is weird i was able to enter the shell twice but poetry wasnt available, but there is now an error at building contourpy, i didnt change anything in the flake.nix or pyproject.toml | 09:42:52 |
| dustee | i tried to add dotenv but poetry wasnt there | 09:43:09 |
| dustee | can i clear the cache or something? | 09:43:38 |
| K900 | You shouldn't have to | 09:47:48 |
| dustee | well i did the unthinkable, i restarted the machine. and it seemed to help some, the build progressed i got another setuptools error which i solved and was able to build into the shell and now have access to poetry | 09:58:42 |
| dustee | but 'poetry run python manage.py runserver 0.0.0.0:5600' errors with 'ImportError: libstdc++.so.6: cannot open shared object file: No such file or directory
' | 09:59:14 |
| dustee | i think i solved this one with adding "cppy" to build requirements for some package, but where do i put it now when the shell already built successfully? are there runtime requirements somewhere or something | 10:02:29 |
| K900 | In reply to @dustee:matrix.org
but 'poetry run python manage.py runserver 0.0.0.0:5600' errors with 'ImportError: libstdc++.so.6: cannot open shared object file: No such file or directory
' You don't need poetry run | 10:05:49 |
| K900 | You should just run python directly from the shell | 10:05:57 |
| dustee | ok that works, django is running | 10:10:51 |
| dustee | thanks so much for your help | 10:10:57 |
|  @qyliss:fairydust.space left the room. | 10:11:10 |
| 17 Nov 2023 |
 adisbladis | The behaviour of editable together with flakes is kinda terrible.. | 00:46:33 |
| adisbladis | This doesn't work:
poetry2nix.mkPoetryEnv {
projectDir = ./.;
editablePackageSources = {
my-app = ./src;
};
}
because my-app resolves to a store path
| 00:46:52 |
| adisbladis | So it has to be used with --impure | 00:47:20 |
 @petrichor:envs.net | I don't know, it kind of makes sense to me that this use-case requires --impure: there's no reproducibility if you can edit one of the dependencies at any time and have those edits reflected immediately in the environment | 10:52:19 |
| @petrichor:envs.net | It would be nice to be able to flip the default though, and declare directly in a flake.nix that some actions should be considered impure by default (with a warning message printed | 10:53:03 |
| @petrichor:envs.net | * It would be nice to be able to flip the default though, and declare directly in a flake.nix that some actions should be considered impure by default (with a warning message printed) | 10:53:05 |
| adisbladis | I was considering making it relative to an environment variable | 11:23:42 |
| adisbladis | So you can use something like https://github.com/srid/flake-root | 11:24:24 |
| 18 Nov 2023 |
 cpcloud | Seems like the nixpkgs catch_conflicts.py script is now broken for Python 3.9 | 11:24:21 |
| cpcloud | Ah, fixed in https://github.com/NixOS/nixpkgs/pull/267669 | 11:38:06 |
| 19 Nov 2023 |
|  pbsds changed their display name from pbsds to pbsds (federation borken, may not see reply). | 03:35:23 |
| adisbladis | In reply to @adis:blad.is
The behaviour of editable together with flakes is kinda terrible.. I think the really hard part about editable installs with flakes is that it doesn't fail in a predictable way.
Maybe I should check for if a path is a nix store path when doing editable and fail on that, since it's clearly not the desired behaviour. | 06:28:11 |
|  ZXGU joined the room. | 11:01:29 |
