Octoprint-venv-tool fails at FormerLurker/Octolapse install step

AEtherScythe · April 24, 2025, 4:36pm

What is the problem?

octoprint-venv-tool fails at FormerLurker/Octolapse install step

What did you already try to solve it?

I retried the operation, looking for logs, but I don't know where to find them.

Have you tried running in safe mode?

NO. Octoprint is stopped as per the documentation.

Did running in safe mode solve the problem?

N/A

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

octoprint-systeminfo-20250424123012.zip (1.1 MB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

On Raspberry Pi Buster, with all the latest updates available for this very old OS...
I started to migrate to python 3.13.3 using my favorite pyenv approach.
e.g.

$ sudo apt-get install libbz2-dev libncurses-dev libreadline-dev libsqlite3-dev tk-dev liblzma-dev
$  git clone https://github.com/pyenv/pyenv.git ~/.pyenv
$  cd ~/.pyenv && src/configure && make -C src
$  echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bashrc
$  echo 'command -v pyenv >/dev/null || export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.bashrc
$  echo 'eval "$(pyenv init -)"' >> ~/.bashrc

Logout and back in

$ pyenv install --list | grep '[[:blank:]]3\.'
$ pyenv install 3.13.3
$ pyenv global 3.13.3

$ python --version
Python 3.13.3

$ pip install --upgrade pip

Then I proceeded with the Octopi migration...

pi@octopip:~ $ sudo service octoprint stop

pi@octopip:~ $ ./octoprint-venv-tool recreate-venv /home/pi/oprint --python `which python3`

Creating plugin export at /tmp/plugin-export-z8hs3mld.json...

Backing up existing venv to /home/pi/oprint.bck...

Creating new venv at /home/pi/oprint using python at /home/pi/.pyenv/shims/python3

Python at /home/pi/.pyenv/shims/python3 has version (3, 13, 3)

Creating venv from /home/pi/.pyenv/shims/python3...

Installing pip...

Installing wheel...

Installing OctoPrint...

Installing plugin export /tmp/plugin-export-z8hs3mld.json into recreated venv /home/pi/oprint...

Installing https://github.com/paukstelis/OctoPrint-Cancelobject/archive/master.zip...

Installing https://github.com/cesarvandevelde/OctoPrint-M73Progress/archive/master.zip...

Installing https://github.com/FormerLurker/Octolapse/archive/master.zip...

Restoring backed up venv...

Error running recreate-venv: Command '('/home/pi/oprint/bin/python', '-m', 'pip', 'install', 'https://github.com/FormerLurker/Octolapse/archive/master.zip')' returned non-zero exit status 1.

I don't know where to look to find further logs about the FormerLurker/Octolapse install issue.

AEtherScythe · April 24, 2025, 4:40pm

Is it this bug?

github.com/FormerLurker/Octolapse

[Bug]: Cannot install on Python 3.12

opened 09:13AM - 11 Jun 24 UTC

JohnyPeaN

#### If this is a feature request describe it here  ___REPLACE_THIS__FEATURE_REQUEST_DESCRIPTION_GOES_HERE #### Version of Octolapse  Octolapse Version: 0.45 #### Version of OctoPrint  OctoPrint Version: 1.10.1  #### When you ran into the problem, did you have diagnostic logging enabled?  Diagnostic Logging was Enabled: NO #### What were you doing when the problem occurred  1. Upgraded to octoprint 1.10.1, system upgraded python to 3.12 2. Tried to install octolapse plugin - failed 3. Prepared latest versioneer.py from master (https://github.com/python-versioneer/python-versioneer) 4. Extracted octolapse.zip, replaced versioneer.py with vesion from step 3, repacked into zip 5. installed from resulting file - success #### What should have happened? Installation should succeed. #### What happened instead? > Collecting https://github.com/FormerLurker/Octolapse/archive/v0.4.5.zip Downloading https://github.com/FormerLurker/Octolapse/archive/v0.4.5.zip / 1.3 MB 4.8 MB/s 0:00:00 Preparing metadata (setup.py): started error: subprocess-exited-with-error >× python setup.py egg_info did not run successfully. │ exit code: 1 ╰─> [15 lines of output] /tmp/pip-req-build-qf456kab/versioneer.py:421: SyntaxWarning: invalid escape sequence '\s' LONG_VERSION_PY['git'] = ''' Traceback (most recent call last): File "<string>", line 2, in <module> File "<pip-setuptools-caller>", line 34, in <module> File "/tmp/pip-req-build-qf456kab/setup.py", line 25, in <module> plugin_version = NumberedVersion.clean_version(versioneer.get_versions(verbose=True)["version"]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-req-build-qf456kab/versioneer.py", line 1412, in get_versions cfg = get_config_from_root(root) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-req-build-qf456kab/versioneer.py", line 342, in get_config_from_root parser = configparser.SafeConfigParser() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? [end of output] >note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed >× Encountered error while generating package metadata. ╰─> See above for output. >note: This is an issue with the package mentioned above, not pip. hint: See above for details. Preparing metadata (setup.py): finished with status 'error'` #### Operating System running OctoPrint and Octolapse  OS Name: Manjaro ARM Linux Os Version: 24.04 #### Printer model & used firmware incl. version  Printer Model: Anycubic i3 Mega S Printer Firmware Version: Marlin 2.1.2.2 (knutwurst 1.5.4) #### Browser and version of browser, operating system running browser  Browser: Firefox Browser OS: Cachyos #### Link to the gcode file you were printing when the problem occurred  Link to Gcode File: ___REPLACE_THIS__GCODE_FILE_LINK_GOES_HERE #### Link to settings.json  Link to settings.json with all passwords removed: ___REPLACE_THIS__SETTINGS_JSON_LINK_GOES_HERE #### Link to plugin_octolapse.log  Link to plugin_octolapse.log: not available / not installed #### Link to octoprint.log  Link to octoprint.log: ___REPLACE_THIS__LINK_GOES_HERE #### Link to contents of Javascript console in the browser  Link to javascript console output: ___REPLACE_THIS__LINK_GOES_HERE #### Screenshots and/or videos of the problem:  Screenshot/Video Links: ___REPLACE_THIS__LINKs_GO_HERE ## Please consider becoming a patron If you like this project, [please support my work by becoming a patron,](https://www.patreon.com/bePatron?u=9588101) and consider adding a 'star' to the repository. It takes a lot of time and effort to maintain the project and respond to issues. The cost of test prints, software, cameras, printer parts, etc. can quickly add up, so every bit helps. You can find various [videos and tutorials](https://www.youtube.com/channel/UCnnTLQetNw7FqfQOLJCMqoQ) by subscribing to my Youtube channel. You can also [follow me on Twitter](https://twitter.com/FormerLurker1).

AEtherScythe · April 24, 2025, 4:49pm

The problematic plugin was disabled anyway, so I have uninstalled the plugin.
Attempting the python migration again now.

Maybe add an option to octoprint-venv-tool to skip disabled plugins?
That would be oh-so-convenient. =D

AEtherScythe · April 24, 2025, 4:55pm

We're good!

pi@octopip:~ $ ./octoprint-venv-tool recreate-venv /home/pi/oprint --python `which python3`
Creating plugin export at /tmp/plugin-export-hwg18qls.json...

Backing up existing venv to /home/pi/oprint.bck...

Creating new venv at /home/pi/oprint using python at /home/pi/.pyenv/shims/python3
Python at /home/pi/.pyenv/shims/python3 has version (3, 13, 3)
Creating venv from /home/pi/.pyenv/shims/python3...
Installing pip...
Installing wheel...
Installing OctoPrint...

Installing plugin export /tmp/plugin-export-hwg18qls.json into recreated venv /home/pi/oprint...
Installing https://github.com/cesarvandevelde/OctoPrint-M73Progress/archive/master.zip...
Installing https://github.com/eyal0/OctoPrint-PrintTimeGenius/archive/master.zip...
Installing https://github.com/paukstelis/OctoPrint-Cancelobject/archive/master.zip...

Recreation of /home/pi/oprint successful, removing backup...
... done!

/home/pi/oprint has been recreated with /home/pi/.pyenv/shims/python3!

It would still be helpful to keep a log file around that has the finer details of what went wrong with the problematic plugin.
It would still be helpful to have an option to skip disabled plugins during the python migration.