-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate sage.media.wav, since it is totally undoctested, and evidently full of confusing bugs #12673
Comments
Attachment: trac_12673.patch.gz |
comment:2
Alternatively, doctest the code. I've attached a patch to delete it, but maybe that is too draconian. |
comment:3
This is (very tangentially) related to #7668 and this interact by Marshall. Given that it's not the worst to eventually have easy-to-use wave handling, perhaps it would be appropriate to split the difference between doctesting and deleting. Could one simply comment out all the code and raise (doctested?) |
comment:4
Please fill in your real name as Author. |
comment:5
I've changed my mind. I think that we should just replace this by some really nice documentation about how to use the |
New commits:
|
Author: Matthias Koeppe |
Commit: |
Reviewer: Travis Scrimshaw |
comment:13
LGTM. |
comment:14
Thanks! |
comment:15
Are there no doctests at all that will get confused here? Maybe we should add one along the lines of the ones in sage.finance. |
comment:16
(I mean #32427.) |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
There was not a single doctest. Now there is one. |
comment:20
It was definitely the wild wild west in those days. Thanks, and sorry to override Travis' review :) I will assume patchbot will be happy and restore his assessment. |
comment:21
Replying to @kcrisman:
Don't worry about it at all. We are a community with different options, and we as a collective should agree about positive reviews. |
…e; deprecated in sagemath#12673, sagemath#32988 <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes sagemath#1234" use "Introduce new method to calculate 1+1" --> <!-- Describe your changes here in detail --> <!-- Why is this change required? What problem does it solve? --> <!-- If this PR resolves an open issue, please link to it here. For example "Fixes sagemath#12345". --> <!-- If your change requires a documentation PR, please link it appropriately. --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [x] The title is concise, informative, and self-explanatory. - [ ] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on - sagemath#12345: short description why this is a dependency - sagemath#34567: ... --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: sagemath#36305 Reported by: Matthias Köppe Reviewer(s):
As I think http://480.sagenb.org/home/pub/137/ amply illustrates, the mere existence of the untested and very buggy module sage.media.wav causes more confusion than it is worth for now. It would be best to remove it from Sage, and only add something back as a result of a new (probably student) project to do things right.
CC: @jasongrout @sagetrac-mhampton
Component: misc
Author: Matthias Koeppe
Branch/Commit:
2bf2bd0
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/12673
The text was updated successfully, but these errors were encountered: