Improve toml typings

[faresbakhit]

Add toml's full API. Fixes #6484.

[faresbakhit]

I'm not sure if it is correct to use TomlDecoder(Generic[_T]). Should I have just used MutableMapping[str, Any] instead?

[Akuli]

Thanks! toml is now deprecated and many projects are switching to tomli instead, but we still accept improvements to the toml stubs.

[Akuli]

Thanks for working on this! It has turned out to be trickier than I expected :)

[faresbakhit]

Finally, Got the tests to pass 😄!

[Akuli]

A couple final things, then this will be ready :)

[faresbakhit]

In __init__.pyi, should this be preferred over the current one?

from . import decoder as decoder, encoder as encoder
from .decoder import (
    TomlDecodeError as TomlDecodeError,
    TomlDecoder as TomlDecoder,
    TomlPreserveCommentDecoder as TomlPreserveCommentDecoder,
    load as load,
    loads as loads,
)
from .encoder import (
    TomlArraySeparatorEncoder as TomlArraySeparatorEncoder,
    TomlEncoder as TomlEncoder,
    TomlNumpyEncoder as TomlNumpyEncoder,
    TomlPathlibEncoder as TomlPathlibEncoder,
    TomlPreserveCommentEncoder as TomlPreserveCommentEncoder,
    TomlPreserveInlineDictEncoder as TomlPreserveInlineDictEncoder,
    dump as dump,
    dumps as dumps,
)

VSCode's ms-python.python extension currently highlights the functions and classes as variables which looks a bit bad but in reality they are really variables just as defined in toml's source code. What do you think?

[Akuli]

Both import styles are acceptable. If one produces better syntax highlighting than the other, use whichever highlights better :)

[faresbakhit]

Okay then, I think this is it! 😄

[Akuli]

Thanks!

[JelleZijlstra]

Both import styles are acceptable. If one produces better syntax highlighting than the other, use whichever highlights better :)

This is about from ... import X as X vs. X = X, right? I think it makes sense to standardize on the first style in general. We could probably enforce it in flake8-pyi.