https://pantsbuild.org/ logo
Join Slack
Powered by
How would one resolve this warning? Ignore it or r...
# general
l
How would one resolve this warning? Ignore it or request the lib maintainers not bundle the changelog at the root of their wheel?
Copy code
/vscode/userdata/cache/pants/named_caches/pex_root/installed_wheels/735ba74cef654ed9306ec06e9e2d860eca7ef7df89bb666e69046a64904b4300/pex-2.1.108-py2.py3-none-any.whl/pex/venv/pex.py:159: PEXWarning: Encountered collision building venv at /workspace/dist/export/python/virtualenvs/web-api/3.9.10 from /workspace/dist/export/python/virtualenvs/web-api/requirements.pex:
1. /workspace/dist/export/python/virtualenvs/web-api/3.9.10/lib/python3.9/site-packages/CHANGELOG.md was provided by:
        sha1:d19fd146bc7b13765d84651aea1afc8b6dc1718d -> /vscode/userdata/cache/pants/named_caches/pex_root/installed_wheels/ad37842ebe4ff72284a172ee2335245d39fde8354e98b6e7988522572a0e96db/starlite-1.39.0-py3-none-any.whl/CHANGELOG.md
        sha1:e8c7347384dee66012b97aaed18c89c2198fdf85 -> /vscode/userdata/cache/pants/named_caches/pex_root/installed_wheels/04e1f125cb28cbe745f2fece4bd2b419786395dc7efabac74fe037dc5397490a/pydantic_factories-1.15.0-py3-none-any.whl/CHANGELOG.md
        sha1:f25fed786169c77f6d35521d93a04bb2d3151a38 -> /vscode/userdata/cache/pants/named_caches/pex_root/installed_wheels/37a264596a3cd0c2627cf98e22fbf1231e76c19cd83c536d847fa17a2e80c211/pydantic_openapi_schema-1.3.0-py3-none-any.whl/CHANGELOG.md
        sha1:9dfd6f3e588c7fd52b3be2f57483e45dccaa7d1c -> /vscode/userdata/cache/pants/named_caches/pex_root/installed_wheels/ceb5667d6c58bcbc305d5922ead791f0b50f0b9f658747144577a3dccffc5335/starlite_multipart-1.2.0-py3-none-any.whl/CHANGELOG.md
  pex_warnings.warn(message)
h
In an ideal world, yes. These files are all racing to write to 
site-packages/CHANGELOG.md
and that is objectively an error. This page explains as much: https://jwodder.github.io/kbits/posts/pypkg-mistakes/#top-level-readme-or-license-file-in-wheel
Pex could accept that this specific example is a common error and squelch the warning, but I’m not sure that’s wise, since this is pointing out a real issue with these dists, even if in practice it probably doesn’t matter
l
Sorry for the delay. That makes sense to me. Thanks!
5 Views
Open in Slack
PreviousNext
Powered by