Well, at least from the interpreter, 3.6.3 seemed to have fixed it. I'll add that to the application too.
Well, at least from the interpreter, 3.6.3 seemed to have fixed it. I'll add that to the application too.