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
I would almost certainly agree with @shippy on this; the only reason not to do this is if we believe there's a race condition where selenium is being used by two threads simultaneously.
Realistically it would make more sense to create a destructor that ensures the process is killed after it goes out of scope - That way the process that launches it is responsible for killing it.
Right now, an error is raised with a specific command to run.
We always, always, always end up running the command.
Therefore, just running the call with
subprocess.run
/subprocess.Popen
could save a lot of time here.The text was updated successfully, but these errors were encountered: