openvscode-server VS vscode-python

> Yeah, sadly there are entry level laptops cheaper than a phone or said monitor plus a keyboard and mouse

Many people already have a monitor, mouse, and keyboard lying around. They'll also have a phone already. Plus, there are very cheap docks where you can just slide your phone into a laptop shell, priced similarly to the worst and most awful Chromebooks imaginable.

> So nothing works offline.

You can run a vscode server on your phone (https://github.com/gitpod-io/openvscode-server/releases). What's lacking is the VSCode GUI, so pointing a browser at http://[::1]:8080/ will work just fine.

This already exists!! https://www.gitpod.io/

The next part is the 'Public access' parameter which needs to be aligned with the DB Subnet Group configuration. When set to No, the provisioned ENI will only have Private IP. If you try to access it from the Internet, your PC or a cloud development environment such as Gitpod that would obviously not be accessible. However, if you set it to Yes, the ENI will also have a Public IP and a Public hostname (DNS endpoint). This settings can be changed without the need to re-provision the RDS which is quite handy.

https://www.gitpod.io/ does this

Not sure what .devcontainer means, but you can take a look to https://github.com/gitpod-io/openvscode-server or https://github.com/coder/code-server

I am using this project (https://github.com/gitpod-io/openvscode-server/) to run on my Linux box, then I can access it's server through my web browser.

We look forward to integrating more with Gitpod in the future! Check out the Gitpod homepage for more information and new development environment templates.

I suggest you check out https://www.gitpod.io, which does more general provisioning of GitOps clusters/Pods in their managed Kubernetes clusters. It's not specifically ML, but we've looked at it for POC ML projects that want basic hosting.

The last option - the Dev Environments - is the most exciting functionality - it gives you the possibility to host development environments (similar to Gitpod) on AWS using Cloud9 but also, and this is really cool, using Visual Studio or JetBrains IDEs. When using that option, the IDE on your local PC is only the "presentation layer", the source code is stored and run on an AWS instance and the IDE uses remote connectivity to talk to the Dev Environment in the background.

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.