Current status of sub-packages

SunPy has in variations in stability across sub-packages. This document summarizes the current status of the SunPy sub-packages, so that users understand where they might expect changes in future, and which sub-packages they can safely use for production code. For help or to discuss specific sub-packages, refer to the maintainer list to find who to contact.

The classification is as follows:

Planned
Actively developed, be prepared for possible significant changes.
Reasonably stable, any significant changes/additions will generally include backwards-compatiblity.
Mature. Additions/improvements possible, but no major changes planned.
Pending deprecation. Might be deprecated in a future version.
Deprecated. Might be removed in a future version.

The current planned and existing sub-packages are:

Sub-Package   Comments
sunpy.cm Only forwards compatible changes expected.
sunpy.coordinates Should be stable, with additions and small changes expected.
sunpy.data Should see no major changes.
sunpy.database Undergoing changes with each major release.
sunpy.image None
sunpy.instr None
sunpy.io Should see no major changes.
sunpy.map Any future changes should largely maintain backwards compatibility.
sunpy.net Any future changes should largely maintain backwards compatibility.
sunpy.physics None
sunpy.roi There is very little functionality.
sunpy.sun Sub-module `constants` is stable. Sub-module `models` will likely have major changes. Sub-module `sun` is deprecated in 1.0 and will be removed in 2.0.
sunpy.time Any future changes should largely maintain backwards compatibility.
sunpy.timeseries Any future changes should largely maintain backwards compatibility.
sunpy.visualization Any future changes should largely maintain backwards compatibility.

Taken with love from the Astropy project.