Added verbose= to AstrometryNet#2484
Conversation
…ssed to ``solve_from_source_list`` when calling ``solve_from_image``.
Codecov Report
@@ Coverage Diff @@
## main #2484 +/- ##
==========================================
- Coverage 62.92% 62.90% -0.03%
==========================================
Files 133 133
Lines 17302 17308 +6
==========================================
Hits 10888 10888
- Misses 6414 6420 +6
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
|
Getting rid of these prints has come up before, thanks for doing the cleanup. One holdup is to decide whether to go with I recall @andamian put some very good arguments for the logger approach, but maybe the |
|
Logger is good for pipeline but can be troublesome if astroquery is used as "middleware" where the downstream packages also have their own loggers and find it hard to control yours. Also, it can clutter up notebooks if not set properly for that use case. So, it really depends on how you want it to be used and where. |
|
I like @pllim's point here - if we get included in pipelines, and we've seen cases of that happening, we don't want to spam when different modes are activated. I'd therefore lean toward But I can be sold either way. |
|
I think the |
|
Thanks @astrofrog! |
With this it is possible to suppress the print() statements which can clutter up stdout when running on many images.
I've also solved a small bug that caused
solve_timeoutto not be passed through tosolve_from_source_listwhen callingsolve_from_image.