vscode-python VS quokka

Ah, Chrome and slow spinners.

Python tests were taking ages on VSCode due to an SVG spinner:

https://bugs.chromium.org/p/chromium/issues/detail?id=103626...

https://github.com/microsoft/vscode-python/issues/9216

It seems to be a problem caused by the new version of the Python extension. Here is a GitHub link for you to follow up.

For the python extension, please file your issue here: https://github.com/microsoft/vscode-python/issues

There seems to be a focus on feature velocity, and as the big parts start to stabilize (language server stuff, refactoring, extension framework, general UI/UX expectations), I hope we'll see some more attention paid to the default experience. But changing defaults in an ecosystem where users embrace configurability is tough, see the pythonPath fiasco, so I don't know the way forward. Core dev Brett Cannon seems to support the opinionated path for the VSCode Python experience going forward, so we'll see where that takes us.

I filed a GitHub report, you can always follow up.

Jedi said it had a fix on this post which links to this but isn't that just the Jedi source code showing fixes? The only reference I see in there is " Autocomplete inherited methods when overriding in child class ", but I just want it to autocomplete when typing a method from the parent class on a subclass instance.

If you still want to use python3.3.1 in vscode, you can submit a report on GitHub to consult the official staff.

It works fine on my machine after testing, can you provide your test code and show your personal settings(settings.json)? If you are convinced that this is a problem with python extensions, you can file a report on GitHub.

Does this help? Maybe you are opening the workspace at the wrong folder level?

Actually, it looks like it might be an issue with syntax highlighting ("Intellisense" in MS terminology) in Microsoft VS Code. Here is almost an identical post to mine in their forum.

For more features and details check out the official docs https://quokkajs.com/

Used to be true, but between Quokka.js for quick prototypes, Wallaby.js for running tests smartly within the IDE, and now Console Ninja which enables inline console.log within the VSCode while running servers for common tooling (webpack, vite). As well as continuously improving collaboration tools like Live Share, And it's become hard for me to find an argument that Webstorm is still better for productivity here.

I use https://quokkajs.com/ it has a free version!

There are some fantastic tools such as Quokka which make "more algorithmic" development very interactive and fun

There's also extensions like https://quokkajs.com/

Quokka.js

I’m a Clojure(script) dev learning TS. My Clojure REPL flow is Cursive + IntelliJ. The closest equivalent I’ve found is https://quokkajs.com for inline evaluation and https://wallabyjs.com for test evaluation. Both are paid products but have free 30 day evaluation periods. Both work in IntelliJ and VsCode.

If you want to code and practice your JS in a sandbox, I highly recommend using VS Code (if you're not already using that for your HTML/CSS) in conjunction with Quokka.js. If you use `console.log()` function to log your results, Quokka will output directly in the editor. There are online resources that do something similar like codesandbox.io but I've found it nice to have a local environment.