You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have my rezconfig.py set package_definition_python_path="/path/to/shared/code" and I include the shared module with include decorator for my package's commands function.
The included module was copied correctly into {package.root}/.rez/include directory when I run rez-build --install. But the installed package not able to pick up the correct copy of include module after I re-build with source have changed.
Cause
I found that it was because the copied shared module was named with hash string, which is fine but then Rez did not pick the right one, only the first one it globed.
Maybe we could drop naming shared module with hash string ? Just hash it again when trying to access them.
I'll try submit a PR as a proposal of solution.
The text was updated successfully, but these errors were encountered:
Problem
I have my
rezconfig.py
setpackage_definition_python_path="/path/to/shared/code"
and I include the shared module withinclude
decorator for my package'scommands
function.The included module was copied correctly into
{package.root}/.rez/include
directory when I runrez-build --install
. But the installed package not able to pick up the correct copy of include module after I re-build with source have changed.Cause
I found that it was because the copied shared module was named with hash string, which is fine but then Rez did not pick the right one, only the first one it
glob
ed.https://github.com/nerdvegas/rez/blob/f81c721c079abe99746dce80853da45351a2b683/src/rez/utils/sourcecode.py#L324-L328
Maybe we could drop naming shared module with hash string ? Just hash it again when trying to access them.
I'll try submit a PR as a proposal of solution.
The text was updated successfully, but these errors were encountered: