microsoft
/
lisa
зеркало из https://github.com/microsoft/lisa.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
lisa/pyproject.toml

53 строки
1.4 KiB
TOML
Исходник Обычный вид История

Setup pyproject.toml with Poetry toolchain I ran `poetry init` using the cross-platform Python packaging, dependency management, and virtual environment management tool Poetry: https://python-poetry.org/ The chosen version follows Semantic Versioning: https://semver.org/, with the Python specific pre-release versioning suffix ‘.dev1’: https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme Since this is “LISAv3” it seemed appropriate to set our version to ‘3.0.0.dev1’, “the first development release of LISAv3.” I pinned Python to version 3.8, as we will always use a Poetry provided Python and not depend on a system’s packaged Python version. This will avoid many headaches. I added Chi’s existing dependencies from ‘requirements.txt’, and then added my suggested development dependencies: - black, the opinionated code formatter - flake8 (and integrations), the semantic analyzer - isort, the import sorter - mypy, the static type checker - python-language-server (and integrations), the de facto LSP server - rope, to provide completions and renaming to pyls While Microsoft is developing their own LSP servers, they do not integrate with the existing ecosystem of tools, and their latest tool, Pyright, simply does not support ‘pyproject.toml’. Since pyls is used far more widely, and supports every editor, we will use this. Finally, I updated the readme with instructions on how to use this toolchain, and deleted the outdated bootstrap files.
2020-08-04 11:06:22 +03:00
[tool.poetry]
name = "LISA"
version = "3.0.0.dev1"
description = "Linux Integration Services Automation"
authors = ["Andrew Schwartzmeyer <andrew@schwartzmeyer.com>", "Chi Song <song.chi@microsoft.com>"]
license = "Apache License 2.0"
[tool.poetry.dependencies]
python = "^3.8"
psutil = "^5.7.2"
pyyaml = "^5.3.1"
retry = "^0.9.2"
change to a better singleton pattern.
2020-08-06 10:00:39 +03:00
paramiko = "^2.7.1"
refactoring code for process 1. use spurplus to get unique interface for local and remote processes 2. rename executable to tool 3. other minor changes
2020-08-10 06:54:31 +03:00
spurplus = "^2.3.3"
use strong type schema, init azure platform code 1. use dataclasses as base schema, dataclasses_json for serialization, and marshmallow for validation. 2. remove yaml format schema, add python schema. 3. use strong type to replace dict based code. 4. add platform schema and node schema for platform extension. 5. add _initialize for platform 6. init azure platform code. 7. other small improvements.
2020-08-20 07:04:55 +03:00
dataclasses-json = "^0.5.2"
# portalocker for compatibility of Windows, trigger pywin32 installed
portalocker = "^1.7.1"
azure-identity = {version = "^1.4.0", allow-prereleases = true}
azure-mgmt-resource = {version = "^15.0.0-beta.1", allow-prereleases = true}
support deploy azure environment, and refactoring 1. support azure deployment and add arm template. 2. remove envs, use constants to pass variables like path. 3. add clone to copy from runbook to actual environment. 4. refine runner to delete env on failure. 5. refine schema to support listable validator, and rich configs. 6. other minor improvements.
2020-08-27 13:12:57 +03:00
azure-mgmt-compute = {version = "^17.0.0-beta.1", allow-prereleases = true}
azure-mgmt-network = {version = "^16.0.0-beta.1", allow-prereleases = true}
Setup pyproject.toml with Poetry toolchain I ran `poetry init` using the cross-platform Python packaging, dependency management, and virtual environment management tool Poetry: https://python-poetry.org/ The chosen version follows Semantic Versioning: https://semver.org/, with the Python specific pre-release versioning suffix ‘.dev1’: https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme Since this is “LISAv3” it seemed appropriate to set our version to ‘3.0.0.dev1’, “the first development release of LISAv3.” I pinned Python to version 3.8, as we will always use a Poetry provided Python and not depend on a system’s packaged Python version. This will avoid many headaches. I added Chi’s existing dependencies from ‘requirements.txt’, and then added my suggested development dependencies: - black, the opinionated code formatter - flake8 (and integrations), the semantic analyzer - isort, the import sorter - mypy, the static type checker - python-language-server (and integrations), the de facto LSP server - rope, to provide completions and renaming to pyls While Microsoft is developing their own LSP servers, they do not integrate with the existing ecosystem of tools, and their latest tool, Pyright, simply does not support ‘pyproject.toml’. Since pyls is used far more widely, and supports every editor, we will use this. Finally, I updated the readme with instructions on how to use this toolchain, and deleted the outdated bootstrap files.
2020-08-04 11:06:22 +03:00
[tool.poetry.dev-dependencies]
black = "^19.10b0"
flake8 = "^3.8.3"
Add flake8-black package So that `black --check` is run automatically by `flake8`.
2020-08-05 23:58:32 +03:00
flake8-black = "^0.2.1"
Setup pyproject.toml with Poetry toolchain I ran `poetry init` using the cross-platform Python packaging, dependency management, and virtual environment management tool Poetry: https://python-poetry.org/ The chosen version follows Semantic Versioning: https://semver.org/, with the Python specific pre-release versioning suffix ‘.dev1’: https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme Since this is “LISAv3” it seemed appropriate to set our version to ‘3.0.0.dev1’, “the first development release of LISAv3.” I pinned Python to version 3.8, as we will always use a Poetry provided Python and not depend on a system’s packaged Python version. This will avoid many headaches. I added Chi’s existing dependencies from ‘requirements.txt’, and then added my suggested development dependencies: - black, the opinionated code formatter - flake8 (and integrations), the semantic analyzer - isort, the import sorter - mypy, the static type checker - python-language-server (and integrations), the de facto LSP server - rope, to provide completions and renaming to pyls While Microsoft is developing their own LSP servers, they do not integrate with the existing ecosystem of tools, and their latest tool, Pyright, simply does not support ‘pyproject.toml’. Since pyls is used far more widely, and supports every editor, we will use this. Finally, I updated the readme with instructions on how to use this toolchain, and deleted the outdated bootstrap files.
2020-08-04 11:06:22 +03:00
flake8-bugbear = "^20.1.4"
use strong type schema, init azure platform code 1. use dataclasses as base schema, dataclasses_json for serialization, and marshmallow for validation. 2. remove yaml format schema, add python schema. 3. use strong type to replace dict based code. 4. add platform schema and node schema for platform extension. 5. add _initialize for platform 6. init azure platform code. 7. other small improvements.
2020-08-20 07:04:55 +03:00
flake8-isort = "^4.0.0"
isort = "^5.4.2"
Setup pyproject.toml with Poetry toolchain I ran `poetry init` using the cross-platform Python packaging, dependency management, and virtual environment management tool Poetry: https://python-poetry.org/ The chosen version follows Semantic Versioning: https://semver.org/, with the Python specific pre-release versioning suffix ‘.dev1’: https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme Since this is “LISAv3” it seemed appropriate to set our version to ‘3.0.0.dev1’, “the first development release of LISAv3.” I pinned Python to version 3.8, as we will always use a Poetry provided Python and not depend on a system’s packaged Python version. This will avoid many headaches. I added Chi’s existing dependencies from ‘requirements.txt’, and then added my suggested development dependencies: - black, the opinionated code formatter - flake8 (and integrations), the semantic analyzer - isort, the import sorter - mypy, the static type checker - python-language-server (and integrations), the de facto LSP server - rope, to provide completions and renaming to pyls While Microsoft is developing their own LSP servers, they do not integrate with the existing ecosystem of tools, and their latest tool, Pyright, simply does not support ‘pyproject.toml’. Since pyls is used far more widely, and supports every editor, we will use this. Finally, I updated the readme with instructions on how to use this toolchain, and deleted the outdated bootstrap files.
2020-08-04 11:06:22 +03:00
mypy = "^0.782"
pyls-black = "^0.4.6"
pyls-isort = "^0.1.1"
pyls-mypy = "^0.1.8"
python-language-server = "^0.34.1"
rope = "^0.17.0"
add support for code coverage
2020-09-03 05:55:03 +03:00
coverage = "^5.2.1"
Setup pyproject.toml with Poetry toolchain I ran `poetry init` using the cross-platform Python packaging, dependency management, and virtual environment management tool Poetry: https://python-poetry.org/ The chosen version follows Semantic Versioning: https://semver.org/, with the Python specific pre-release versioning suffix ‘.dev1’: https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme Since this is “LISAv3” it seemed appropriate to set our version to ‘3.0.0.dev1’, “the first development release of LISAv3.” I pinned Python to version 3.8, as we will always use a Poetry provided Python and not depend on a system’s packaged Python version. This will avoid many headaches. I added Chi’s existing dependencies from ‘requirements.txt’, and then added my suggested development dependencies: - black, the opinionated code formatter - flake8 (and integrations), the semantic analyzer - isort, the import sorter - mypy, the static type checker - python-language-server (and integrations), the de facto LSP server - rope, to provide completions and renaming to pyls While Microsoft is developing their own LSP servers, they do not integrate with the existing ecosystem of tools, and their latest tool, Pyright, simply does not support ‘pyproject.toml’. Since pyls is used far more widely, and supports every editor, we will use this. Finally, I updated the readme with instructions on how to use this toolchain, and deleted the outdated bootstrap files.
2020-08-04 11:06:22 +03:00
Configure black, flake8, and isort to work together As recommended by Black: https://github.com/psf/black/blob/master/docs/compatible_configs.md
2020-08-05 23:59:55 +03:00
[tool.black]
line-length = 88
target-version = ['py38']
[tool.isort]
multi_line_output = 3
include_trailing_comma = true
force_grid_wrap = 0
use_parentheses = true
ensure_newline_before_comments = true
line_length = 88
Setup pyproject.toml with Poetry toolchain I ran `poetry init` using the cross-platform Python packaging, dependency management, and virtual environment management tool Poetry: https://python-poetry.org/ The chosen version follows Semantic Versioning: https://semver.org/, with the Python specific pre-release versioning suffix ‘.dev1’: https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme Since this is “LISAv3” it seemed appropriate to set our version to ‘3.0.0.dev1’, “the first development release of LISAv3.” I pinned Python to version 3.8, as we will always use a Poetry provided Python and not depend on a system’s packaged Python version. This will avoid many headaches. I added Chi’s existing dependencies from ‘requirements.txt’, and then added my suggested development dependencies: - black, the opinionated code formatter - flake8 (and integrations), the semantic analyzer - isort, the import sorter - mypy, the static type checker - python-language-server (and integrations), the de facto LSP server - rope, to provide completions and renaming to pyls While Microsoft is developing their own LSP servers, they do not integrate with the existing ecosystem of tools, and their latest tool, Pyright, simply does not support ‘pyproject.toml’. Since pyls is used far more widely, and supports every editor, we will use this. Finally, I updated the readme with instructions on how to use this toolchain, and deleted the outdated bootstrap files.
2020-08-04 11:06:22 +03:00
[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"