We're running 64-bit in production, so we shouldn't target 32-bit at all. The name of the test is `test_get_user_info_gets_user_info_long`, so I think we should force a long in the call to TwitterAccount. This is a minor issue and the fix here is good enough. I think we should add `L` in the test to ensure that we're actually triggering the bug on 64-bit systems and call it a day. :-)