Migrating from Pylint/Flake8 setup to integrated

[Kein]

According to
https://github.com/microsoft/vscode-python/wiki/Migration-to-Python-Tools-Extensions
mypy, pylint and flake8 are integrated (???)

This was my setup before:

    "python.linting.enabled": true,
    "python.linting.pylintEnabled": true,
    "python.linting.pylintArgs": [
        "--disable=bare-except,multiple-imports,global-statement,relative-beyond-top-level,superfluous-parens,import-error,missing-function-docstring,invalid-name,bad-whitespace,line-too-long,missing-class-docstring,unused-variable,unused-argument,multiple-statements,bad-continuation"
    ],
    "python.linting.flake8Enabled": false,
    "python.linting.flake8Args": [
        "--ignore=E305,E302,E226,E741,E501,E222,E127,E251,F722,W292,F841"
    ],
    "python.linting.mypyEnabled": true,

How can I now migrate properly to new Pylance type checking with the same settings for the linters?

[brettcannon]

mypy, pylint and flake8 are integrated

They were integrated. Now support is via separate extensions.

How can I now migrate properly to new Pylance type checking with the same settings for the linters?

That's a question for Pylance, but I'm pretty sure they don't support a lot of things Pylint and flake8 do.

[Kein]

Why is this question for Pylance if python.linting.* config space is courtesy of vscode-python?
So is the wiki page talking about the deprecation of old settings and linters.

[brettcannon]

Why is this question for Pylance

Because you said, "How can I now migrate properly to new Pylance type checking". If you're asking how to move to the new tool extensions, then the wiki page you linked to tells you how.