Piotr Krzemiński

Right now, after explicitly building Python stdlib (`./gradlew :kotlin-stdlib-py:build`), the KLib is accessible under `libraries/stdlib/py/build/libs/kotlin-stdlib-py-js-1.6.255-SNAPSHOT.klib`. The goal now is to build it within `./gradlew dist` and copy it over to...

I refer to https://kotlinlang.slack.com/archives/C0289CS37AS/p1637160755034700?thread_ts=1636875290.016700&cid=C0289CS37AS which is pretty vague, but I understand it as e.g. using `maven-publish` plugin for publishing instead of some custom Gradle configurations. Pragmatically, we can leave things...

Left to do: currently Python stdlib relies on copying some JS stdlib. It shouldn't happen - both should be independent. It's a matter of copying some files over to Python...

Sorry, I have to drop working on this fix. Feel free to take over.

.

Knock knock.

Is it still on the roadmap? If yes, does it make sense to exclude it from auto-resolving?

Robot, your resistance is futile, please stop auto-resolving this issue.

I'm considering porting snakeyaml-engine to multiplatform. Started a thread in https://kotlinlang.slack.com/archives/C7A1U5PTM/p1684498259191979?thread_ts=1684498259.191979&cid=C7A1U5PTM

Here's a WIP integration with the multiplatform port of snakeyaml-engine https://github.com/charleskorn/kaml/pull/437. I need to pause working on it, but it potentially requires minimal effort to push to a mergeable state.