jupyter VS vscode-python

6. Jupyter Jupyter is a collection of tools and applications designed for interactive computing and data visualization. At the heart of the Jupyter ecosystem is the Jupyter Notebook, an interactive web-based platform that allows you to create and share documents containing live code, equations, visualizations, and narrative text. It’s an excellent tool for exploratory data analysis, model prototyping, and creating reproducible data science workflows.

How cool. This motivated a quick search - this could be fun:

How to write your own kernel

https://jupyter-client.readthedocs.io/en/stable/kernels.html

All the language kernels (a lot of abandoned ones - the mariaDB one ('binder') will take a while to load but SQL in Jupyter!)

https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

There are Jupyter kernels for Python, Mathics, Wolfram, R, Octave, Matlab, xeus-cling, allthekernels (the polyglot kernel). https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

Not only there is. But it is only a simple Google search away... But to make it simpler... There are 3 😁 https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

As it seems, this is not quite straight forward and manyusers have similar troubles.

Community maintained kernels : https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

Derek Banas on YouTube is doing a "Python for Finance" course at ghe moment using Jupyter, and is making the files available. I believe he's done others too.Failing that, there's this Git repo: A gallery of interesting jupyter notebooks

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.