On Mon, 2024-09-02 at 14:07 +0100, Barry Scott wrote: > > > On 2 Sep 2024, at 12:13, Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > > > Yes, I'm vaguely aware of that possibility though I've never had to use > > it up to now, i.e. everything has "just worked". > > Usually on Fedora it has just worked in the past. > But there are too many edge cases where pip installing a module can break system tools. > You would be unhappy if dnf broke. > > What I do is create one venv that I put the tools I pip install into then symlink the tools into my ~/bin. > OK > > On 2 Sep 2024, at 12:13, Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > > > For example, Proton is normally invoked by Steam or Wine, so does this > > mean I have to change those as well? > > Proton and Wine are not python modules so the python venv is not involved. I must have been thinking of 'protonup', a script I found somewhere that updates the version of Proton. I might just remove it, or use venv as you suggest. poc -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
