Bsync import dependencies#221
Open
bsync wants to merge 3 commits into
Open
Conversation
Modified example to show the potential need for a 'nodeinit_setup' which executes immediately after it is serialized to the node. This feature means that classes like the class 'C' in the example can extend other python builtin classes like the 'cmd' class.
This allows strings of the form 'import <...>' to be added directly to the JobCluster 'depends' argument with the result that they are guaranteed to be inserted before all other depends items and prefixed to the compute.code that is serialized to the dispy nodes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small modification to directly support 'import <...>' type strings as JobCluster dependencies. They are always prefixed to the compute.code and serialized as is to the compute node(s).