@Arjan Could totally be node 12! maybe its a stretch to think so, but at work we had problems on a bunch of unrelated stuff and using 'LTS' supported version 10 instead of the pre-release 12 fixed it ! ... so I wouldn't be surprised if the beta node 12 was a problem. (node is the engine running all the debug stuff of vscode) might be worth a try to replace node 12 by the more stable node 10 (if its not a major inconvenience for you to try this out)
On Saturday, October 12, 2019 at 4:10:21 PM UTC-4, Arjan wrote: > > Hmm, I'm sure I saw Python 2.7 getting installed, as well as Chocolatey > and one or more MS dependencies, perhaps one of those triggered it. But I > was just mentioning that message for completeness. > > As for versions: > - VSCode 1.39.1 > - Node.JS 12.11.1 -- that seems like the only significant difference, but > seems an unlikely cause for the problem? > - Leo 6.0-final (master branch from Git) > - Python 3.7.3 (via Anaconda) > - PyQt version 5.9.6 (installed via `conda install pyqt` -- as far as I > remember, and put in my notes, I didn't specify anything further for Qt5 > itself). > > Cheers, > Arjan > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/57812f0f-caaf-4204-b44a-821622105fd7%40googlegroups.com.
