docs/selenium_manager: mention about Python now supporting ENV for driver path (#2055)[deploy site]

* docs/selenium_manager: mention about Python now supporting ENV for driver path

* commit as what requested

---------

Co-authored-by: Sri Harsha <12621691+harsha509@users.noreply.github.com>

Author: Delta456

website_and_docs/content/documentation/selenium_manager.en.md

@@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
 It's possible to use an environment variable to specify the driver path without using Selenium Manager.
 The following environment variables are supported:
 
-* SE_CHROMEDRIVER
-* SE_EDGEDRIVER
-* SE_GECKODRIVER
-* SE_IEDRIVER
-* SE_SAFARIDRIVER
+* `SE_CHROMEDRIVER`
+* `SE_EDGEDRIVER`
+* `SE_GECKODRIVER`
+* `SE_IEDRIVER`
+* `SE_SAFARIDRIVER`
 
 For example, to specify the path to the chromedriver, 
 you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable.
 The following bindings allow you to specify the driver path using an environment variable:
 
 * Ruby
 * Java
+* Python
 
-This feature is available in the Selenium Ruby binding starting from version 4.25.0.
+This feature is available in the Selenium Ruby binding starting from version 4.25.0 and in the Python binding from version 4.26.0.
 
 ## Building a Custom Selenium Manager
 In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can

website_and_docs/content/documentation/selenium_manager.ja.md

@@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
 It's possible to use an environment variable to specify the driver path without using Selenium Manager.
 The following environment variables are supported:
 
-* SE_CHROMEDRIVER
-* SE_EDGEDRIVER
-* SE_GECKODRIVER
-* SE_IEDRIVER
-* SE_SAFARIDRIVER
+* `SE_CHROMEDRIVER`
+* `SE_EDGEDRIVER`
+* `SE_GECKODRIVER`
+* `SE_IEDRIVER`
+* `SE_SAFARIDRIVER`
 
 For example, to specify the path to the chromedriver,
 you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable.
 The following bindings allow you to specify the driver path using an environment variable:
 
 * Ruby
 * Java
+* Python
 
-This feature is available in the Selenium Ruby binding starting from version 4.25.0.
+This feature is available in the Selenium Ruby binding starting from version 4.25.0 and in the Python binding from version 4.26.0.
 
 ## Building a Custom Selenium Manager
 In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can

website_and_docs/content/documentation/selenium_manager.pt-br.md

@@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
 It's possible to use an environment variable to specify the driver path without using Selenium Manager.
 The following environment variables are supported:
 
-* SE_CHROMEDRIVER
-* SE_EDGEDRIVER
-* SE_GECKODRIVER
-* SE_IEDRIVER
-* SE_SAFARIDRIVER
+* `SE_CHROMEDRIVER`
+* `SE_EDGEDRIVER`
+* `SE_GECKODRIVER`
+* `SE_IEDRIVER`
+* `SE_SAFARIDRIVER`
 
 For example, to specify the path to the chromedriver,
 you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable.
 The following bindings allow you to specify the driver path using an environment variable:
 
 * Ruby
 * Java
+* Python
 
-This feature is available in the Selenium Ruby binding starting from version 4.25.0.
+This feature is available in the Selenium Ruby binding starting from version 4.25.0 and in the Python binding from version 4.26.0.
 
 ## Building a Custom Selenium Manager
 In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can

website_and_docs/content/documentation/selenium_manager.zh-cn.md

@@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
 It's possible to use an environment variable to specify the driver path without using Selenium Manager.
 The following environment variables are supported:
 
-* SE_CHROMEDRIVER
-* SE_EDGEDRIVER
-* SE_GECKODRIVER
-* SE_IEDRIVER
-* SE_SAFARIDRIVER
+* `SE_CHROMEDRIVER`
+* `SE_EDGEDRIVER`
+* `SE_GECKODRIVER`
+* `SE_IEDRIVER`
+* `SE_SAFARIDRIVER`
 
 For example, to specify the path to the chromedriver,
 you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable.
 The following bindings allow you to specify the driver path using an environment variable:
 
 * Ruby
 * Java
+* Python
 
-This feature is available in the Selenium Ruby binding starting from version 4.25.0.
+This feature is available in the Selenium Ruby binding starting from version 4.25.0 and in the Python binding from version 4.26.0.
 
 ## Building a Custom Selenium Manager
 In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can