[request] Update pypi release

[yozachar]

It's been over a year. Please create a new tagged release for PyPi.

[wookayin]

+1. Looking forward to #496 being merged.

[stsewd]

Anything we can do to help with the new release? I found this bug #496 and realized it was already fixed in master :D

[wookayin]

/cc @justinmk @bfredl

Please neovim maintainers have more attention to this repo as well as neovim-core.

[clason]

It's been over a year. Please create a new tagged release for PyPi.

1. there hasn't been any significant changes since the last release, so tagging a new one now would just be release theatre

2. a new PyPi release would require updating to the current minimal Python version and distribution methods, which is significant development work

Please neovim maintainers have more attention to this repo as well as neovim-core.

3. that's not how this work; time is a finite resource, especially for volunteer work, which is understandably focused on core work (especially since the constantly improving Lua API makes Python plugins less and less popular).

[clason]

Anything we can do to help with the new release? I found this bug #496 and realized it was already fixed in master :D

Help is welcome. The first step would be to review #519 and make sure it works, or improve so it passes current requirements.

[yozachar]

#496 and #519 are merged.

[justinmk]

Released 0.5: https://github.com/neovim/pynvim/releases/tag/0.5.0

[wookayin]

Hmm I wish I had some discussion and set the scope before we cut the 0.5 release...

[justinmk]

@wookayin we can always do another followup release