[AstroPy] Capturing pyfits warnings
Tue Sep 14 15:36:44 CDT 2010
Bridgman, William T. wrote:
> I've got something almost working based on this prescription.
> In some ways, I think throwing an exception might not be the preferred
Why would that be the case?
What is the preferred behavior?
If I understood your original posting correctly, you were looking to
handle an exception.
I think that is the typical behavior in Python.
> Doesn't the actual FITS standard have some odd data block size (2880
> bytes?). I suspect the messages are from files that are not quite
> filling the block but are not actually corrupted.
> I'm trying to track these errors/warnings to determine if that is
> indeed the case.
> On Sep 14, 2010, at 3:43 PM, Jim Vickroy wrote:
>> Hi John,
>> I'm curious to learn why pyfits uses the *warnings* module in this
>> fashion. I naively would expect to see exceptions in the situation
>> encountered by Tom.
>> -- jv
>> firstname.lastname@example.org wrote:
>>> Jim's suggestion should work as long as what is being generated
>>> is an exception and not a warning. If a warning is being generated
>>> through the warnings module, you will need to have the warning
>>> module generate an exception instead of a warning message. The
>>> PyFITS user manual gives an example of ignoring a warning message,
>>> but the same template applies to raising an exception. Just
>>> replace the word 'ignore' in the samples with the word 'error'.
>>> So when starting a python session use:
>>> python -W"error"
>>> Or when running a script:
>>> python -W"error" myscript.py
>>> Or within your script:
>>> import warnings
>>> import pyfits
>>> warnings.filterwarnings('error', category=UserWarning,
>>> # do your thing.
>>> Then using Jim's try/except block should get these warnings as
>>> Jim T.
>>> AstroPy mailing list
>> AstroPy mailing list
> Dr. William T."Tom" Bridgman Scientific Visualization
> Global Science & Technology, Inc. NASA/Goddard Space Flight
> Email: William.T.Bridgman@nasa.gov Code 610.3
> Phone: 301-286-1346 Greenbelt, MD 20771
> FAX: 301-286-1634 http://svs.gsfc.nasa.gov/
> AstroPy mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the AstroPy