Sorry for the rapid fire, but I got a new thing af...
# general
h
Sorry for the rapid fire, but I got a new thing after upgrading to 2.15 that I'm not really sure how to interpret.
Copy code
$ ./pants export --resolve=python-default
17:05:46.14 [INFO] Initializing scheduler...
17:05:46.96 [INFO] Scheduler initialized.
17:06:18.04 [INFO] Completed: chosen_resolve.name
17:06:21.26 [INFO] Completed: Get interpreter version
/home/nathanael/.cache/pants/named_caches/pex_root/installed_wheels/71c50e03e63506d9e56add7cd5a4d6bb9fcc7985f39e7d2e152233fc4d6fd74d/pex-2.1.111-py2.py3-none-any.whl/pex/dist_metadata.py:397: PEXWarning: Ignoring 1 `Requires` field in /home/nathanael/.cache/pants/named_caches/pex_root/unzipped_pexes/74f3628ae4574df8984c577d64332d800d17ae01/.deps/sockjs_tornado-1.0.7-py3-none-any.whl metadata:
1.) Requires: tornado

You may have issues using the 'sockjs-tornado' distribution as a result.
More information on this workaround can be found here:
  <https://github.com/pantsbuild/pex/issues/1201#issuecomment-791715585>

  pex_warnings.warn(
Wrote mutable virtualenv for python-default (using Python 3.8.10) to dist/export/python/virtualenvs/python-default
I don't really get what's special about this package and exporting it.
setup.py
for the project looks normal and I don't see how it relates to the linked comment.
Oh, maybe I kind of see now
Is it possible to suppress this warning?
e
With
pex
... yes:
--no-emit-warnings
, but within Pants there would be more involved. If the dependency is direct, you might just fix it. Fork the repo, fix setup.py and use a VCS requirement.
And, of course!, try to get upstream to accept the fix.
There is the env var knob too, but to use that you'd have to punch through
[subprocess-environment]
, and that's a pretty broad brush / big hammer: https://pex.readthedocs.io/en/v2.1.123/api/vars.html#PEX_EMIT_WARNINGS