https://bugs.kde.org/show_bug.cgi?id=458164

--- Comment #4 from Bartimaeus <cnachtm...@gmail.com> ---
(In reply to Alexander Semke from comment #3)
> (In reply to Bartimaeus from comment #2)
> > I have Python 3.8.10 installed and have the same issue (with LabPlot v 2.9.0
> > on Windows). What *exact* version of Python is needed for this version of
> > LabPlot? There isn't any indication in the program itself that I can find
> > that says this (seems like having this specified in the components tab of
> > the "About LabPlot" dialog would be a good idea). LabPlot also doesn't seem
> > to be able to detect that it's the wrong version of Python (or isn't
> > providing any sort of warning to the user). It would be nice if LabPlot
> > could give a warning to tell the user what they need to do to get the
> > feature working until a more flexible solution can be found.
> Yes, this area needs definitely more attention from us and we're looking
> already into into how to enable different versions and to improve the error
> handling.
> 
> As to your first question, it should work with 3.8.10. Did you add python
> executable to PATH on your computer. If yes, does you get the same result as
> described in this ticket - you're able to create a python notebook, type in
> an expression and don't get it evaluated - or is LabPlot immediately
> crashing for you once you try to add a new python notebook?

Checking Python install location in cmd:
C:\Users\[username]>where python
C:\Users\[username]\AppData\Local\Microsoft\WindowsApps\python.exe

My user Path variable has: %USERPROFILE%\AppData\Local\Microsoft\WindowsApps

I get the same behavior as described in the ticket-- able to create a python
notebook, type in an expression and don't get it evaluated

I've uploaded an image with two screenshots and some annotations to show the
behavior: https://imgur.com/a/oPdZgQF


I also tried adding to the System environment Path variable with no change in
behavior

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to