| 22 Jan 2022 |
 adisbladis | Something that would be extremely welcome is to document these kind of things. | 08:39:15 |
 mou | I understand. Python ecosystem is such chaos (( Every tool which decides to fix all issues will be buried in routine and exceptions ( If i come up with solution for my case, i'll definitly contribute it back in form of documentation | 08:40:10 |
| adisbladis | <3 | 08:40:35 |
| adisbladis | For all it's minor issues I still think Poetry is by far the best thing to happen to Python in a very long time | 08:40:56 |
| mou | Indeed. I found poetry too late ) And was shocked about how long it already existed and i did not even heard of it. | 08:42:26 |
| mou | I did it. Look like now i'm a little closer to understanding of poetry2nix override layers) | 08:55:33 |
| mou | adisbladis: what do you think of creating a document like Troubleshooting with structure like Error message or log tail to match -> description of problem -> possible typical solution? Maybe it could reduce amount of similar questions asked | 08:57:35 |
| adisbladis | In reply to @mou_bugtracker:matrix.org
adisbladis: what do you think of creating a document like Troubleshooting with structure like Error message or log tail to match -> description of problem -> possible typical solution? Maybe it could reduce amount of similar questions asked I've been thinking about something similar. But I never get around to writing docs myself. | 08:58:07 |
| adisbladis | I think it'd be great! | 08:58:14 |
 K900 | Another random convenience idea I just got | 09:00:48 |
| K900 | Make it possible to override build-systems.json | 09:01:03 |
| K900 | Just to save on some typing | 09:01:08 |
| mou | I could try to write first version in upcoming days, hope community will help to fix language issues, because my english is more like pidgin and have many grammar issues. | 09:01:12 |
| K900 | Something like buildSystemOverrides = { aiosqlite = "flit" } | 09:01:42 |
| adisbladis | In reply to @mou_bugtracker:matrix.org
I could try to write first version in upcoming days, hope community will help to fix language issues, because my english is more like pidgin and have many grammar issues. Don't let that stop you :) I'm happy to nit on some English spelling. | 09:01:57 |
| K900 | Could potentially allow for better special case handling for weird build systems too | 09:02:21 |
| adisbladis | K900: That could easily be generalised, it doesn't have to be just build systems | 09:03:09 |
| adisbladis | I like the much higher level interface :) | 09:03:17 |
| K900 | Yeah but ideally you'd want to not have it at all | 09:03:26 |
| K900 | ¯\_(ツ)_/¯ | 09:03:29 |
| mou | I agree with adisbladis . The more poetry2nix will be used the more various exception will be found. Too many attributes will be added this way. Python ecosystem has too many legacy and surprises (( K900 Maybe what you suggested could be implemented with function over overrides.withDefaults . | 09:07:01 |
| adisbladis | In reply to @k900:0upti.me
Yeah but ideally you'd want to not have it at all We're always going to have overrides for native deps, so as long as the interface is generic I think it's a really nice addition | 09:07:15 |
| mou | something like
overrides = poetry2nix.buildSystemOverrides { aiosqlite = "flit" } | 09:08:23 |
| K900 | Mostly I just want to avoid it getting to a point where it's easier to add overrides than it is to fix things upstream | 09:09:14 |
| mou | but upstreams are python packages | 09:09:43 |
| mou | poetry for example. It's really difficult to propose changes to product used by hundred thousands | 09:10:36 |
| mou | PR mentioned above in poetry is still did not accepted ( | 09:11:24 |
| adisbladis | There is a very little documented interface that is' a lot better than withDefaults, namely poetry2nix.defaultPoetryOverrides.extend:
(poetry2nix.defaultPoetryOverrides.extend (self: super: {})).extend(self: super: {}) | 09:11:27 |
| adisbladis | It actually composes nicely | 09:12:37 |
| adisbladis | I'm thinking that might be a decent foundation | 09:12:48 |
