native-api

**In `_tkinter` changes 2->3, there are no relevant changes as shown below. So, the relevant logic is effectively the same.** As per [_tkinter.diff.zip](https://github.com/RedFantom/mtTkinter/files/1791147/_tkinter.zip), the changes between 2 and 3 are:...

Okay, got the results on the logic, too. All in all, for non-threaded Tcl, all Tcl calls are wrapped with locks (see comment at https://github.com/python/cpython/blob/master/Modules/_tkinter.c#L162 ) . So, **they _should_...

https://bugs.python.org/issue33257

> Thus, if I understand correctly, after your patch is merged `mtTkinter` will be obsolete for the updated version of Python 2.7? Yes, exactly. I've looked through all the other...

Looks like shims are not on PATH. If you've upgraded to Pyenv 2 from an earlier version -- did you add `eval "$(pyenv init --path)"` to the session's login shell's...

@distobj You need to not change `-` to `--path` but rather add a `--path` line to login shell's configuration (while the `-` line should be in interactive shell's configuration). If...

> you don't need to set your shims in non-login shells A non-login shell is always a descendant of a login shell. So if you set up the PATH in...

@andersrmr Not relevant to Pyenv. We do not use `cygpath`.

Perhaps we can adjust the initialization code to work in the case when Pyenv-Win is on PATH. Then we need to figure out how to detect that. --- Alternatively --...

Some time ago, I've updated the suggested text for shell configuration files given by `pyenv init` to: ``` export PYENV_ROOT="$HOME/.pyenv" [[ -d $PYENV_ROOT/bin ]] && export PATH="$PYENV_ROOT/bin:$PATH" eval "$(pyenv init...