I’m running into issues running fmt2. The pex reso...
# general
f
I’m running into issues running fmt2. The pex resolution is having problems. I think it has to do with python2/3 issues. I’ll thread my output
Copy code
Failed to execute PEX file. Needed macosx_10_14_x86_64-cp-37-cp37m compatible dependencies for:
 1: docformatter==1.3.1
  But this pex only contains:
   docformatter-1.3.1-py2-none-any.whl
 2: untokenize==0.1.1
  But this pex only contains:
   untokenize-0.1.1-py2-none-any.whl

)
      Traceback (most recent call last):
       File "/Users/nhoward/Workspace/pants/src/python/pants/engine/native.py", line 288, in call
        val = func(*args)
       File "/Users/nhoward/Workspace/pants/src/python/pants/engine/isolated_process.py", line 195, in fallible_to_exec_result_or_raise
        description.value,
      pants.engine.isolated_process.ProcessExecutionFailure: process 'Run docformatter for src/python/pants/backend/jvm/tasks:scalafmt' failed with exit code 1.
      stdout:

      stderr:
      Failed to execute PEX file. Needed macosx_10_14_x86_64-cp-37-cp37m compatible dependencies for:
       1: docformatter==1.3.1
        But this pex only contains:
         docformatter-1.3.1-py2-none-any.whl
       2: untokenize==0.1.1
        But this pex only contains:
         untokenize-0.1.1-py2-none-any.whl
It looks like pex resolved the dependencies as py2, but verifies for py3.7
I worked around it by re-adding isort v1 to fmt, but that’s awkward
I wish the isort output in the self check failures was more descriptive
e
@fancy-queen-20734 I think that's this bug in Pex: https://github.com/pantsbuild/pex/issues/898 That's next on my queue.