Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"package_definition_build_python_paths" defined paths are not available from top level in "package.py" #433

Closed
KelSolaar opened this issue Jun 1, 2017 · 1 comment
Closed

"package_definition_build_python_paths" defined paths are not available from top level in "package.py" #433

KelSolaar opened this issue Jun 1, 2017 · 1 comment

Comments

@KelSolaar
Copy link
Contributor

As described in #426 (comment), adding a path to package_definition_build_python_paths in the config file does not expose it to package.py top level, i.e. it is not added to sys.path and you cannot import any module under the added path.
nerdvegas pushed a commit that referenced this issue Dec 13, 2018
addresses #433
e540560
@nerdvegas nerdvegas mentioned this issue Dec 13, 2018
Merged
@nerdvegas
Copy link
Contributor

https://github.com/nerdvegas/rez/releases/tag/2.25.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KelSolaar @nerdvegas