The linked issue has been fixed in 0.5.7, but the update (PR #392911 / 0d25c10) didn't drop this part.
0d25c10