| 7 Nov 2023 |
 @fractivore:cyberia.club | Should I contribute it to nixpkgs or something? poetry2nix said something about pushing changes upstream | 20:52:49 |
| @fractivore:cyberia.club | I'm pretty new to making open source contributions | 20:52:57 |
 K900 | You should contribute the overrides that worked for you | 20:54:51 |
| K900 | But putting the whole thing into nixpkgs will require a different build process | 20:55:03 |
| K900 | The current policy with Python packages in nixpkgs is to not use tools like poetry2nix, but use nixpkgs packages directly | 20:55:32 |
| @fractivore:cyberia.club | Oh, okay, I guess I'll just pull the build-systems.json file where it says to put the overrides in the edgecases.md file | 20:57:15 |
| 8 Nov 2023 |
 adisbladis | In reply to @k900:0upti.me
The current policy with Python packages in nixpkgs is to not use tools like poetry2nix, but use nixpkgs packages directly I always found it funny how that is very strict but with languages like Rust and Go we're basically "yolo" | 02:34:49 |
 @reckenrode:matrix.org | Redacted or Malformed Event | 03:04:08 |
| adisbladis | I'm thinking about an alternative to preferWheel/preferWheels that's less opaque.
I think it's currently a bit hard to understand when/why it's not providing you with wheels https://github.com/nix-community/poetry2nix/issues/1403#issuecomment-1797861008 | 09:01:39 |
| adisbladis | Maybe preferWheel (the singular option) should be removed in favour of a requireWheel or similar that hard-fails when it can't be selected | 09:02:16 |
| adisbladis | The hard-fail could provide an error message that explains common failure modes, and maybe dump some platform information so you can understand what's going on | 09:03:01 |
|  @ryoschin:matrix.org joined the room. | 12:18:01 |
| @ryoschin:matrix.org | In reply to @k900:0upti.me
The current policy with Python packages in nixpkgs is to not use tools like poetry2nix, but use nixpkgs packages directly Yay... | 12:19:10 |
| K900 | Are you packaging your thing for nixpkgs? | 12:19:27 |
| K900 | Or for personal use? | 12:19:32 |
| K900 | If you're building it with the intention of upstreaming into nixpkgs, you'll need to package your missing dependencies and your thing using nixpkgs tooling | 12:20:01 |
| @ryoschin:matrix.org | Oh, personal use | 12:20:42 |
| K900 | Then you can use poetry2nix | 12:21:06 |
| @ryoschin:matrix.org | In reply to @ryoschin:matrix.org
Yay... I apologize for this one, I didn't dig deep enough into your conversation | 12:21:25 |
| @ryoschin:matrix.org | In reply to @k900:0upti.me
Then you can use poetry2nix Should I then paste my previous question here, or? | 12:22:09 |
| K900 | Just use the example flake in the poetry2nix repo | 12:22:25 |
| @ryoschin:matrix.org | Using the flake section is too small for me to spot it.. I swear I thought there was only the shell example! Sorry for wasting your time | 12:23:56 |
| @ryoschin:matrix.org | Is there a way to automatically call poetry shell? It seems like MyPy cannot automatically detect packages downloaded via poetry, however when used in poetry shell, it works. | 14:51:51 |
| @ryoschin:matrix.org | * Is there a way to automatically call poetry shell? It seems like MyPy cannot automatically detect packages downloaded via poetry, however when used in poetry shell, it can. | 14:52:03 |
| @ryoschin:matrix.org | * Is there a way to automatically call poetry shell? It seems like MyPy cannot automatically detect packages downloaded via poetry, however when installed with poetry add mypy and used in poetry shell, it can. | 14:54:22 |
| K900 | You should not be installing stuff through poetry at all | 14:56:40 |
| K900 | You should just use the Nix shell | 14:56:44 |
| K900 | And mypy should respect PYTHONPATH from that | 14:56:49 |
| @ryoschin:matrix.org | O-oh... So, I do not use pyproject.toml to specify the dependencies, and instead use flake.nix to specify the python311Packages.package? | 14:59:00 |
| K900 | No | 14:59:26 |
