[🐛 Bug]: selenium.webdriver.support.ui.WebDriverWait vs selenium.webdriver.support.wait.WebDriverWait

[jkbzh]

Description

Hi,

I'm using selenium's py classes. Debian Trixie (13,5), inside venv with latest pip and libraries.

These two classes seem very close and I can't tell the difference on which cases one should be used over the other. The changelog doesn't mention that one will be deprecated.

Moreover the doc pages give the same examples for the until_not method, both using selenium.webdriver.support.ui

https://www.selenium.dev/selenium/docs/api/py/selenium_webdriver_support/selenium.webdriver.support.ui.html
https://www.selenium.dev/selenium/docs/api/py/selenium_webdriver_support/selenium.webdriver.support.wait.html

I'm not sure what's going on here. It's either a typo on the example for selenium.webdriver.support.wait.until_not or something else.

Would be good if the doc said what's the difference between both classes and in which cases, which class is more appropriate.

Reproducible Code

pydoc selenium.webdriver.support.ui.WebDriverWait
pydoc selenium.webdriver.support.wait.WebDriverWait
pydoc selenium.webdriver.support.ui.WebDriverWait.until_not
pydoc selenium.webdriver.support.wait.WebDriverWait.until_not

[selenium-ci]

@jkbzh, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[cgoldberg]

Hi @jkbzh

The classes are both the same.

The WebDriverWait class belongs to selenium.webdriver.support.wait. It is re-exported in the selenium.webdriver.support.ui namespace (I think to preserve backwards compatibility, I'm not really sure).

Moreover the doc pages give the same examples for the until_not method, both using selenium.webdriver.support.ui

I will update the examples in the docstrings to be more consistent (using selenium.webdriver.support.wait.WebDriverWait)

[cgoldberg]

@jkbzh updated examples will be in next release

[jkbzh]

thank you for the explanation and update!

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.