@vitor Thank you so much for getting back to me and helping me with this question.
Forgive me for maybe using the wrong terminology before. I am not a programmer, and still trying to learn these things.
"Globally", was probably the more proper term for what I was asking than "system-wide", although I am glad that Workflows cannot make changes system-wide.
When you say it cannot install the libraries system-wide, is that different from installing libraries globally, or global libraries/environments? (I may be wrong again, but would global usually mean locations like "/usr/local/bin/" for Mac?)
If different, will Workflows potentially be able to install libraries globally (again I apologize if my terminology is inaccurate)
I am very glad to hear that those things haven't happened.
Maybe I'm just paranoid, but when learning how to set up virtual environments, I was told repeatedly to be very careful with installing libraries globally.
Great to know this.
I should have thought to show package content. I have been able to locate it now, but the right clicking from Alfred preferences is actually a big help(to find the actual workflow, because the name can be scrambled)
Thank you very much! Very useful.
This is great. So it sounds like an isolated environment inside the workflow directory.
I'm glad that if setup this way It can simply be deleted with the workflow, also meaning the libraries shouldn't affect my system, and very easy to manage for users. Especially people like me that don't understand code as much.
You say "that's how it should be done" though, so a workflow may be setup another way? If so, is there a way to know if a Workflow has been setup this way? Or is the only way to know by going through the code and checking yourself?
Also this may be a little unrelated, but generally speaking, if the access permission of the Alfred app to the terminal disabled, will that affect how workflows work?
Thank you!