pyre-check VS pyenv-installer

Did you come across pyre in your search? MIT license and pretty fast.

https://github.com/facebook/pyre-check

Pyre is a performant type-checker developed by Facebook. Pyre can analyse codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code.

Pyre from Meta, pyright from Microsoft and PyType from Google provide additional assistance. They can 'infer' types based on code flow and existing types within the code.

Have you seen Pyre[0]? Not Rust, OCaml, and pretty fast. Made by a team at Meta and open sourced on GitHub. If you use python-lsp, I wrote an extension[1] to enable integration (though I haven't tested it recently, been programming in rust; it is mostly a "for me" extension).

0: https://pyre-check.org/

1: https://github.com/cricalix/python-lsp-pyre

Internally we use Pyre for Python type checking: https://github.com/facebook/pyre-check

Before type hinting, work had intense rules and linters enforcing docstrings with types. Now, type hints and automatic pyre runs take care of all the heavy lifting.

Python now has an optional type system and if you add one of them such as mypy or pyre to your CI process and you can configure GitHub to refuse the pull request until types are added you can make it somewhat strongly typed.

If you have a preexisting codebase I believe the way you can convert it is to add the types that you know on commits and eventually you will have enough types that adding the missing ones should be easy. For the missing ones Any is a good choice.

https://pyre-check.org and https://github.com/python/mypy are popular.

To install it make sure that all prerequisites are met. Then use the pyenv-installer project like this to get the tool installed:

I tried the uninstaller from https://github.com/pyenv/pyenv-installer and I'm getting this.

After you’ve installed the build dependencies, you’re ready to install pyenv itself. I recommend using the pyenv-installer project:

For python, it's recommended to use pyenv, which allows you to install several versions of python at the same time with simple commands like this: pyenv install 3.9.13

Please don't contribute worthless and irrelevant comments like this. As you doubtless well know, piping from curl into bash is something that a large subset of respected programmers think is reasonable, and another rather tedious subset do not. For example, the entire Rust community clearly has a consensus that it's reasonable: https://rustup.rs/ As does homebrew https://brew.sh/ and pyenv https://github.com/pyenv/pyenv-installer#install to name whatever came to my mind in 30s thought.

Since the debate has such large numbers on both sides, your individual opinion on it is neither interesting nor germane.

name: Test, build and release # whenever a branch or commit is pushed on: [push] jobs: # use pytest test: # used to ensure testing is done right env: DEVELOPMENT: '1' runs-on: ubuntu-latest # to avoid using old sqlite version container: image: debian:latest options: --user root steps: # check out repo - uses: actions/checkout@v2 # prevent from asking user for input - run: export DEBIAN_FRONTEND=noninteractive # install recommended tools for building Python - run: apt -q update - run: apt -q install make build-essential libssl-dev zlib1g-dev libbz2-dev libreadline-dev libsqlite3-dev wget curl llvm libncursesw5-dev xz-utils tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev git sqlite3 -y - run: apt -q upgrade -y # install pyenv - run: curl -L https://github.com/pyenv/pyenv-installer/raw/master/bin/pyenv-installer | bash - run: exec $SHELL - run: ~/.pyenv/bin/pyenv update # install and set up required Python - run: ~/.pyenv/bin/pyenv install 3.10.2 - run: ~/.pyenv/bin/pyenv virtualenv 3.10.2 npbc - run: ~/.pyenv/bin/pyenv local 3.10.2/envs/npbc # print version info (debugging) - run: ~/.pyenv/shims/python -V - run: ~/.pyenv/shims/python -c "import sqlite3; print(sqlite3.version)" # install pip packages - run: ~/.pyenv/shims/pip install -r requirements.txt pytest # run test - run: ~/.pyenv/shims/pytest -vv

curl -L https://github.com/pyenv/pyenv-installer/raw/master/bin/pyenv-installer | bash

This uses the pyenv-installer project to install pyenv on your system.