Skip to content
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: simplify nipype etelemetry ping handling #3

Merged
merged 3 commits into from
Jun 4, 2020

Conversation

oesteban
Copy link

@oesteban oesteban commented Jun 3, 2020

Since we are setting pretty up-to-date nipype version restrictions on setup.cfg, the version check and logging it are unnecessary and confusing.

But, we still want to record nipype users, so let's just ping manually.

@oesteban oesteban marked this pull request as draft June 3, 2020 23:04
@oesteban
Copy link
Author

oesteban commented Jun 3, 2020

wait, I think we don't need this much, really.

@oesteban oesteban marked this pull request as ready for review June 3, 2020 23:17
Copy link
Owner

@mgxd mgxd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the minimal approach, but one concern:

fmriprep/config.py Outdated Show resolved Hide resolved
@@ -33,6 +33,7 @@ install_requires =
psutil >= 5.4
pybids >= 0.10.2
pyyaml
requests
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at this point, why not just add etelemetry directly and leverage the check there:
etelemetry.get_project("nipy/nipype")

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought of using _etrequest directly, but we really don't want to do any kind of error handling. After going through the code it seemed more lightweight

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You bring up a good point... it would be useful to have an exception-free version in etelemetry.

@oesteban oesteban requested a review from mgxd June 4, 2020 00:05
@mgxd mgxd merged commit d54925f into mgxd:fix/nipype-et Jun 4, 2020
@oesteban oesteban deleted the fix/nipype-et-patch branch September 4, 2020 08:30
mgxd pushed a commit that referenced this pull request Sep 20, 2021
DOC: typo - delete bracket
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants