jolly-midnight-72759
06/03/2021, 4:26 PM.pex/install
and .pex/code
. A new pex I am trying to deploy is failing on not being able to find something on a path that includes .pex/installed_wheels/
. The only recent change I can think of is we recently updated to v2.2.3
of pants.happy-kitchen-89482
06/03/2021, 10:03 PMjolly-midnight-72759
06/03/2021, 10:06 PMPEX-INFO
for two different hashes of the same target package:
189c203,208
< "zip_safe": false
---
> "strip_pex_env": true,
> "unzip": false,
> "venv": false,
> "venv_bin_path": "False",
> "venv_copies": false,
> "zip_safe": true
(older on left, newer on right)happy-kitchen-89482
06/04/2021, 4:06 PMjolly-midnight-72759
06/04/2021, 9:01 PMsettings.py
to be pex 🧠 .enough-analyst-54434
06/10/2021, 2:26 PMzip_safe=False
in the corresponding BUILD target?
+ "we ended up solving this by changing the django loader in settings.py
to be pex" - Pex has no explicit Django integrations so I'm not sure what this means. Does Django have a concept of a "pex" loader?jolly-midnight-72759
06/10/2021, 2:55 PMpkgutil
to load the Django templates.enough-analyst-54434
06/10/2021, 3:08 PMjolly-midnight-72759
06/10/2021, 4:07 PMzip_safe=False
AND had the regular Django file system loader it worked. When we removed the regular Django loader and just used our pex loader, we could remove the setting (i.e. not set zip_safe
) like it was before.PEX_INFO
our pex's were being built with zip_safe=False
and that changed to True
even though it was not set in our BUILD
file (before or later). I assume something happened in our upgrade from v1 to v2 that caused this change and we missed it for this legacy code.enough-analyst-54434
06/10/2021, 4:27 PMpython_binary
target depending directly or indirectly on a python_requirement_library
generated via the python_requirements
macro marked as zip_safe=False
. So the default for python_binary
was the same as now for `pex_binary`; i.e.: `zip_safe=True`; it's just that the 99.9% use case of having that binary depending on a 3rdparty requirement defined via requirements.txt happend to flip that to False
. We no longer do that.