chore: drop poetry, migrate to pip + flit_core#563
Open
MIchaelMainer wants to merge 4 commits into
Open
Conversation
- Replace poetry-core build backend with flit_core in all 8 packages - Convert all pyproject.toml from [tool.poetry] to PEP 621 [project] format - Fix [mypy] -> [tool.mypy] in abstractions, authentication/azure, bundle, tests/validation - Fix tests/validation mypy files setting to 'validation' - Create requirements-dev.txt per package (8 packages + tests/validation) - Update build.yml: replace poetry install/run with pip and direct commands - Update cd-publish-python.yml: replace poetry with pip install build + python -m build - Remove poetry-plugin-mono-repo-deps from root requirements_dev.txt Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It was highly suggested from an internal Pythonista that we should drop Poetry as it adds extra complexity when encountering edge scenarios. This will also make Kiota-Python better match what we are doing for the graph repos.
Validation runs:
https://github.com/microsoft/kiota-python/actions/runs/26969442452
https://dev.azure.com/microsoftgraph/Graph%20Developer%20Experiences/_build/results?buildId=221616&view=results