Re: Python installation paths, pip, F36

On 26. 05. 22 6:10, Owen Taylor wrote: [ At Miro's request, resending this to python-devel so the discussion can be public ] Hi Miro - Hey Owen. [the same here] When rebuilding a package to include in a Flatpak, we want to install *everything* under prefix=/app - that includes Python modul

Re: Python installation paths, pip, F36

On 26. 05. 22 6:27, Neal Gompa wrote: On Thu, May 26, 2022 at 12:10 AM Owen Taylor wrote: [ At Miro's request, resending this to python-devel so the discussion can be public ] Hi Miro - When rebuilding a package to include in a Flatpak, we want to install *everything* under prefix=/app - t

Re: Python installation paths, pip, F36

Thanks for the detailed response! To start with your final questions: > - Why is Python itself not installed in the /app prefix? > - Where and how is pip install invoked? The way that Flatpaks work is that there are *two* filesystem images, one mounted on /usr and one mounted on /app. The ima

Re: Python installation paths, pip, F36

On 26. 05. 22 17:13, Owen Taylor wrote: Thanks for the detailed response! To start with your final questions: >   - Why is Python itself not installed in the /app prefix? >  - Where and how is pip install invoked? The way that Flatpaks work is that there are *two* filesystem images, one mou

Re: Python installation paths, pip, F36

On Thu, May 26, 2022 at 1:07 PM Miro Hrončok wrote: > On 26. 05. 22 17:13, Owen Taylor wrote: > > > A pip with a backported patch (or a rebase) + this approach sounds most > > maintainable for Fedora 36. But if we think that the --prefix %{_prefix} > > approach actually works, then perhaps we can

Re: Python installation paths, pip, F36

On 26. 05. 22 22:08, Owen Taylor wrote: On Thu, May 26, 2022 at 1:07 PM Miro Hrončok > wrote: On 26. 05. 22 17:13, Owen Taylor wrote: > A pip with a backported patch (or a rebase) + this approach sounds most > maintainable for Fedora 36. But if we th