224640 2021-04-15 19:00:39 -0700 Investigate using tox for testing Python code 2025-10-24 14:40:25 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED WONTFIX https://bugs.webkit.org/show_bug.cgi?id=224638 InRadar P2 Normal --- 224869 226016 261004 1 gsnedders webkit-unassigned ap don.olmstead jbedard webkit-bug-importer oldest_to_newest 1750892 0 gsnedders 2021-04-15 19:00:39 -0700 c.f. https://tox.readthedocs.io/en/latest/ Whether we care about this probably varies a bit; webkitcorepy etc. are in principle installable via pip so testing them via virtualenvs (therefore in isolated environments) would have some value. However, the larger value in my book would be able to run tests against multiple supported Python versions in a single command. That said, this is a relatively small benefit compared with the other benefits many get from it. 1750893 1 webkit-bug-importer 2021-04-15 19:00:48 -0700 <rdar://problem/76736746> 2154145 2 gsnedders 2025-10-24 14:40:25 -0700 I think at this point we're better off going with nox, which is configured with actual Python code, as this allows us to easily maintain a singular entry-point (i.e., test-webkitpy) which runs everything.