DearPyGui: could Not Find a version that satisfies the requirement (aka Unable to install in Macintosh Python 3.91 (Big Sur))
This may affect other 3.9x install platforms? I was only able to test Python 3.91 Macintosh.
DearPyGui version - v0.6.166+ (5c74d61?) downloaded directly from Github ~14:00ish on 2/10/2021
Mac OS X Big Sur 11.2.1 Python 3.9.1 (default, Feb 2 2021, 22:54:59) [Clang 12.0.0 (clang-1200.0.32.29)] on darwin
Unable to use PIP to install dearpyGui.
(intelworking) benjamin@Nerv scripts % pip install dearpygui
ERROR: Could not find a version that satisfies the requirement dearpygui
ERROR: No matching distribution found for dearpygui
Looking at verbose mode, “Skipping link: none of the wheel’s tags match:” is plastered on all of the links.
Comparing it to the tags produced below, so the arm64, and universal2 tags.
(intelworking) benjamin@Nerv scripts % python3 -c"from packaging import tags; print(‘\n’.join([str(t) for t in tags.sys_tags()]))" |head -5 cp39-cp39-macosx_11_0_arm64 cp39-cp39-macosx_11_0_universal2 cp39-cp39-macosx_10_16_universal2 cp39-cp39-macosx_10_15_universal2 cp39-cp39-macosx_10_14_universal2
I have tried this in Rosetta 2, as well as in M1 Native. I have had no issues with python libraries in Rosetta 2, including Cryptopgraphy, PyMuPDF, etc. So Rosetta2 (Intel Translation) mode does not appear to be the issue.
I’ll be happy to assist in troubleshooting, testing, etc.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 40 (17 by maintainers)
In my previous message I incorrectly assumed the new github mac runners were M1’s but I was completely wrong. Once I get an M1, I can build them manually but I’m not sure when that will be. Until that time, you could try building the wheel locally like this but I believe the platform name should be
macosx-11.0-arm64.Just to add a data point: I was able to build this library locally with the instruction provided:
python3 -m setup bdist_wheel --plat-name macosx-11.0-arm64 --dist-dir distBut I would like to add thatbdist_wheelrequirepip install wheel.My machine is the new MBP14, 10 Core CPU / 16 Core GPU / 16GB RAM, running macOS Monterey 12.0.1. I was able to get the demo running consistently at around 100-115 FPS. I was not able to hit 120 FPS with the build in monitor, but that might be due to the variable refresh rate scheduling of the OS and not really the library.
Out of curiosity, are there any way to limit FPS? When I’m running demo with 60 FPS monitor the GPU power consumption stabled at 70mW. When I’m running demo with built-in 120 FPS panel, the GPU power consumption stabled at about 300mW. I can see myself limiting my app at 60FPS to save some power consumption.
@hoffstadt I can also confirm that building wheel and installing it on M1 mac with Big Sur 11.6 / Python 3.9.7 works as expected 😃 I’m getting 60 fps at M1 MBP / 16 GB:
Will be in the next release (1.0)
I get the same error with: macOS 11.5.2 Python 3.8.2 (default, Jun 8 2021, 11:59:35) [Clang 12.0.5 (clang-1205.0.22.11)] on darwin
Hi, you need to make sure you have cmake installed as a command line tool! here
We’ve added 2 wheels for Apple Silicon. Python 3.8 & Python 3.9. We will continue to add more once we’ve automated the process a bit. We are having to manually build the wheels at the moment.
Also note, GLFW (the windowing library we use for Mac/Linux) will possibly show an error:
This is being address (because we are in the process of removing GLFW altogether).
@HoofedEar
You might be mixing architectures … is your python arm or x86 based?
I did it with Python 3.9 and did exactly what was mentioned in the Wiki. Nothing different. Then installed it with
pip install <wheel-file>We finally go access to the new mac runners. Should have it up later this week!
Hi,
Same problem on Windows with Python 3.8.5, and on Raspbian with Python 3.8.0.
But it works on another Windows with Python 3.8.6. Hope it helps somehow!
Well, it certainly does a lot, but there does appear to be an issue:
And doing a file search does not find an “distinfo.txt” file in the cloned repository.