| 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 |
