Remove deprecated io.ascii Reader/Writer and unified I/O interfaces
See original GitHub issueThe Reader
/ Writer
keywords for io.ascii.read/write
have been deprecated for quite a while.
Likewise Unified I/O formats like aastex
(instead of ascii.aastex
) have been deprecated for quite a while.
The 4.0 release would be a good time to clean this up!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Unified File Read/Write Interface — Astropy v5.2
astropy provides a unified interface for reading and writing data in different formats. For many common cases this will streamline the process of...
Read more >Full Changelog — Astropy v1.2.dev14793
astropy.cosmology; astropy.io.ascii; astropy.io.fits; astropy.io.misc; astropy.io.votable ... Remove deprecated register argument for Unit classes. [#4448].
Read more >python-astropy-2.0.3-bp151.3.2 - SUSE Package Hub -
Coordinate frames and models now use this interface. ... [#3750] + astropy.io.ascii o Remove HTML from the list of automatically-guessed formats when ...
Read more >codecs — Codec registry and base classes — Python 3.11.1 ...
These have to provide the interface defined by the base classes ... While the builtin open() and the associated io module are the...
Read more >Full Changelog — Astropy v0.4.2 - The University of Texas at Austin
The astropy.io.ascii output formats latex and aastex accept a dictionary ... These deprecated interfaces will be removed from the development version of ...
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
No point in dragging this through the milestones, the issue is not critical. It is deprecated now for a while, so the removal can happen in any milestone, if 4.3 is a descoping release then it’s ideal, otherwise the 5.0 LTS is good too.
I suppose this is off the table for 4.1, so I’m remilestoning.