Only the wheel is on pypi though.
I find an usable ebuild on github: https://github.com/enometh/enometh-overlay/blob/f964106af5a2824b37aed531eb81c0e5dba6ab53/dev-python/selenium/selenium-4.2.0.ebuild
It's not usable. It doesn't have tests. Furthermore, it's proprietary. Even if it was useful at all, we couldn't use it.
(In reply to Michał Górny from comment #2) > It's not usable. It doesn't have tests. > > Furthermore, it's proprietary. Even if it was useful at all, we couldn't > use it. fwiw, I do have a hacky ebuild for this, was really a hack job just for #gentoo-chromium testing
Created attachment 783005 [details] selenium-4.1.4.ebuild
(In reply to Sam James from comment #4) > Created attachment 783005 [details] > selenium-4.1.4.ebuild Yes, I've been thinking about doing something like that but I'm not sure whether it's worth the effort vs waiting for upstream to finally manage to make a working release. Should the pypi/github logic be the other way around there?
https://github.com/gentoo/gentoo/commit/83a4e16567756b4e741773a8ef4e89ca304883e7