-
Notifications
You must be signed in to change notification settings - Fork 24
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
ENH: annotate graph edges as optionals #20
Conversation
Usefull when 2 (or more) operations provifing the same output, and only one has fully satisfied inputs. Before it would fail trying to evaluate the un-satisfied ones. + New TC added. .
were writing in text-mode in PY3. and failing as encoding error.
Codecov Report
@@ Coverage Diff @@
## master #20 +/- ##
=========================================
+ Coverage 77.87% 78.3% +0.43%
=========================================
Files 5 5
Lines 348 355 +7
=========================================
+ Hits 271 278 +7
Misses 77 77
Continue to review full report at Codecov.
|
My mistake, this enhancement is not needed. Will scavenge TC. |
+ enh TC with parallel. + Scavenged from yahoo#20.
Eventually merged. |
but still annotate edges with optional edge data-attribute. Reverted bc Operation must not know its network, to belong to more than one. Also the `Operation.net` contradicted `NetwotkOperation.net`; the later indeed is the network it wraps (not the net it is part of).
but still annotate edges with optional edge data-attribute. Reverted bc Operation must not know its network, to belong to more than one. Also the `Operation.net` contradicted `NetwotkOperation.net`; the later indeed is the network it wraps (not the net it is part of).
optional
with theneed <-- operation
edge (instead of only on theneed
node).I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.