Description: -- Steps to Reproduce: 1. Open console window 2. Create a working folder for a new project, change to that folder: mkdir proj && cd proj 3. Add (prepend) "C:\Program Files\LibreOffice\program" to the PATH: set PATH=C:\Program Files\LibreOffice\program;%PATH% 4. Verify the python.exe to be executed is the one from LibreOffice: where python 5. Run command: python -m venv venv Actual Results: Error occurs: C:\Program Files\LibreOffice\program\python-core-3.10.18\bin\python.exe: No module named venv Expected Results: The virtual environment named "venv" is created in the folder created on step 2 Reproducible: Always User Profile Reset: Yes Additional Info: Creating a virtual environment for any project is the standard approach in Python development. This helps a developer to ensure the development environment is the same as the runtime environment, and also makes packaging with ooscript easier. Lacking support for venv complicates development tasks, especially on Windows.
Fix in https://gerrit.libreoffice.org/c/core/+/191377
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/dd8c42bf4b6eb5f692bb929547f69a9aedcf6c0c tdf#168511: python3: bundle venv It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/dcd517331c8db63fee75b1519608e9ca94a491bb related tdf#168511: bundle venv on mac too + Add test It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Xisco Fauli committed a patch related to this issue. It has been pushed to "libreoffice-25-8": https://git.libreoffice.org/core/commit/ecda1df6a14e99d5713309b786ff9137dda4767e tdf#168511: python3: bundle venv It will be available in 25.8.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Xisco Fauli committed a patch related to this issue. It has been pushed to "libreoffice-25-8": https://git.libreoffice.org/core/commit/fbb1d7bcba219685d789c2f4cdf348f8f7f8d696 related tdf#168511: bundle venv on mac too + Add test It will be available in 25.8.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Commit Notification from comment #5) > > It will be available in 25.8.3. > > The patch should be included in the daily builds available at > https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More > information about daily builds can be found at: > https://wiki.documentfoundation.org/Testing_Daily_Builds > > Affected users are encouraged to test the fix and report feedback. Tested venv against daily build 2025-11-06_04.09.06, unfortunately no progress at this time - still not working. There should be "scripts" folder in the "python-core-3.11.14\lib\venv" folder, and "venvlauncher.exe" binary in the "python-core-3.11.14\bin" folder. Otherwise, it won't work (and doesn't).
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/63460e46daa3a0ba2c897e00ba28d8cc26dac6dc related tdf#168511: bundle venvlauncher.exe too It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to denis.gz from comment #6) > (In reply to Commit Notification from comment #5) > > > > It will be available in 25.8.3. > > > > The patch should be included in the daily builds available at > > https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More > > information about daily builds can be found at: > > https://wiki.documentfoundation.org/Testing_Daily_Builds > > > > Affected users are encouraged to test the fix and report feedback. > Tested venv against daily build 2025-11-06_04.09.06, unfortunately no > progress at this time - still not working. There should be "scripts" folder > in the "python-core-3.11.14\lib\venv" folder, and "venvlauncher.exe" binary > in the "python-core-3.11.14\bin" folder. Otherwise, it won't work (and > doesn't). Hi Denis, Thanks for you feedback. 63460e46daa3a0ba2c897e00ba28d8cc26dac6dc should fix the missing venvlauncher.exe. Could you try again with a newer daily build which includes that commit ? Thanks in advance
(In reply to Xisco Faulí from comment #8) > Hi Denis, > Thanks for you feedback. 63460e46daa3a0ba2c897e00ba28d8cc26dac6dc should fix > the missing venvlauncher.exe. Could you try again with a newer daily build > which includes that commit ? > Thanks in advance The result is as following: C:\Users\User\project>python -m venv venv Unable to copy 'C:\\Program Files\\LibreOfficeDev 25\\program\\venvlauncher.exe' Error: [Errno 13] Permission denied: 'C:\\Program Files\\LibreOfficeDev 25\\program\\python-core-3.12.12' Dunno what is it... The same happens both from Administrator and User prompt. This doesn't happen with venv module copied manually from another Python distro (as I described in my initial ticket).
I just noticed the release notes for 25.8.4 shows pip was added to the LO internal python and 26.2.0.3 show venv has been added. I was not able to create a python virtual environment and followed the release notes to this report. I see this report was marked RESOLVED FIXED. I noticed denis.gz at Comment 9 indicated a permission error. This is the behaviour I experience also running as regular user on Windows 11. I am new to the bug reporting process. From what I read I believe it is correct for me to add a comment to this bug report and mark it REOPENED. Keeping a test consistent with Comment 9 I noticed there is a duplicate path separator in the python `sys.prefix` before `python-core-3.12.12` and wonder if this may be the cause of the error. 1. Run cmd.exe 2. Set PATH=C:\Program Files\LibreOffice\program;%PATH% 3. Create a virtual environment: python -m venv lo_venv 4. Receive error: Error: [Errno 13] Permission denied: 'C:\\Program Files\\LibreOffice\\program\\python-core-3.12.12' 5. Run python and import sys and check sys.prefix to ensure it is correct installation: >>> import sys >>> sys.prefix 'C:\\Program Files\\LibreOffice\\program\\\\python-core-3.12.12' Note the duplicate path separator before python-core-3.12.12