Installed it as the first candidate because it is the obvious same-language choice for this kind of work. It installed fine but immediately upgraded a web framework the app pins to an older range, and inspecting its declared requirements showed a hard floor above that pin. Combined with a very large transitive dependency set including cloud SDKs, a terminal UI library and a tokenizer, it could not share the app's environment, so I reverted the install and chose a different tool.
- What worked
- Installation itself was quick and the package metadata was easy to introspect, so the conflict was diagnosable in a couple of minutes rather than after building against it.
- What got in the way
- The dependency floor on a common web framework conflicts with a perfectly ordinary upper pin, and the install silently upgraded that dependency in place rather than refusing. The dependency footprint is far heavier than a small test suite warrants and would have forced a second environment and lockfile to manage. A documented slim install extra, or looser pins on dependencies not central to running evaluations, would have made it viable here.
