-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Fix ModuleNotFoundError: No module named 'cmake' #5195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
Signed-off-by: Yuhong Guo <yuhong.gyh@antgroup.com>
f6f04da
to
c1658d4
Compare
xadupre
reviewed
May 3, 2023
Signed-off-by: Yuhong Guo <yuhong.gyh@antgroup.com>
Signed-off-by: Yuhong Guo <yuhong.gyh@antgroup.com>
Signed-off-by: Yuhong Guo <yuhong.gyh@antgroup.com>
Is this tested in all different environments: venv, conda and w/o venv? |
@justinchuby I have tested this change in following envs:
|
xadupre
approved these changes
May 5, 2023
adityagoel4512
pushed a commit
to adityagoel4512/onnx
that referenced
this pull request
Jul 28, 2023
Signed-off-by: Yuhong Guo <yuhong.gyh@antgroup.com> Co-authored-by: Yuhong Guo <yuhong.gyh@antgroup.com> Co-authored-by: Chun-Wei Chen <jacky82226@gmail.com> Signed-off-by: Aditya Goel <agoel4512@gmail.com>
cjvolzka
added a commit
that referenced
this pull request
Mar 1, 2024
### Description * Fix source and pip tar.gz builds on s390x systems * Revert (#5195) and replace with fix from [this comment](#5194 (comment)) from the original issue (#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing from pypi for environments where we don't have pre-built wheels * Failures include not being able to find pacakges dispite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (#5195) which was to fix (#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH is set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix
cjvolzka
added a commit
that referenced
this pull request
Mar 1, 2024
* Fix builds from source and pip tar.gz on s390x systems * Revert (#5195) and replace with fix from [this comment](#5194 (comment)) from the original issue (#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing `1.16.0rc1` from TestPyPI for environments where we don't have pre-built wheels * Failures include not being able to find pacakges despite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (#5195) which was to fix (#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH gets set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix Signed-off-by: Charles Volzka <cjvolzka@us.ibm.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 2, 2024
### Description * Fix builds from source and pip tar.gz on s390x systems * Revert (#5195) and replace with fix from [this comment](#5194 (comment)) from the original issue (#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing `1.16.0rc1` from TestPyPI for environments where we don't have pre-built wheels * Failures include not being able to find pacakges despite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (#5195) which was to fix (#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH gets set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix Signed-off-by: Charles Volzka <cjvolzka@us.ibm.com>
cjvolzka
added a commit
that referenced
this pull request
Mar 2, 2024
### Description * Cherry-pick (#5984) - Fix builds from source and pip tar.gz on s390x systems * Revert (#5195) and replace with fix from [this comment](#5194 (comment)) from the original issue (#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing `1.16.0rc1` from TestPyPI for environments where we don't have pre-built wheels * Failures include not being able to find pacakges despite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (#5195) which was to fix (#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH gets set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix Signed-off-by: Charles Volzka <cjvolzka@us.ibm.com>
cjvolzka
added a commit
that referenced
this pull request
Mar 5, 2024
…5986) ### Description * Cherry-pick (#5984) - Fix builds from source and pip tar.gz on s390x systems * Revert (#5195) and replace with fix from [this comment](#5194 (comment)) from the original issue (#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing `1.16.0rc1` from TestPyPI for environments where we don't have pre-built wheels * Failures include not being able to find pacakges despite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (#5195) which was to fix (#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH gets set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix Signed-off-by: Charles Volzka <cjvolzka@us.ibm.com>
isdanni
pushed a commit
to isdanni/onnx
that referenced
this pull request
Mar 18, 2024
### Description * Fix builds from source and pip tar.gz on s390x systems * Revert (onnx#5195) and replace with fix from [this comment](onnx#5194 (comment)) from the original issue (onnx#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing `1.16.0rc1` from TestPyPI for environments where we don't have pre-built wheels * Failures include not being able to find pacakges despite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (onnx#5195) which was to fix (onnx#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH gets set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](onnx#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix Signed-off-by: Charles Volzka <cjvolzka@us.ibm.com> Signed-off-by: isdanni <leedanni@gmail.com>
linshokaku
pushed a commit
to linshokaku/onnx
that referenced
this pull request
Oct 2, 2024
### Description * Fix builds from source and pip tar.gz on s390x systems * Revert (onnx#5195) and replace with fix from [this comment](onnx#5194 (comment)) from the original issue (onnx#5194) ### Motivation and Context * Building on s390x (and other environments depending on python setup) fails * The issue also can also appear when installing `1.16.0rc1` from TestPyPI for environments where we don't have pre-built wheels * Failures include not being able to find pacakges despite them being installed ``` pip3 install -e . ... -- Could NOT find pybind11 (missing: pybind11_DIR) ... Traceback (most recent call last): File "/onnx/.setuptools-cmake-build/tools/protoc-gen-mypy.py", line 28, in <module> import google.protobuf.descriptor_pb2 as d_typed ``` * The issue is cased by (onnx#5195) which was to fix (onnx#5194) * The original fix bypasses the pip venv PYTHONPATH and attempts to rely on sys.path. However without the pip venv PYTHONPATH, some modules may not be found even if they are installed. * For reference, the pip venv PYTHONPATH gets set to `/tmp/pip-build-env-bn_o_cjc/site` which contains `sitecustomize.py` which comes from https://github.com/pypa/pip/blob/main/tests/lib/venv.py#L171-L189 * Instead of bypassing the pip venv PYTHONPATH, [this comment](onnx#5194 (comment)) from the original issue shows how to address the issue using pyproject.toml's `[build-system]` * I replicated the origial issue and confirmed this fix resolves it. * I confirmed the builds work on s390x with this fix Signed-off-by: Charles Volzka <cjvolzka@us.ibm.com> Signed-off-by: Linsho Kaku <linsho@preferred.jp>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
run release CIs
Use this label to trigger release tests in CI
topic: build
Issues related to ONNX builds and packages
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.
Description
Described by #5194
Motivation and Context
Since
python setup.py build
works fine, I compared theos.environ
and found thatpip install -e .
add a strangePYTHONPATH
toos.environ
. Deleting it make the installation working fine.