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: Avoid loading result from file when writing reports #3024
Conversation
746632c
to
fe354b8
Compare
Codecov Report
@@ Coverage Diff @@
## master #3024 +/- ##
==========================================
- Coverage 67.52% 64.13% -3.39%
==========================================
Files 344 342 -2
Lines 44045 43984 -61
Branches 5552 5548 -4
==========================================
- Hits 29740 28211 -1529
- Misses 13566 14646 +1080
- Partials 739 1127 +388
Continue to review full report at Codecov.
|
@effigies, if you could spare one minute with this I'd really appreciate it. Especially, the new additions to make Path more consistent across 3.x versions - https://github.com/nipy/nipype/pull/3024/files#diff-7d84fc0957a520f25bb02479beb87c51R75 (see also some tests that I added). |
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.
This seems reasonable overall. A couple comments on the Path
hacks. In addition, would it be possible to tag the regions that are compensating for failures in specific Python versions with # PY34
, # PY35
, etc? That will make them easier to find and purge when we bump our minimum Python.
Minimize the access to the ``result`` property when writing pre/post-execution reports. This modification should particularly preempt nipy#3009 (comment)
Co-Authored-By: Chris Markiewicz <effigies@gmail.com>
c7735db
to
c5d3128
Compare
c5d3128
to
c120ee5
Compare
Summary
Minimize the access to the
result
property when writingpre/post-execution reports.
This modification should particularly preempt #3009 (comment)
Acknowledgment