[AstroPy] Draft specification for PyFITS functional interface

[Nor]

Keeping the two separated would be my preference as well. It would 
leave pyfits unpolluted by the "quick and dirty" high level interface 
(qpyfits? :-) )

On Mar 30, 2005, at 2:42 PM, Paul Barrett wrote:
>
> I'm wondering if these convenience functions aren't better off in a 
> separate python module that imports pyfits.  This approach would keep 
> the pyfits interface simple and objected-oriented, and would signal 
> that the procedural interface is being used.  Command line versions of 
> these convenience functions could also exist, so that users could 
> easily extract information from a FITS file.
>
>  -- Paul
>
> -- 
> Paul Barrett, PhD      Space Telescope Science Institute
> Phone: 410-338-4475    ESS/Science Software Branch
> FAX:   410-338-4767    Baltimore, MD 21218
> _______________________________________________
> AstroPy mailing list
> AstroPy at scipy.net
> http://www.scipy.net/mailman/listinfo/astropy