Package Details: python-selenium 4.30.0-1

Git Clone URL: https://aur.archlinux.org/python-selenium.git (read-only, click to copy)
Package Base: python-selenium
Description: Python language bindings for Selenium WebDriver
Upstream URL: https://github.com/SeleniumHQ/selenium
Licenses: Apache-2.0
Submitter: jelly
Maintainer: carsme (txtsd)
Last Packager: txtsd
Votes: 37
Popularity: 1.82
First Submitted: 2022-01-23 14:41 (UTC)
Last Updated: 2025-03-25 03:53 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

medaminezghal commented on 2025-03-22 14:12 (UTC)

I think you should add selenium-manager as optional dependency.

txtsd commented on 2025-03-04 05:15 (UTC)

@Sukolyn Builds for me in and out of chroot. Try rustup updateing your rust version. makepkg -c cleans up after a build btw, for a clean build you want makepkg -C.

Sukolyn commented on 2025-03-03 17:05 (UTC) (edited on 2025-03-03 17:13 (UTC) by Sukolyn)

I have a lot of error simply entering makepkg -c :

error: could not compile `autocfg` (lib)
Caused by:
process didn't exit successfully: `rustc --crate-name autocfg --edition=2015 /home/sukolyn/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/autocfg-1.3.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=121 --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=2ba0a37b04727790 -C extra-filename=-0f99bcb19efed741 --out-dir /home/sukolyn/aur/python-selenium/src/selenium-4.29.0/target/release/deps -C strip=symbols -L dependency=/home/sukolyn/aur/python-selenium/src/selenium-4.29.0/target/release/deps --cap-lints allow -Cforce-frame-pointers=yes -C debuginfo=2 --remap-path-prefix=/home/sukolyn/aur/python-selenium/src=/usr/src/debug/python-selenium` (signal: 7, SIGBUS: access to undefined memory)
warning: build failed, waiting for other jobs to finish...

error: could not compile `getrandom` (lib)
[...] `stable_deref_trait` (lib), `proc-macro2` (lib), jobbserver` (lib), `pkg-config` (lib), `memchr` (lib), `bytes` (lib)
[...]
ERROR Backend subprocess exited when trying to invoke build_wheel

drfear commented on 2025-03-02 16:16 (UTC)

After fresh install, on attempt to open any driver,

File "/usr/lib/python3.13/site-packages/selenium/webdriver/common/selenium_manager.py", line 99, in _get_binary
    raise WebDriverException(f"Unable to obtain working Selenium Manager binary; {path}")
selenium.common.exceptions.WebDriverException: Message: Unable to obtain working Selenium Manager binary; /usr/lib/python3.13/site-packages/selenium/webdriver/common/linux/selenium-manager

Fix: create the linux subdirectory just mentioned and in there create 'selenium-manager' as a link to /usr/bin/selenium.webdriver.common.selenium-manager

txtsd commented on 2025-02-03 13:21 (UTC)

Thanks @kbipinkumar!

I incorporated your patches and also added you as a contributor.

kbipinkumar commented on 2025-02-01 15:38 (UTC)

apparently the error was introduced in the upstream by this pull request. i have attempted to revise the PKGBUILD with fixes as suggested here

the revised PKGBUILD can be found here. i am able to build the package with revised PKGBUILD in clean chroot

txtsd commented on 2025-02-01 13:58 (UTC)

@kbipinkumar Any ideas on how to fix it?

kbipinkumar commented on 2025-02-01 07:24 (UTC)

building with version 4.28.1 from upstream fail with following error

running build_ext
running build_rust
cargo rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib --
error: the package 'selenium-manager' does not contain this feature: pyo3/extension-module
error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib --` failed with code 101

txtsd commented on 2025-01-20 15:50 (UTC)

@Xeonacid We've tried that and ended up with missing files.

Xeonacid commented on 2025-01-20 11:43 (UTC)

According to RFC, it is better to move to the GitHub source tarball instead of the PyPI source.

1 2 3 4 5 6 .. 8 Next › Last »