Skip to content

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented May 5, 2024

@@ -12,8 +12,7 @@ description = "A fork of the GYP build system for use in the Node.js projects"
readme = "README.md"
license = { file="LICENSE" }
requires-python = ">=3.8"
# The Python module "packaging" is vendored in the "pylib/packaging" directory to support Python >= 3.12.
# dependencies = ["packaging>=23.1"] # Uncomment this line if the vendored version is removed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove the vendored packaging source code as well?

Copy link
Contributor Author

@cclauss cclauss May 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My preference would be to do this in two steps even if there is a bit of duplication.

@cclauss cclauss requested a review from legendecas May 6, 2024 14:01
@legendecas legendecas merged commit e063e20 into main May 6, 2024
@legendecas legendecas deleted the pyproject.toml-dependencies=packaging branch May 6, 2024 22:49
@legendecas
Copy link
Member

I think it would be still necessary to have the vendored packaging source to be used in the nodejs core repo with python 3.12 support. LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The return of ModuleNotFoundError: No module named 'packaging' on Py3.12
2 participants