astropy/astropy#9468 highlighted that there are code snippets in docstrings that are not actually picked up during doctesting. I strongly feel that shouldn't be the case, we should skip any such testing in very rare occasions.
I tag this as a coordinates issue, but they may be other sub packages affected by the same problem.

I am suggesting adding up another feature which will be either a standalone or a part of an advanced search. I suggest adding up a tool which will permit to select a given area. A user can predefine searchable objects by their type (like dwarfs, blue giants and the like) and magnitude (all objects of the apparent/absolute magnitude, for example, 13). When search is done, the search box would list

it should either link to the animator docs or copy the function signature information

Problem

Lightkurve has a lot of unit tests which access the data archive at MAST. This causes a number of problems:

• our tests are slow;
• many of our tests require internet access;
• tests sometimes fail due to intermittent issues at MAST rather than Lightkurve issues;
• we add an unnecessary load on MAST's services.

Current workaround

We have flagged the tests which require inte

The python implementation of leapfrog does not make use of the fact that drifts can be combined when not storing output, causing it to be slower than necessary. Comparing to the C implementation, it also appears to not be as precise.