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

Installation Process Reliability Issues on Windows (Standalone) #23169

Open
Kai-yhuin opened this issue Dec 4, 2024 · 0 comments
Open

Installation Process Reliability Issues on Windows (Standalone) #23169

Kai-yhuin opened this issue Dec 4, 2024 · 0 comments

Comments

@Kai-yhuin
Copy link

Problem Description

Due to license issues, I have been using Spyder standalone since version 3 and now 5. Though have to change the python interpreter from time to time, I'm quite happy with the version 5. Lately when I recommend others to use, which they installed version 6, things get messy.

What steps reproduce the problem?

  1. Install Spyder 6 standalone on Windows 10.
  2. Install Python3 via windows installer (pip and environment variable checked).
  3. Change python interpreter inside Spyder, and install spyder-kernels via pip as instructed.
  4. Restart Spyder.
  5. Change graphics backend from inline to Qt.
  6. Install all necessary modules: numpy, matplotlib, PyQt5, etc
  7. Run a simple code plt.imread(), plt.imshow().

What is the expected output? What do you see instead?

Most people can get in done, but will have one or two still getting the graphics displayed as inline. We tried several methods but end up changing to Tk backend. It's not really a functionality issue, but user experience issue, why our previous method no longer works, and/or why upgrading is unfriendly.

Suggestion: is it possible to make Qt as default? inline is really inconvenient and impractical for image processing, perhaps drop it? XD
Other: changing the language version without virtual environment, could it be improved? Currently have to change path environment or delete the whole thing just to ensure pip has no conflict.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant