Yet Another Geographer

Working between python 2 and python 3

Whereas on my test server, this works, on the python 2 compute server, this yields zero always, since n_accepted is an int less than the int _total_iterations. Thus, the tuner takes the acceptance rate to be zero, even when the acceptance rate is likely never zero.After my summer of code experience, I’ve come to think this division behavior is the scariest design choice in python 2, and makes the jump from 2 to 3 and back so fraught. I totally forget about __future__ because in 90% of my environments, I don’t need it. And, when I have to maintain code in both 2 and 3, bugs like this can’t be autoconverted, and often will only show by causing the program to act strangely, but not fail.

imported from: <a href='https://yetanothergeographer.tumblr.com/153334732599/working-between-python-2-and-python-3'yetanothergeographer