-
Notifications
You must be signed in to change notification settings - Fork 114
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
read(): Strange behavior if frames, out, and fill_value are given? #210
Comments
I agree! |
mgeier
added a commit
to mgeier/python-soundfile
that referenced
this issue
Nov 14, 2017
Partial solution to bastibe#210, but this breaks blocks()! The tests can be run without testing blocks(): python3 -m pytest -k"not blocks"
I've started to address this in #214, but there is still some work to be done ... |
mgeier
added a commit
to mgeier/python-soundfile
that referenced
this issue
Nov 14, 2017
Partial solution to bastibe#210, but this breaks blocks()! The tests can be run without testing blocks(): python3 -m pytest -k"not blocks"
mgeier
added a commit
to mgeier/python-soundfile
that referenced
this issue
Nov 14, 2017
Partial solution to bastibe#210, but this breaks blocks()! The tests can be run without testing blocks(): python3 -m pytest -k"not blocks"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This behavior seems strange to me:
I'd expect that a view into
out
with 7 elements would be returned, i.e.I think it is strange that
frames
is only ignored ifout
andfill_value
are given, but it is not ignored if onlyout
is given:I think that if specified by the user,
frames
should never be ignored. I'd expect this behavior:Is anybody with me on that?
Or am I missing something?
The text was updated successfully, but these errors were encountered: