While working on porting a utility using launchpadlib from Python2 to Python3, I noticed the binary attachments were becoming unreadable.
I wrote a little proof of concept that uploads a given binary attachment to a launchpad issue (see attachment). To use it on staging launchpad:
APPORT_STAGING=1 ./poc.py <bug_number> </path/to/file.bin>
When using the exact same script with python2 (basically, replacing `python3` with `python` in the shebang line), the binary file is properly attached. That's why I think it's a bug with python3-launchpadlib.
While working on porting a utility using launchpadlib from Python2 to Python3, I noticed the binary attachments were becoming unreadable.
I wrote a little proof of concept that uploads a given binary attachment to a launchpad issue (see attachment). To use it on staging launchpad:
APPORT_ STAGING= 1 ./poc.py <bug_number> </path/to/file.bin>
When using the exact same script with python2 (basically, replacing `python3` with `python` in the shebang line), the binary file is properly attached. That's why I think it's a bug with python3- launchpadlib.