@whit537 Effectively, L forces to use the long type. 
I have focused the test to verify that there is no problem with Twitter identifiers. For these Twitter identifiers with 64bit int type is used, so, there is no need to check the long type. But maybe you are right and we need to check it on 64bit too, to check if it works on 32bit.

Another way to fix the problem is to convert the identifier to unicode type before creating the TwitterAccount object, because AccountElsewhere accepts int and unicode types but converts int to unicode just after check it.

What do you think about it?