You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The title might be a bit confusing, but what i'm referring to is how some python scripts are ran in a subshell, even though they could be used as regular python modules.
Is something that is present A LOT in the web.py file, but i fail to understand why even do that if you can create a job in the python that executes code, instead of opening a shell as a subprocess.
I assume this will be fixed when the RVC becomes a module, however I'll prefer fixing this sooner than later.
Opening a subshell and executing a python script adds a huge amount of overhead and introduces extreme amounts of security vulnerabilities, shell=True is one of the culprits for that in particular.
Also, the code will look just more appealing without all of the subprocess creation within shells and all the yields of the stdout as a generator for gradio interface to update properly
The text was updated successfully, but these errors were encountered:
The title might be a bit confusing, but what i'm referring to is how some python scripts are ran in a subshell, even though they could be used as regular python modules.
Is something that is present A LOT in the web.py file, but i fail to understand why even do that if you can create a job in the python that executes code, instead of opening a shell as a subprocess.
I assume this will be fixed when the RVC becomes a module, however I'll prefer fixing this sooner than later.
Opening a subshell and executing a python script adds a huge amount of overhead and introduces extreme amounts of security vulnerabilities,
shell=True
is one of the culprits for that in particular.Also, the code will look just more appealing without all of the subprocess creation within shells and all the yields of the
stdout
as a generator for gradio interface to update properlyThe text was updated successfully, but these errors were encountered: