https://bugs.documentfoundation.org/show_bug.cgi?id=143867
--- Comment #10 from flywire <flywi...@gmail.com> --- ;TLDR Embedded LO python will never be standard so DOCUMENT IT so users can work with it, include pip as in a standard install (likely in an admin area). Someone getting a non-standard undocumented feature to work means no more than it can work. ========== (In reply to elmau from comment #9) > With LibO 7.2 in W10, pip install correctly again. So, we can close this > issue. Why? V7.2 is pre-release. V7.0 is still available. How are users expected to deal with the issue? LibreOffice 7.2.0 - If you're a technology enthusiast, early adopter or power user, this version is for you! LibreOffice 7.1.5 - This version is slightly older and does not have the latest features, but it has been tested for longer. For business deployments, we strongly recommend support from certified partners which also offer long-term support versions of LibreOffice. Available Versions - LibreOffice is available in the following released versions: 7.2.0, 7.1.5, 7.0.6 > PS C:\Program Files\LibreOffice\program> .\python.exe > C:\Users\Pruebas\get-pip.py --user Where is *that* documented? I never have any need for powershell. ========== (In reply to Ming Hua from comment #7) > (In reply to flywire from comment #6) > > pip maintainers consider LibreOffice python install is incomplete because > > pip should be installed as part of the distribution - > > https://github.com/pypa/pip/issues/10006#issuecomment-899956947 > Again, I want to point out that the problem description in that ticket seems > to only apply for LO 7.0 or earlier, from my personal experience. > Problem: Installing packages is essential for more than trivial python use yet there is no documentation Issues are: * Clear user documentation should be available. Pip maintainers say their documentation can't be followed because the LO python package doesn't include pip - pip should be part of embedded python. * It is not uncommon for users to have python installed on their system. How can a user work with the specific version they need to? How does a user even know where LO embedded python is in eg "C:\Program Files\LibreOffice\program\python.exe" or is that "C:\Program Files\LibreOffice\program\python-core-3.8.10\bin", or perhaps "C:\Users\User\AppData\Roaming\Python\Python38\Scripts"? * Related issue is should LO python be in a venv as in other software where it is embedded? 1. What documentation are you referring to? 2. Version information above. 7.0 is an available version. How are users expected to know how to deal with this issue? > > Tested on LibreOffice 7.2 (Python 3.8) [LibreOffice 7.0 (Python 3.7) not > > tested]. > > > > Following [Ensure you can run pip from the command > > line](https://packaging.python.org/tutorials/installing-packages/#id13) > > > If that still doesn’t allow you to run python -m pip > > > > ``` > > Microsoft Windows [Version 10.0.19043.1165] > > (c) Microsoft Corporation. All rights reserved. > > > > C:\Program Files\LibreOffice\program>python -m get-pip.py > > C:\Program Files\LibreOffice\program\python-core-3.8.10\bin\python.exe: > > Error while finding module specification for 'get-pip.py' > > (ModuleNotFoundError: __path__ attribute not found on 'get-pip' while trying > > to find 'get-pip.py') > Why did you do this? get-pip.py is the filename of the script, not a python > module name. And -m requires a module parameter to follow. This would > never work, not on LO's bundled python, nor on the official python.org > installation. > LO has no docs for installing packages or pip. I followed the link given to the official pip docs. "And -m ... This would never work" - that's my understanding of the pip docs. Who knows why you chose those commands, I showed my workflow clearly rather than just the commands that worked. > You should invoke the script directly with "python.exe get-pip.py", like you > did below. > > > C:\Program Files\LibreOffice\program>python get-pip.py > > Defaulting to user installation because normal site-packages is not > > writeable > Why did this happen? Did you run the command above with an ordinary user > without administrative privileges? I'm an ordinary user and I followed official pip docs. iirc I installed with and without admin rights during testing but I can't recall which one I documented here. Should be without admin rights. > > Collecting pip > > Using cached pip-21.2.4-py3-none-any.whl (1.6 MB) > > Installing collected packages: pip > > Attempting uninstall: pip > > Found existing installation: pip 21.2.4 > > Uninstalling pip-21.2.4: > > Successfully uninstalled pip-21.2.4 > > WARNING: The scripts pip.exe, pip3.8.exe and pip3.exe are installed in > > 'C:\Users\User\AppData\Roaming\Python\Python38\Scripts' which is not on > > PATH. > > Consider adding this directory to PATH or, if you prefer to suppress this > > warning, use --no-warn-script-location. > And here the script warned you that you are installing pip inside your home > directory, which is normally not checked by LO's python.exe. Again, where are the docs? > > Successfully installed pip-21.2.4 > > ``` > > > > I don't know where it found existing installation, it wasn't in the path and > > that folder was empty until pip was installed. Maybe `get-pip.py` needs to > > be downloaded to `C:\Program > > Files\LibreOffice\program\python-core-3.8.10\bin`. > The get-pip.py can be placed in any folder, just make sure to run it with > LO's python. For example > > "C:\Program Files\LibreOffice\program\python.exe" get-pip.py > can be done from any folder that contains get-pip.py. > > Also make sure you run it with an admin account (or at least an account that > can write to C:\Program Files\LibreOffice\), and things should go smoothly. *Document it* and make pip part of LO embedded python. -- You are receiving this mail because: You are the assignee for the bug.