Arch Linux User Repository

For now, I'm working around this by manually copying the js files into the webdriver/remote directory, so that they can be loaded when needed:

From the extracted tarball:

sudo cp rb/lib/selenium/webdriver/atoms/*.js /usr/lib/python3.12/site-packages/selenium/webdriver/remote/

I don't recommend doing this, but it seems to work for me (for now).

Any progress on getting the latest install to work, including get_attribute?

@carsme Thank you. I've got it updated and building. I updated .nvchecker.toml also to check on github, and download the selenium-x-python tags from github.

Is there any other kind of check you do besides just getting it to build and going through namcap logs?

@txtsd Of course, I'd love some help.

Can I have co-maintainer on this package, please? I'd like to take on the challenge of maintaining it.

I rolled back to python-selenium 4.22.0 after get_attribute() doesn't work anymore.

Does anyone have a working PKGBUILD, or an idea of what needs to be changed for this to work?

Update to 4.24.0-1 fails with

collect2: error: ld returned 1 exit status
= note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
= note: use the `-l` flag to specify native libraries to link
= note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#rustc-link-lib)
error: could not compile `selenium-manager` (bin "selenium-manager") due to 1 previous error

At the beginning of the update there were these warnings:

running egg_info
writing selenium.egg-info/PKG-INFO
writing dependency_links to selenium.egg-info/dependency_links.txt
writing requirements to selenium.egg-info/requires.txt
writing top-level names to selenium.egg-info/top_level.txt
reading manifest file 'selenium.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.py' under directory 'selenium/webdriver/common/html5'
warning: no files found matching '*.py' under directory 'selenium/webdriver/phantomjs'
warning: no files found matching '*.xpi' under directory 'selenium/webdriver/firefox'
warning: no files found matching '*.json' under directory 'selenium/webdriver/firefox'
warning: no files found matching '*.js' under directory 'selenium/webdriver/remote'
warning: no files found matching 'selenium/selenium.py'
warning: no files found matching 'selenium/webdriver/common/linux/selenium-manager'
warning: no files found matching 'selenium/webdriver/common/macos/selenium-manager'
warning: no files found matching 'selenium/webdriver/common/windows/selenium-manager.exe'
warning: no files found matching 'LICENSE'
writing manifest file 'selenium.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'selenium.webdriver.common.actions' is absent from the `packages` configuration.
!!
    ############################
    # Package would be ignored #
    ############################
    Python recognizes 'selenium.webdriver.common.actions' as an importable package[^1],
    but it is absent from setuptools' `packages` configuration.

    This leads to an ambiguous overall configuration. If you want to distribute this
    package, please make sure that 'selenium.webdriver.common.actions' is explicitly added
    to the `packages` configuration field.

    Alternatively, you can also rely on setuptools' discovery methods
    (for example by using `find_namespace_packages(...)`/`find_namespace:`
    instead of `find_packages(...)`/`find:`).

    You can read more about "package discovery" on setuptools documentation page:

    - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

    If you don't want 'selenium.webdriver.common.actions' to be distributed and are
    already explicitly excluding 'selenium.webdriver.common.actions' via
    `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
    you can try to use `exclude_package_data`, or `include-package-data=False` in
    combination with a more fine grained `package-data` configuration.

    You can read more about "package data files" on setuptools documentation page:

    - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


    [^1]: For Python, any directory (with suitable naming) can be imported,
          even if it does not contain any `.py` files.
          On the other hand, currently there is no concept of package data
          directory, all directories are treated like packages.
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'selenium.webdriver.common.bidi' is absent from the `packages` configuration.

It seems the new version of the package is missing files. Since update, I'm having the following issue:

Traceback (most recent call last):
  [...]
  File "/home/user/Projects/daemon/./main.py", line 225, in __init__
    self.url = element.find_element(by=By.CLASS_NAME, value="__icon").get_attribute("href")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/selenium/webdriver/remote/webelement.py", line 177, in get_attribute
    _load_js()
  File "/usr/lib/python3.12/site-packages/selenium/webdriver/remote/webelement.py", line 48, in _load_js
    getAttribute_js = pkgutil.get_data(_pkg, "getAttribute.js").decode("utf8")
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/pkgutil.py", line 453, in get_data
    return loader.get_data(resource_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap_external>", line 1186, in get_data
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3.12/site-packages/selenium/webdriver/remote/getAttribute.js'

The package should install required JS wrappings as well. As a workaround, I replaced all calls to get_attribute() with get_dom_attribute() in my application, but it probably won't be suitable for more complicated cases.

==> Making package: python-selenium 4.24.0-1 (Wed 04 Sep 2024 22:05:32 UTC)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found python-selenium-4.24.0.tar.gz
-> Found fix-selenium-manager-build.patch
==> Validating source files with sha256sums...
python-selenium-4.24.0.tar.gz ... Passed
fix-selenium-manager-build.patch ... Passed
==> Extracting sources...
-> Extracting python-selenium-4.24.0.tar.gz with bsdtar
==> Starting prepare()...
patching file py/setup.py
==> Starting build()...
/evrusnex/.espressif/python_env/idf5.3_py3.12_env/bin/python: No module named build
==> ERROR: A failure occurred in build().