Closed lourinaldi closed 2 years ago
Hey, thanks for opening this up.
From your traceback, I don't think your patch would fix anything : "ValueError: invalid literal for int() with base 10: 'Us.app/Wrapper'".
There seems to be a problem related to the parsing of df
output, as encountered on Windows.
Could you paste here the output of df -P -k
on your system ?
Thanks, bye 👋
Hey, thanks for opening this up. From your traceback, I don't think your patch would fix anything : "ValueError: invalid literal for int() with base 10: 'Us.app/Wrapper'". There seems to be a problem related to the parsing of
df
output, as encountered on Windows. Could you paste here the output ofdf -P -k
on your system ?Thanks, bye 👋
So it looks like it didn't like whitespace in the Volume name under the "Filesystem" column of df's output (/Applications/Among Us.app/Wrapper
).
Indeed, the parsing is currently very naive, as based on whitespaces. It worked well on *NIX and derivatives as the filesystem column was not supposed to contain any whitespace. I'll try to fix this without aiming for proper Windows support (as originally planned), as you are already concerned on macOS. Cheers
@lourinaldi please check the updated patch and tell me whether it suits you. If you can provide a "real" example in unit tests, it would be great. Bye :wave:
use the float() method to avoid invalid literal for int() with base 10
Description
The Python ValueError: invalid literal for int() with base 10 error is raised when you try to convert a string value that is not formatted as an integer.
To solve this problem, you can use the float() method to convert a floating-point number in a string to an integer. Then, you can use int() to convert your number to an integer.
Reason and / or context
How has this been tested ?
Python 3.9.7 on MacOS 11.6
Types of changes :
Checklist :