RuntimeError: Cannot parse version 0+untagged
See original GitHub issueDescribe the issue:
Build fails on macOS Monterey 12.3.1 / python 3.10.4 / pip 22.1, not sure whether it’s a numpy or pip issue though.
Reproduce the code example:
git clone https://github.com/numpy/numpy
pip install numpy/
Error message:
% pip install numpy/
Processing ./numpy
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [20 lines of output]
Error in sitecustomize; set PYTHONVERBOSE for traceback:
AssertionError:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
main()
File "/usr/local/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/usr/local/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
return hook(config_settings)
File "/usr/local/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/setuptools/build_meta.py", line 177, in get_requires_for_build_wheel
return self._get_build_requires(
File "/usr/local/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/setuptools/build_meta.py", line 159, in _get_build_requires
self.run_setup()
File "/usr/local/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/setuptools/build_meta.py", line 281, in run_setup
super(_BuildMetaLegacyBackend,
File "/usr/local/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/setuptools/build_meta.py", line 174, in run_setup
exec(compile(code, __file__, 'exec'), locals())
File "setup.py", line 64, in <module>
raise RuntimeError(f'Cannot parse version {FULLVERSION}')
RuntimeError: Cannot parse version 0+untagged.1.gae8b9ce
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
NumPy/Python version information:
python 3.10.4
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
raise RuntimeError(f'Cannot parse version {FULLVERSION ...
I tried Intel® Distribution for Python* for Linux* online, it tells me 'This machine uses operating system "Ubuntu Linux version 16.04".
Read more >raise RuntimeError(f'Cannot parse version {FULLVERSION ...
Solved: I tried to link MKL with numpy in Windows subsystem Linux.
Read more >RuntimeError: The current Numpy installation - Esri Community
After upgrading ArcGIS Pro from 2.5 to 2.6 version I faced a problem in running the model codes because the project environment was...
Read more >h5py BIOM error - Metagenomics
RuntimeError : h5py is not installed, cannot parse HDF5 BIOM file. Solution: install h5py in python (for reading .biom files). pip install h5py....
Read more >NumPy: setup.py - Fossies
(\d+)', FULLVERSION) 63 if _V_MATCH is None: 64 raise RuntimeError(f'Cannot parse version {FULLVERSION}') 65 MAJOR, MINOR, MICRO = _V_MATCH.groups() 66 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
👍 Ah, you didn’t say that 😃 Yes, that will do it.
I just found out what’s wrong. I initially cloned the repo with
--depth 1
which for some reason result in the error. The problem was gone and I was able to build the wheel successfully by cloning without the--depth
flag. I’m closing the issue. If this behavior is unexpected, feel free to re-open it.