Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Non-actionable warnings in astropy (specifically io.fits and units)
See original GitHub issueI have some production code where I added reading in a CIAO X-ray event file and it now generates a warning each time:
UnitsWarning: The unit 'angstrom' has been deprecated in the FITS standard. Suggested: nm (with data multiplied by 0.1).
Why are we issuing this warning? A substantial fraction of FITS files are generated by some other person or institution and there is nothing to be done about this warning except add code to suppress it. In my case this warning is causing a red flag every day to come up in our processing status board, so I really have to suppress it.
Maybe if people really want to opt in to these warnings it could be done via a configuration setting?
Issue Analytics
- State:
- Created 7 years ago
- Comments:25 (25 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@saimn - No, I don’t think so. Also it’s a rather low priority as only a cosmetic issue, the warning doesn’t cause any failure for us.
Yes, the latter three.
The stat one is more serious and we need to fix or get rid of the example (#4927), as that warning is actually not one of these “non-actionable ones” and breaks tests when using pytest 3.1.1 and sphinx 1.6.2