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

Include in instructions to configure PythonSlicer as Python interpreter in PyCharm #20

Open
amymmorton opened this issue Dec 5, 2024 · 4 comments

Comments

@amymmorton
Copy link

I added my frustration and detailed steps to the discourse too- but I'm shocked that such an important detail is missing in the README.

I've been struggling to set this up for weeks on and off..
I didn't even get the idea until an ai google search tipped me off:
image
Even that doesn't instruct to find you PythonSlicer.exe

and the youtube tutorial I was trying to follow gave a hint (though not explicitly)
image

@lassoan
Copy link
Member

lassoan commented Dec 6, 2024

The AI chatbot gave incorrect answer. There is no need to select "PythonSlicer" as interpreter in PyCharm.

When debugging Slicer, you "attach" the debugger to the Python interpreter running in Slicer, so you may not even need to select any Python interpreter inside PyCharm (but if PyCharm wants you to select one then you can choose any default/system Python environment that you have).

If you use the latest PyCharm version then the connection fails because PyCharm developers broke their debugger (again). See details and a workaround here: #19

@amymmorton
Copy link
Author

OK thank-you! Maybe then the suggested IDE should be switched to VSCode in the readme then?

@amymmorton
Copy link
Author

VS Code successful- and you're right no explicit interpreter required. Thank-you!

image

lassoan added a commit that referenced this issue Dec 6, 2024
@lassoan
Copy link
Member

lassoan commented Dec 6, 2024

Maybe then the suggested IDE should be switched to VSCode in the readme then?

Good point, I've updated the README file.

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

2 participants