DOC: remove datareader docs
See original GitHub issueio.data
and io.web
have been deprecated since 0.17 and moved to the pandas-datareader
project. I am not necessarily saying we should already remove the code (although we could, certainly given that the tests cause failures from time to time, but we can also wait until 0.20), but my proposal is to already remove the docs (and only include a link to the pandas-datareader docs).
Reason: some of the examples are failing anyways (due to issues with yahoo), our docs already take quite a while to build, and the exact same content is available in the pandas-datareader docs.
Any objections?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Deleting DataReaders - RTI Community
Delete the DataReader by using the Subscriber's delete_datareader() operation (Deleting Subscribers). Note: A DataReader cannot be deleted within its own reader ...
Read more >pandas-datareader Documentation - Read the Docs
Remove import of deprecated tm.get_data_path (GH566). • Allow full usage of stooq url parameters. • Removed unused requests-file and requests- ...
Read more >pandas-datareader — pandas-datareader 0.10.0 documentation
Up-to-date remote data access for pandas. Works for multiple versions of pandas. Quick Start¶. Install using pip. pip install pandas ...
Read more >Delete data from Cloud Firestore - Firebase
The following examples demonstrate how to delete documents, fields, and collections. Delete documents. To delete a document, use the delete() method: Web ...
Read more >Deleting a Document from a Record Library
Uh… so how do I undeclare it? The answer is that with record libraries, all documents are not only automatically declared records, manual...
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 Free
Top 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
I would just raise automagically substituting a package is not good
What we could do is remove the code (and tests), but still include the file to raise a more informative ImportError (the current deprecation warning, but as an error).