IRC channel logs
2023-06-08.log
back to list of logs
<civodul>i mean, there are different kinds of kitchen sinks <civodul>the Emacs flavored kitchen sink is fine with me <civodul>there's consistency, plus it's a golden sink <civodul>what you describe is a mess in the literal sense of the word <civodul>it's out of control, but noone realizes until it collapses (leftpad style) <rekado>one real problem of these maximalist dependency sinks is version conflicts, and Python doesn’t have a good solution for that at all. <rekado>I wonder if we could successfully revisit our attempts to scope visibility of dependencies in Python packages <rekado>I’m working on a couple dozen packages now and one of them needs an older version of shellingham, yet I can’t just keep an older copy for this particular package. <rekado>because that older version of shellingham would conflict with the newer version if any other package used it too <rekado>we’ve been having this problem with tornado 5 and 6 <PurpleSym>rekado: I think I mentioned before that it’s possible to modify Python’s library loader in a way that each package has “its own”, built-in PYTHONPATH. <PurpleSym>(Without having a global environment-variable PYTHONPATH.) <rekado>yes, there have been a few attempts in the past IIRC but they kinda ran out of steam <rekado>I’d love for this work to continue, because it’s a real shame we can’t benefit from all these independent package builds when we are forced to dump them all into the same environment <PurpleSym>Yeah, we (explicitly including me) seems to have trouble getting good ideas across the finishing line. (pyproject-build-system, antioxidant, …) <PurpleSym>rekado: Have you had the time to create an SSH key for the guix-cran user on berlin, btw? <rekado>PurpleSym: sorry, put it off and didn’t get back to it. <rekado>that’s so that the guix-cran user can manipulate the git repo? <PurpleSym>rekado: Correct, we I need to add it to the robot’s GitHub account, so it can push.