+1

Seems like this was causing issues on a Windows 64-bit machine (not sure if that is relevant or not).

#865 was merged onto master, but could have been applied to v1.1.x, hence this PR.

See also #387 Fix Tk crash on locales with non-'.' decimal separator

@WeatherGod / @mdboom or other dev: I have commited this pull request. In order to merge the v1.1.x branch back into master, can I simply do:

git co master
git fetch upstream
git pull upstream master
git merge upstream/v1.1.x
git push upstream_WRITEABLE master     #(my setup: upstream is read only, upstream_WRITABLE is full ssh access)

Yes -- that looks correct to me. I usually do a "git log" before the push just to make sure it did what I thought it would.

In addition, I always do a "--dry-run" for that final git push to make sure it is going to the correct location. This rule is actually much more important for pushing commits to your personal branches because it makes sure that you aren't accidentially pushing your personal work up to the official tree. This happened frequently when we initially started using git a year or two ago.

Thanks for the advice. Seems to have done the trick (c3c41a3...ea3c539).

@cgohlke thanks for doing this work & sorry for hijacking this issue with my commit questions ;-) .