I am puzzled by your response.
If I create a new virtualenv, run "pip install selenium" in it, and then
run "python3 -c 'import selenium.webdriver;
selenium.webdriver.Chrome()'", it just works, right out of the box. That
is clearly the intent of the vendor of the PyPI package. Quoting from
the Selenium Manager Documentation (
https://www.selenium.dev/documentation/selenium_manager/ ): "Selenium
bindings use this tool by default, so you do not need to download it or
add anything to your code or do anything else to use it. ... Selenium
Manager is the official driver manager of the Selenium project, and it
is shipped out of the box with every Selenium release." They have
clearly and explicitly stated that their intention is for the Selenium
Manager to be packaged with the Python driver.
The main intent of Selenium Manager is to make code that uses one of the
drivers to work out of the box without changes on more platforms. The
workaround you are telling people to use in the README explicitly
countermands that intent by telling people trying to use the Selenium
Python driver on Debian that they need to put in custom code that will
be incompatible with any other platform.
If the vendor had intended for Selenium Manager to be an optional
component of the driver, then trying to use the driver when it's not
present wouldn't cause an unintelligible stack trace, it would revert to
the previous behavior. That is clearly not their intent (and they've
said as much, explicitly).
Finally, by failing to package Selenium Manager with the Python driver
as the vendor intends, you have caused a clear, explicit regression,
i.e., code which previously worked just fine has suddenly stopped
working due to what I am arguing is simply a packaging error.
You don't even have to compile Selenium Manager to include it in the
package. It's already embedded in the pip package and all you need to do
is include the file in the deb along with the other files you're already
including.
It's just quite puzzling to see someone claiming that leaving out of the
deb a component that the vendor intended to be included, and thereby
causing the package to stop working for everyone trying to use it, is
the correct behavior and no fix is required.
