Given that the issue can not be reproduced except on an older version (3.3) that is no longer being actively maintained, the proper thing to do is mark this as "out of date".

If the problem recurs with 3.5 (once cx_Freeze can be tried there) then a new bug should be opened at that time.

Mark:  I recommend moving to a newer version, specifically 3.4 would seem like a winner for you.  If you are truly stuck for whatever reason on 3.3 and your patch works for you, I'd suggest using it there until you can migrate to a more recent release.