Michael Droettboom

Yes, I should have been explicit -- the lossy compression schemes in FITS do make a lot of sense for astronomy data, and should probably be brought over to FINF....

Renamed issue -- this is now for lossy compression methods. Lossless compression is basically a done deal.

The `tags`, which drive the conversion of parts of the tree to specific datatypes (most importantly ndarrays), and schema validation (by matching a subtree to a particular schema. This feature,...

Also forgot to mention anchors and aliases. Though those could be replicated with the `JSON Pointer` convention, or just resolved away with duplication as long as the references aren't cyclical.

Or maybe get Python 3 documentation building working (can't remember what the blockers were on that), which presumably wouldn't do this? --- Actually, scratch that: we'd also have to make...

Closing in favor of the more comprehensive #98295.

> I think a better approach would be to create sub-checklists or a single issue per file with another checklist for the paths that need coverage, instead of opening dozen...

> Maybe it would be better to start by trimming down the list to remove files that have no issues, and see how many files are left first. I programmatically...

Thanks. The revised plan you suggested should work just fine. I didn't know about the feature to automatically open an issue from a checklist item.

@ofey404 wrote: > Hi, do you need some more eyes in checking coverage report? I just read Python Developer's Guide and I'm finding some issue with "easy" tag to fix...