Alexandre Archambault
Alexandre Archambault
If you want to build Scala CLI without the mill-scala-cli plugin, you can add a line such as ```scala def enableScalaCli = false ``` right below [this one](https://github.com/VirtusLab/scala-cli/blob/8aab8a311c5fe5e81366ae4f56984df3478b721c/project/settings.sc#L786).
Closing this issue… As of https://github.com/VirtusLab/scala-cli/pull/1335 (that uses Mill `0.10.7`), it seems the incremental compilation issues went away. It seems to be the same on the coursier build, where I...
(Draft for now as I only tested that with Python 3.10 locally…)
@shadaj Is that better now? This only relies on `PyValue`, no more `py.*` stuff.
Although I reproduced that here using Scala CLI, this is also happening to me outside of it, when running things from standard JARs.
Same thing from Scala Native too: ``` $ echo 'py.Dynamic.global.print("Hello")' > foo.sc $ scala-cli run -S 2.13 --python foo.sc --native 2>/dev/null | cat $ scala-cli run -S 2.13 --python foo.sc...
Thanks a lot for the workaround, @kiendang! Don't know if this issue should be closed… It seems the `python` binary ensures its stdout is flushed. Maybe ScalaPy could do the...
Should be a matter of setting [`jvmIdOpt`](https://github.com/VirtusLab/scala-cli/blob/0d09ebf5fd369074090c9e431c43af318b07293a/modules/options/src/main/scala/scala/build/options/JavaOptions.scala#L20) in the `BuildOptions` provided by the directive.
In Scala CLI, for now, `UTF-8` is assumed almost everywhere, yeah…
Same with Scala.JS: ```text $ scala-cli run --js -S 2.13.8