BLD: Install thonny with conda and/or mamba

User story: Users can install Thonny with conda and/or mamba:

conda install -c conda-forge -y thonny

conda install -c conda-forge -y mamba

mamba install -c conda-forge -y thonny
mamba install -y thonny

• Create a conda-forge feedstock for thonny
  • Create a separate conda-forge feedstock(s) for thonny plugin(s)

Docs:

• https://conda-forge.org/docs/
  • https://conda-forge.org/docs/maintainer/adding_pkgs.html
  • https://conda-forge.org/docs/maintainer/updating_pkgs.html

    Pushing to regro-cf-autotick-bot branch¶ When a new version of a package is released on PyPI/CRAN/…, we have a bot that automatically creates version updates for the feedstock. In most cases you can simply merge this PR and it should include all changes. When certain things have changed upstream, e.g. the dependencies, you will still have to do changes to the created PR. As feedstock maintainer, you don’t have to create a new PR for that but can simply push to the branch the bot created. There are two alternatives […]

• https://github.com/conda-forge/spyder-feedstock/tree/master/recipe

[westurner]

publish 64-bit wheels for Python 3.10.

https://github.com/pypa/cibuildwheel

https://anaconda.org/conda-forge/jpype1

https://anaconda.org/conda-forge/thonny

https://github.com/conda-forge/spyder-feedstock/tree/master/recipe

[aivarannamaa]

I tried to install thonny-py5mode with latest Thonny beta (containing 64-bit Python 3.10) and could confirm the problem with jpype1. IMO the best solution in this case would be convincing jpype1 developer to publish 64-bit wheels for Python 3.10.