Control: tags -1 severity normal Hello Jonathan,
Am Wed, Sep 06, 2023 at 04:37:28PM -0400 schrieb Jonathan Kamens: > Opening a new ticket since bug 1050378 is resolved and I don't know > how to reopen a resolved ticket (nor do I know if it is even possible > for me to reopen a resolved ticket). https://www.debian.org/Bugs/server-control#reopen if you use 'bts' this would become the following CLI command: $ bts 1050378 reopen If you prefer to use a MTA ensure to include the following line at the very beginning of the body. reopen 1050378 > python3-selenium 4.12.0+dfsg-1 still doesn't work. > > I get this when I try to create a selenium.webdriver.Chrome object: > > selenium.common.exceptions.NoSuchDriverException: Message: Unable to obtain > driver for chrome using Selenium Manager.; For documentation on this error, > please visit: > https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location > > The ChangeLog for this release claims: > > * [5b22b76] d/README.Debian: Add section about the Selenium Manager > * [25b0d5f] d/NEWS moved to d/python-selenium.NEWS > (Closes: #1050378) > > But neither of those files exists in the python3-selenium package. Was > there an intention to add them to the package that wasn't followed > through on? This is indeed a issue, both file should be within the package python3-selenium but are not in 4.12.0-1. This slipped somehow through. The file are moved now into the correct binary package. > Incidentally, I took a look at README.Debian in the source package and > there are some issues with the text that may be worth fixing as well. > In particular: > > >While writing it's not packaged for Debian. In order to make python3-selenium > > I suggest changing "While writing" (which is not really an idiom that > is used in English) to "At this time". > > >usable with this new circumstance you will need to adjust your source in a > >way to choose the used driver directly and skip the calling of the manager > >code in Selenium. Please have a look at the following example how to archive > > I think you mean to say "achieve" here rather than "archive". Correct, I'm not a native english speaking person and all spelling and grammar tools do not not detect all common mistakes, I fixed the relevant parts which will get included in a next upload. > In any case I do not believe that documenting this deficiency in > README.Debian, even if/when it is included in the package, is a > sufficient fix for the issue. The issue IMO should remain unresolved > until Selenium Manager is properly packaged for Debian. And then? Who will package the required package? I'm not tend to do this. And adding at minimum two lines of additional code to your project/code/application that is intended to be running on a Debian system isn't a big thing to me. If you rely on Selenium Manager you should fill a RFP issue I suggest. If you think the problem (and also the possible solutions) aren't well enough explained and to less documentation is provided how to work around the new requirement for Selenium Manager is now needed as a middle layer we are happy to get suggestions and text snippets how this can be improved. To find out how to set the driver interface manually instead by the Selenium Manager took me about 30min on searching with my preferred search engine. I'm sure others will be able to find quite the same in a similar time. So no, I don't think your report is of severity grave nor is python3-selenium within Debian not working currently. Regards Carsten
