It it possible to make

python_tests

use the virtualenv instead of pex?

It already is using a venv. All PEXes Pants builds internally use the Pex

--venv

mode. That mode creates a venv (using

python -mvenv ...

), populates it with the contents of the PEX and runs from there. Are you seeing unexpected behavior?

It takes about 25-50 seconds to run a single test, it seems to building a pex file

Ok. There are two things to track down: 1. Is that 'Building requirements.pex ...' happening more often than expected? It should only happen when requirements are edited. 2. Is that time markedly different from a Pip resolve of the same requirements?

I have tried to use a lock file, but I can’t seem to make it work. We have a big lock file (~410 packages) and pants doesn’t finish locking them even though they are fully locked (e.g. exported from poetry)

Aha - ok, that needs to be solved then.

It usually hangs, but when it finally finished creating the

repository.pex

I’m getting

OSError: [Errno 36] File name too long:

on this call stack

ProcessExecutionFailure: Process 'Extracting urllib3==1.26.7; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.6.0" and python_version < "4" or python_full_version >= "3.5.3" and python_version < "4" or python_full_version >= "3.5.0" and python_version < "4" from repository.pex' failed with exit code 1.
stdout:

stderr:
Traceback (most recent call last):
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.bootstrap/pex/pex.py", line 483, in execute
    exit_value = self._wrap_coverage(self._wrap_profiling, self._execute)
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.bootstrap/pex/pex.py", line 401, in _wrap_coverage
    return runner(*args)
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.bootstrap/pex/pex.py", line 432, in _wrap_profiling
    return runner(*args)
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.bootstrap/pex/pex.py", line 539, in _execute
    return self.execute_entry(self._pex_info.entry_point)
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.bootstrap/pex/pex.py", line 655, in execute_entry
    return self.execute_pkg_resources(entry_point)
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.bootstrap/pex/pex.py", line 687, in execute_pkg_resources
    return runner()
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.deps/pex-2.1.44-py2.py3-none-any.whl/pex/bin/pex.py", line 1159, in main
    pex_builder.build(
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.deps/pex-2.1.44-py2.py3-none-any.whl/pex/pex_builder.py", line 651, in build
    with safe_open(tmp_zip, "ab") as pexfile:
  File "/home/ubuntu/.cache/pants/named_caches/pex_root/unzipped_pexes/592827b562c4aa09c1e9af6b3ed7b797eef1a4dc/.deps/pex-2.1.44-py2.py3-none-any.whl/pex/common.py", line 282, in safe_open
    return open(filename, *args, **kwargs)  # noqa: T802

Aha - ok, that method of resolution / building internal PEXes was very short lived, Are you in a position to try upgrading to 2.7.1?: https://pypi.org/project/pantsbuild.pants/2.7.1

@enough-analyst-54434 what’s the current recommended version of pants?

The latest stable is always a good bet and that happens to be 2.7.1: https://pypi.org/project/pantsbuild.pants/#history

2.7.0

but I’m doing a PoC so I can use any version which you think will make my journey better

Yeah - please try 2.7.1. The 0 -> 1 contains an important change to requirement handling mostly encapsulated here: https://github.com/pantsbuild/pants/pull/13078

OK, now it works 😐

Excellent.