-
Notifications
You must be signed in to change notification settings - Fork 47
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
1.3.3 struggling with zero byte files #71
Comments
Hm, I can't repro on OS X:
(Note that despite FIDO listing itself as 1.3.1 I am using the latest tarball release.) |
Hi Misty, I installed from PIP and so I removed that and then installed from the downloadable releases to try again also: Zip:
Tarball:
Differences in Python version? |
Hm, also cannot reproduce. I note fido.py can return three values when the length of the BOF buffer is zero, which seems strange as it usually returns two values. Perhaps this check has moved further up the call chain and this is now dead code that shouldn't get called? @ross-spencer Any chance you've got an old version of Fido installed somewhere else? (under the old package name?!) UPDATE Hah, I've managed to break my installation and reproduce this error by using UPDATE 2 @mistydemeo or perhaps you have the old version cached in site-package? |
Thanks @anjackson - I haven't been using FIDO on this machine up until today so I wasn't expecting it to be something legacy on my system - from your update do you still think it might be a conflict between an old and a new version? |
If it is, then AFAICT it's the other way around - ie Fido was was only working for me (and is only working for @mistydemeo) because we had/have old Fido installs on the PYTHONPATH. |
Cool. Thanks Andy. If it turns out that it is my install then I can nuke whatever I need to nuke and then try again too. I would have looked at the code today as well but had a few other priorities to work on first. |
It looks like it was in fact old FIDO installs for me; after nuking my virtualenv I'm now seeing this same behaviour. |
Instead of returning two or three values depending on the arguments, always return three values, with the third value being set to None if not relevant. Updates every place that calls this method to ignore the third value if it's not required. Fixes #71.
I believe this was introduced by 6c7f798. |
Instead of returning two or three values depending on the arguments, always return three values, with the third value being set to bytes_to_read if known. Updates every place that calls this method to ignore the third value if it's not required/used. Fixes #71.
Thanks @mistydemeo, I definitely should pay more attention to changes like that in the future. @jhsimpson will merge #74 soon. |
Stack trace:
Empty file listing below:
Distro stats:
The text was updated successfully, but these errors were encountered: