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.
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
Enabling of parallelization of
analysis.atomicdistances.AtomicDistances
#4822base: develop
Are you sure you want to change the base?
Enabling of parallelization of
analysis.atomicdistances.AtomicDistances
#4822Changes from 9 commits
c79b7f0
1bd64bc
916a973
cbb3e66
16a0605
0b58a73
9836575
5d6ed62
fd8163a
2aad77d
102ff95
7b61370
fa52881
e7da740
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Update the docs above!!!!
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.
... assuming a breaking change.
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.
Need to be clearer about what was done:
... assuming a breaking change.
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 I'm just confused but it looks to me like the tests haven't actually changed yet (just formatting changes as far as I can tell?) and this just restored the original behavior of
self.results
storing a NumPy array again?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.
yes, first I modified it to have the output would be
self.results.distances
, but then I thought that for the convenience to not modify the docs, where it usesmy_dists.results
tomy_dists.results.distances
I could defineself.results
asself.results.distances
to not have to change the docs and still be able to implement the parallelization of the class.As for the
pytest
changes, first I had theself.results.distances
output and thus the tests needed to have also the.distances
. The Idea to haveself.results
came after creating the PR 🙈, but yes I will then remove the mention of thepytest
modification, was quite late when I finished up the PR, so didn't think about that :)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.
That's a hack!
If this the way we want to go then you have to write more commentary to say what you're doing and why, with references to issue and a note that this needs to be changed for 3.0.