| 7 Nov 2023 |
 K900 | Oh | 20:37:47 |
| K900 | In pyproject.toml replace
[build-system]
requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning"]
build-backend = "poetry_dynamic_versioning.backend"
with
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
| 20:38:14 |
 @fractivore:cyberia.club | It's building! I collected garbage after I edited the pyproject.toml file, maybe I didn't really need to do that. I'm gonna munch some more pasta while it builds. | 20:44:52 |
| @fractivore:cyberia.club | yay it built! My first real derivation! 😄 | 20:51:07 |
| @fractivore:cyberia.club | Now what do I do lol | 20:51:18 |
| K900 | I dunno | 20:51:46 |
| K900 | Run it? | 20:51:49 |
| K900 | Whatever you were trying to do in the first place | 20:51:56 |
| @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 |
