pex files with different content gets same stamp about python-rules HOT 5 OPEN

Also, it's worth stating that my pex is big enough that using PEX_NOCACHE is not an option (and it would be a terrible UX for my users)

from python-rules.

What I think I'd like to do, is to use that content hash of the "_%s#lib" sub-target

from python-rules.

Hum... This is sadly not a fixed problem. Something is wrong with my implementation, and your input, dear @samwestmoreland would be welcomed.

So this works when the content of the sources of the python_binary get modified, but not when the files of dependent python_libraries are changed.

from python-rules.

Do you think it could work to split the last rule which gathers everything in two ?

• One that would gather all the .pex.zip, .wheel and resources
• One that would add the preamble and produce the final pex

We would then be able to put the rule which inject the stamp in the pex in the middle and it would have all the resources available to compute a proper hash.

Do you think it could work ?

from python-rules.

Hey, right I see. Yeap, I think that sounds very reasonable. You essentially want to figure out everything you need that you want to be in the hash, i.e. the deps and the lib_rule, and build them beforehand in order to generate the stamp. Are you happy to create the PR? I can help out if you get stuck!

from python-rules.