this post was submitted on 12 Dec 2023
5 points (100.0% liked)

LabPlot Data Analysis and Visualization Software

108 readers
2 users here now

KDE's data visualization and analysis software. LabPlot is free, open source, works on Linux, WIndows and macOS, and is accessible to everyone.

Share here your tips, tricks and resources, request help, talk to the maintainers and devs, read LabPlot news, connect with other users.

founded 1 year ago
MODERATORS
 

Did you know that you can work with Jupyter notebooks directly in LabPlot?

@[email protected]

For example, let's open the following notebook to see how it works in #labplot

👉 https://github.com/demotu/BMC/blob/master/notebooks/Statistics-Descriptive.ipynb

#DataAnalysis #DataScience #Data #DataViz #Visualization #Plotting #Science #Statistics #FOSS #OpenSource #Python #Jupyter

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 7 months ago (3 children)

That's a great feature, indeed!

I just downloaded this file and opened the notebook in LabPlot. This worked fine in general, but in some places I got errors because of missing packages.

I can see that there is a requirements.txt in the same repo two folders up.

How do I install packages into the environment LabPlot uses? Where can I define a venv for LabPlot? Can I define different venvs for different projects?

[–] [email protected] 0 points 7 months ago (2 children)

@silmaril

Working with a custom venv in LabPlot is not possible yet.

[–] [email protected] 1 points 7 months ago (1 children)

I think it should be quite simple to make this possible.

All we need is a parameter for the python binary path in the CAS Python configuration.

This could be improved further by adding such a parameter to the project, which would override the global value if it is set and which could be a relative path, too. (OK, maybe we would also need some kind of automatism to find the correct binary both on Windows and Linux, because the path from the venv to the acutal python binary is different depending on the system).

[–] [email protected] 1 points 7 months ago

@silmaril unfortunately this is more complicated… we’re not communicating with the binary like this is the case for example for Maxima and Octave but embedding the interpreter at runtime. So, our binaries are linked to python’s shared library. This is done at build step and this is the reason why we can only work with the “system version” of Python. This is an important topic that was raised to us already multiple times and we hope we can start working on it in the near future.