typing

Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate pytype into ALE and this would make it a lot easier.

Currently all responses return 200 (unless there is a server error, in which case 500).

It would be best to have specific codes for different types of errors to differentiate between them.

Example:

400 - Bad request

etc.

Problem

We could improve the readability / experience reading through the library source code if there were module level docstrings.

Suggested solution

All python modules should include a docstring explaining

Ideally there should be a way to install on at least some machines without cargo. This will need an installation script to install the language files in lieu of build.rs.

Some alternative installation methods which would be good to include are:

• sh installation script w/ prebuilt binaries
• AUR package

For prebuilt binaries, it would be ideal to setup GitHub workflows or similar so

On Arch Linux, guess I don't have an OS wordlist:

thread 'main' panicked at 'calledResult::unwrap()on anErrvalue: ToipeError { msg: "No such file or directory (os error 2)" }', /home/ben/.cargo/registry/src/github.com-1ecc6299db9ec823/toipe-0.4.0/src/main.rs:9:40 note: run withRUST_BACKTRACE=1environment variable to display a backtrace
Could print a warning or just use the

TAP works very slow:
to reproduce

from tap import Tap
from argparse import ArgumentParser
from profilehooks import profile, timecall


class SimpleArgumentParser(Tap):
    name: str  # Your name
    language: str = 'Python'  # Programming language
    package: str = 'Tap'  # Package name
    stars: int  # Number of stars
    max_stars: int = 5  # Maximum stars


@profile(dirs=T