Update pyenv plugin

[rominf]

Difference between old and new plugins:
Old plugin doesn't call status --is-interactive; and . (pyenv init -|psub). That means completions are not loaded and PYENV_SHELL is not set. New plugin doesn't call this command either, but it has completions generation script bundled, so completions are generated when pyenv is called. It also sets PYENV_SHELL on init.

[derekstavis]

cc @scorphus @pantuza

[rominf]

Any progress?

[sagebind]

Our usual policy is to not reassign existing package names to new projects, as this can be surprising to users that use the old plugin. For example, setting up a new machine, imagine the surprise of omf install pyenv installing a different plugin than the one on your old machine.

Perhaps consider porting your improvements to the existing pyenv plugin instead?

[rominf]

@sagebind, what's the difference will I port and heavily change the plugin or we replace it?
Anyway, if you want you can replace contents of existing plugin with the new plugin. Probably, it's even better, because the link is prettier.

[scorphus]

@rominf, it's great that you brought up this discussion. There's a pull request open for a few months which I'd pretty much like to merge: oh-my-fish/plugin-pyenv#5

@sagebind, I'd be thankful if you could review it 😃

🐟 🐚

[scorphus]

Closing in favor of aforementioned PR