@quintz Could you open a new 'Get help' topic so I can talk it through later today, since it gets confusing with multiple conversations here.
@bbc0 - The next version of OctoPi is going to be Python 3 default (0.18). The script is easy to use, even for someone who's not a 'techie'!
@Muldoon - do NOT run the commands as root, since it messes with the permissions.
The first error, you can ignore (Made by OctoLapse not playing nice with reading the plugins), the second is because it is run as root.
Sorry, I use Octopi and I use Klipper, but I don't know much about Python. I installed Octopi 017 on my Raspi 3B, and I installed Klipper in the official way, meaning a git pull and then starting the installation script. I don't know if this creates a seperate virtual environment. Updating Klipper works similar: The official way is to do a git pull, then restart the service. In some cases, a new MCU-firmware is an additional step.
As the functionality of Klipper is critical for my printer, I will wait until there is a clear statement from the Klipper developers.
@derekpurdy, Yes, there are a couple of ways. If you are running OctoPrint 1.4.2, then the Plugin Manager will show you directly. For 1.4.2 and earlier versions, you can install the plugin Python 3 Check by @jneilliii using the Plugin Manager.
Thanks![quote="b-morgan, post:47, topic:23973, full:true"] @derekpurdy, Yes, there are a couple of ways. If you are running OctoPrint 1.4.2, then the Plugin Manager will show you directly. For 1.4.2 and earlier versions, you can install the plugin Python 3 Check by @jneilliii using the Plugin Manager.
Hey @Detlev_Rackow
I just had a look at Klipper, and it doesn't run in Python at all. What you may be thinking of is the plugin for OctoPrint for a better (than already functional) integration.
In the coming days the Klipper plugin is being adopted, with the new version already compatible. Once that happens, then you should have no issue upgrading to Python 3.
@coubi64 - that looks like an issue with the specific plugin, (Dashboard) since Resource Monitor updates correctly, whatever is wrong in Dashboard should be reported to the plugin author so they can take a look.
(I am biased) but would it not be fun to have Python 3.7 in the bottom corner of your web interface now. There's also some performance improvements....
True but off-topic story: the very first plugin I published for Cura pretended to offer a way to switch off automatic slicing after making changes. All it did was place a white rectangle over the slicing progress bar so you would not see the slicing taking place. I got actual users telling me how much it sped up Cura. (Since then the plugin has been rewritten to actually do what it promised)
I started the upgrade-script on my Octopi 0.17 with Octoprint 1.4.12.
I confimed all prompts with enter, and entered my password when prompted in order to install python3-dev. Immediately after entering my password, the putty-session was terminated by the host.
Octoprint continued to work. I tried to restart the script, after entering my password for Python3-dev I got a cryptic message about wrong data in the stream.
Next step was to download and start the downgrade-script, which failed, claiming there is no data in the backup path.
At this point, my Octoprint installation does no longer work. The server is reachable via SSH, but Octoprint is not running.
When I ssh into the system, I see:
OctoPrint version : unknown
OctoPi version : 0.17.0
What is the best way to recover? I have an almost up-to-date backup of my Octoprint config, and I can backup my Klipper-config.
@Detlev_Rackow - could you open a separate topic, so I can discuss it through with you, and get a solution - it is fully possible to recover, since nothing of the old install gets deleted.
Easier than the comments of this post, where discussion gets confusing with many people.
Funny, I made a super half-hearted investigation to switch to Python 3 just last week. Saw it wasn't super easy and gave up. Then this post came out. Ran it on my most recent of three OctoPi 0.17 installs and it was super easy. No problems at all. Got the other two running right now but looks like I'll be able to switch everything to Python 3 with no problem at all. Thank you for making it so easy!
