add additional parameter to control if hostname of localhost is used #258
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.
Previously tests on
mac-os> 11 failed when we tried to establish the connection using the hostname fromfrom socket import gethostname. Now this pull request implements a switch to disable resolving the hostname. This is dangerous in distributed environments like HPC clusters, as we want to be able to access python processes on different hosts. So the default behaviour remains the same andfrom socket import gethostnameis used. Only for the tests this option is disabled and the hostname is set tolocalhostinstead. Naively I thought a computer would be able to resolve that its hostname refers tolocalhostbut it seems this behaviour changed inmac-os> 11.