Failing to find local editable package from `pylock.toml` for pex >= 2.91.0

[Lauszus]

I use uv to export the uv.lock to a pylock.toml for one of my projects.

I then use pex with the --pylock argument to create a PEX given the pylock.toml.

This has worked great since you introduced support for pylock.toml initially, but broke in pex >= 2.91.0 with the following error:

pex.pex_builder.PEXBuilder.InvalidExecutableSpecification: Could not find script 'hello' in any distribution a 1.0, b 1.0.0 within PEX!
Could not find script 'hello' in any distribution a 1.0, b 1.0.0 within PEX!

I believe this is because my package relies on another local package like so:

dependencies = [
    "a",
]

[tool.uv.sources]
a = { path = "../a", editable = true }

I have create a repository for replicating the issue: https://github.com/Lauszus/pex-pylock-bug/tree/main

Let me know if you need any more information

[jsirois]

Thanks for the report @Lauszus. I'll get this fixed up today.

That said, this may not be what you want to be doing. This works and slightly in my testing:

diff --git a/Makefile b/Makefile
index 8c16b21..51486f5 100644
--- a/Makefile
+++ b/Makefile
@@ -5,9 +5,12 @@ PACKAGE ?= b
 UV_EXPORT_CMD = uv --directory $(PACKAGE) --quiet \
        export --format pylock.toml --output-file pylock.toml --no-dev
 
+UV_VENV_CMD = uv --directory $(PACKAGE) --quiet \
+       sync
+
 PEX_ARGS = \
        -v \
-       --pylock $(PACKAGE)/pylock.toml \
+       --venv-repository $(PACKAGE)/.venv \
        -o $(PACKAGE).pex \
        -c hello
 
@@ -16,7 +19,7 @@ works:
        uvx pex@2.90.3 $(PEX_ARGS)
 
 bug:
-       $(UV_EXPORT_CMD)
+       $(UV_VENV_CMD)
        uvx pex@2.91.0 $(PEX_ARGS)
 
 latest:

[Lauszus]

Thanks for the report @Lauszus. I'll get this fixed up today.

That said, this may not be what you want to be doing. This works and slightly in my testing:

diff --git a/Makefile b/Makefile
index 8c16b21..51486f5 100644
--- a/Makefile
+++ b/Makefile
@@ -5,9 +5,12 @@ PACKAGE ?= b
UV_EXPORT_CMD = uv --directory $(PACKAGE) --quiet
export --format pylock.toml --output-file pylock.toml --no-dev

+UV_VENV_CMD = uv --directory $(PACKAGE) --quiet \

•   sync
  

PEX_ARGS =
-v \

•   --pylock $(PACKAGE)/pylock.toml \
  

•   --venv-repository $(PACKAGE)/.venv \
    -o $(PACKAGE).pex \
    -c hello
  

@@ -16,7 +19,7 @@ works:
uvx pex@2.90.3 $(PEX_ARGS)

bug:

•   $(UV_EXPORT_CMD)
  

•   $(UV_VENV_CMD)
    uvx pex@2.91.0 $(PEX_ARGS)
  

latest:

Thanks for the quick reply. Is there any downside to use --venv-repository?

I kind of like using the pylock.toml, as I set the pex platform to manylinux_2_28_x86_64-cp-314-cp314/manylinux_2_31_armv7l-cp-314-cp314 and then build the PEX files in manylinux Docker images, so it can build wheels if necessary.

But I guess I could just build the venv using uv and then use PEX to bundle it.

[jsirois]

Is there any downside to use --venv-repository?

On the contrary - there should only be upside. I added the feature to avoid Pip altogether as well as the shortcomings of pylock.toml - which was a deliberately neutered PEP. The minute you add 3rd party dependencies to your example / real use, you should find --venv-repository is much faster and it does not suffer the loss of fidelity of the pylock.toml middle-man lock. Also, you can handle foreign platforms with uv + --venv-repository and not have to resort to containers (IFF you don't need to build wheels - uv also cannot cross-build, but it fails to do so silently IIRC and just plops a native wheel in the foregin platform venv you asked it to build!). I give an example of that here: pantsbuild/pants#23197 (comment)

[Lauszus]

Okay I will give it a go.

Note I need to build some wheels for armv7l, but that is not a problem, as I can just do it in Docker.

[jsirois]

Interesting, it appears to boil down to this:

diff --git a/Makefile b/Makefile
index 8c16b21..3a9dd4e 100644
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@ UV_EXPORT_CMD = uv --directory $(PACKAGE) --quiet \
 
 PEX_ARGS = \
        -v \
-       --pylock $(PACKAGE)/pylock.toml \
+       --pylock `realpath $(PACKAGE)/pylock.toml` \
        -o $(PACKAGE).pex \
        -c hello

When setting up a failing IT to start things off, I had an exact replica of your example repo and the test passed! It was not until I switched to using cwd=... and relative paths that I could simulate failure.

[Lauszus]

Interesting, it appears to boil down to this:

diff --git a/Makefile b/Makefile
index 8c16b21..3a9dd4e 100644
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@ UV_EXPORT_CMD = uv --directory $(PACKAGE) --quiet \
 
 PEX_ARGS = \
        -v \
-       --pylock $(PACKAGE)/pylock.toml \
+       --pylock `realpath $(PACKAGE)/pylock.toml` \
        -o $(PACKAGE).pex \
        -c hello

When setting up a failing IT to start things off, I had an exact replica of your example repo and the test passed! It was not until I switched to using cwd=... and relative paths that I could simulate failure.

Okay interesting. I've already migrated to using --venv-repository and it works a charm :)

[jsirois]

@Lauszus excellent. That should be faster and more robust.

That said, thanks for finding this issue and creating the example repo - that made things very easy to track down. I really appreciate it. The fix should be out later today: #3140

[jsirois]

Fixed in: https://github.com/pex-tool/pex/releases/tag/v2.91.8