Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle userdir migration with pythonlsp dir #72

Open
albilu opened this issue Oct 15, 2023 · 1 comment
Open

Handle userdir migration with pythonlsp dir #72

albilu opened this issue Oct 15, 2023 · 1 comment
Labels
enhancement New feature or request pri-low

Comments

@albilu
Copy link
Owner

albilu commented Oct 15, 2023

2 things:

  1. I think that the computer should resolve this upgrade issue automatically. I do not understand this "Auto Update LSP Sever on startup. My scenario appears to be normal and predictable and should not cause a failure. Next time I upgrade NetBeans it might happen again.

  2. I think that the exception must not happen because it is confusing. Perhaps you can change something to make it go away.

Originally posted by @bernard01 in #71 (comment)

@albilu albilu added enhancement New feature or request pri-low labels Oct 15, 2023
@bernard01
Copy link

bernard01 commented Oct 16, 2023

Just my thoughts:

From my perspective, I do NOT have any preferences or settings that I am expecting to be migrated, say from NetBeans 18 to NetBeans 19 in this case.

What I would expect to happen is as follows:

Let's look at the point after the import of userdir / preferences from a previous NetBeans version.

I do not necessary expect that NetBeans automatically upgrades my Python plugin. This would be a feature that i do not expect. I would be happy if the plugin was missing after the NetBeans upgrade.

However, I do expect that a fresh plugin installation (from a new version download) works as FRESH in this case.

That means that it should find its dependencies and that the installation should ONLY succeed if all dependencies could be installed. If not, then the installation should fail.

At present, the installation succeeds but all dependencies are missing. This is a defect.

If you implement the flow accordingly, then this might be easier and less work for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pri-low
Projects
None yet
Development

No branches or pull requests

2 participants