Please test against astropy v5.2rc1 and report back
See original GitHub issueHello. astropy
v5.2rc1 is out. Please test against it and report back success or failure before v5.2 is really released. Thank you for your help!
Issue Analytics
- State:
- Created 9 months ago
- Comments:6
Top Results From Across the Web
v5.2rc1 astropy.test also runs tests in astropy.extern if installed ...
Also, I am curious, do the tests still fail if you run the two different test suites back to back but in some...
Read more >Known Issues — Astropy v5.2
Issues listed on this page are grouped into two categories: The first is known ... This also includes cases where the test suite...
Read more >astropy v5.1rc1 ready for testing - Google Groups
Hi everyone, The first release candidate (RC) of the core astropy package for the v5.1 release is now available and ready for testing!...
Read more >List of supported software - EasyBuild documentation
A software package for algebraic, geometric and combinatorial problems on linear ... The Astropy Project is a community effort to develop a single...
Read more >Installation — Astropy v1.0.4
Binary installers are available on Windows for Python 2.6, 2.7, and >= 3.3 at PyPI. Testing an installed Astropy¶. The easiest way to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
At this time Lightkurve only uses the MAST TessCut API via Astroquery, so it does not directly depend on “cloud FITS” yet.
(But it could be a great performance improvement in the future!)
Not sure if this is related or not, but using astropy 5.2 and lightkurve 2.3, I’m trying to do a simple median on the flux:
which returns
This can be avoided if you intentionally dodge the
astropy.utils.masked.Masked
object like this:which returns the expected result.