Last active
December 7, 2016 10:31
-
-
Save joleroi/2bec5762adbbaabf89609aba10056045 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Astropy regions is an in-development package for region handling based on | |
Astropy (http://astropy-regions.readthedocs.io/en/latest/). It was already | |
discussed at PyAstro15 and PyAstro16 | |
(http://astropy-regions.readthedocs.io/en/latest/development.html#notes). The | |
motivation for the regions package was to merge the functionality from pyregion | |
(http://pyregion.readthedocs.io/en/latest/) and photutils apertures | |
(http://photutils.readthedocs.io/en/latest/photutils/aperture.html) into a | |
single package and add more functionality. We plan to propose the new regions | |
package for inclusion into the Astropy core as 'astropy.region' in April 2017, | |
well in time for the Astropy 2.0 release. In my talk I | |
will present the functionality that is currently available | |
(http://astropy-regions.readthedocs.io/en/latest/getting_started.html), with the | |
main goal of getting you to use astropy regions for your | |
projects/software packages. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I always assumed it would be
astropy.regions
(plural), notastropy.region
as you write here.The current package is also called
regions
(plural)@joleroi @astrofrog - OK? Or do you prefer to propose
astropy.region
?