-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
include a description of WORKFLOW_SHARE_DIR/bin and lib/python #609
include a description of WORKFLOW_SHARE_DIR/bin and lib/python #609
Conversation
add9c45
to
3543dee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small tweak suggested.
Co-authored-by: Hilary James Oliver <hilary.j.oliver@gmail.com>
Co-authored-by: Hilary James Oliver <hilary.j.oliver@gmail.com>
Co-authored-by: Hilary James Oliver <hilary.j.oliver@gmail.com>
These locations will be placed first in the executable and Python module | ||
search paths, before those in the parent run directory . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe
These locations will be placed first in the executable and Python module | |
search paths, before those in the parent run directory . | |
These locations take precedence over the top level ``bin/`` and | |
``lib/python/`` directories in the run dir. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wxtim and @MetRonnie - this kind of reverses my 2nd review suggestion above. I would prefer to just "state the facts" here, which is where these directories are put in the search paths. "Take precedence" or "called first" (Tim's original phrasing) could be assumed to have wider implications, e.g. for how Cylc itself somehow uses these locations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rather agree with Hilary - can we come to a conclusion @MetRonnie ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still got a build failure
…wxtim/cylc-doc into feature.support_share/bin_and_share/lib * 'feature.support_share/bin_and_share/lib' of github.com:wxtim/cylc-doc: Update src/user-guide/writing-workflows/runtime.rst Update src/user-guide/installing-workflows.rst Apply suggestions from code review Update src/user-guide/writing-workflows/runtime.rst Update src/user-guide/writing-workflows/runtime.rst Update src/user-guide/writing-workflows/runtime.rst Apply suggestions from code review add some extra links Update src/user-guide/writing-workflows/configuration.rst
Accompanies changes to cylc/cylc-flow#5525
Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.