could Not Find a version that satisfies the requirement (aka Unable to install in Macintosh Python 3.91 (Big Sur))

[bschollnick]

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.

[hoffstadt]

Hoping to have a local build script up today.

[hoffstadt]

Could you verify if this build script works for the M1 chip? Instructions I verified it for the intel chip.

This is in the master branch, so you should NOT use this wheel. But if it works, I will back port it to the 0.6.x branch so you can actually use it.

[bschollnick]

Well, it certainly does a lot, but there does appear to be an issue:

Installing collected packages: wheel
  WARNING: The script wheel is installed in '/Users/benjamin/temp/DearPyGui/Dependencies/cpython/debug/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed wheel-0.36.2
Traceback (most recent call last):
  File "/Users/benjamin/temp/DearPyGui/Dependencies/cpython/Lib/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/Users/benjamin/temp/DearPyGui/Dependencies/cpython/Lib/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/Users/benjamin/temp/DearPyGui/Distribution/setup.py", line 10, in <module>
    with open("distinfo.txt", encoding='utf-8') as file:
  File "/Users/benjamin/temp/DearPyGui/Distribution/../Dependencies/cpython/debug/../Lib/codecs.py", line 905, in open
    file = builtins.open(filename, mode, buffering)
FileNotFoundError: [Errno 2] No such file or directory: 'distinfo.txt'

And doing a file search does not find an "distinfo.txt" file in the cloned repository.

[hoffstadt]

Haven't forgot about this. Trying to get my hands on an M1.

[mcxiv]

Hi,

Same problem on Windows with Python 3.8.5, and on Raspbian with Python 3.8.0.

C:\Users\QUENTIN-D\Desktop>pip install dearpygui
ERROR: Could not find a version that satisfies the requirement dearpygui (from versions: none)
ERROR: No matching distribution found for dearpygui

But it works on another Windows with Python 3.8.6. Hope it helps somehow!

[hoffstadt]

For the windows machine can you verify it isn't 32 bit? Raspian isn't supported YET. Will soon!

[mcxiv]

Sorry for French, but voilà :

Can't wait to use it on my Raspberry!

[hoffstadt]

Awesome and I'm excited about the raspberry as well!

Is the python version 32 bit? I believe you can type pip debug on your command line. Can you try that and post the results?

[mcxiv]

Omg you're right, I totally forgot that... I had to install Python 32 bits for whatever reason back in the time...
My other computer where Python 3.8.6 runs is indeed a 64 bits version.
My bad, sorry.

pip version: pip 20.2.3 from C:\Users\QUENTIN-D\AppData\Roaming\Python\Python38\site-packages\pip (python 3.8)
sys.version: 3.8.5 (tags/v3.8.5:580fbb0, Jul 20 2020, 15:43:08) [MSC v.1926 32 bit (Intel)]
sys.executable: c:\users\quentin-d\appdata\local\programs\python\python38-32\python.exe
sys.getdefaultencoding: utf-8
sys.getfilesystemencoding: utf-8
locale.getpreferredencoding: cp1252
sys.platform: win32
sys.implementation:
  name: cpython
'cert' config value: Not specified
REQUESTS_CA_BUNDLE: None
CURL_CA_BUNDLE: None
pip._vendor.certifi.where(): C:\Users\QUENTIN-D\AppData\Roaming\Python\Python38\site-packages\pip\_vendor\certifi\cacert.pem
pip._vendor.DEBUNDLED: False
vendored library versions:
  appdirs==1.4.4
  CacheControl==0.12.6
  colorama==0.4.3
  contextlib2==0.6.0.post1 (Unable to locate actual module version, using vendor.txt specified version)
  distlib==0.3.1
  distro==1.5.0 (Unable to locate actual module version, using vendor.txt specified version)
  html5lib==1.1
  ipaddress==1.0.23
  msgpack==1.0.0 (Unable to locate actual module version, using vendor.txt specified version)
  packaging==20.4
  pep517==0.8.2
  progress==1.5
  pyparsing==2.4.7
  requests==2.24.0
  certifi==2020.06.20
  chardet==3.0.4
  idna==2.10
  urllib3==1.25.9
  resolvelib==0.4.0
  retrying==1.3.3 (Unable to locate actual module version, using vendor.txt specified version)
  setuptools==44.0.0 (Unable to locate actual module version, using vendor.txt specified version)
  six==1.15.0
  toml==0.10.1
  webencodings==0.5.1 (Unable to locate actual module version, using vendor.txt specified version)
Compatible tags: 30
  cp38-cp38-win32
  cp38-abi3-win32
  cp38-none-win32
  cp37-abi3-win32
  cp36-abi3-win32
  cp35-abi3-win32
  cp34-abi3-win32
  cp33-abi3-win32
  cp32-abi3-win32
  py38-none-win32
  ...
  [First 10 tags shown. Pass --verbose to show all.]

[hoffstadt]

Happens alot!

[hoffstadt]

We finally go access to the new mac runners. Should have it up later this week!

[hoffstadt]

Can we check if this has been resolved? One user said it was.

[alahiff]

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

% pip3 install dearpygui
Collecting dearpygui
  ERROR: Could not find a version that satisfies the requirement dearpygui (from versions: none)
ERROR: No matching distribution found for dearpygui

[karanseq]

Hello.
Is there an update on whether this is fixed?
Thanks very much.

[hoffstadt]

Will be in the next release (1.0)

[Endogen]

Release 1.0 is here but i can't install it on my M1. Would love to get this working

[hoffstadt]

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.

[Endogen]

Awesome! That worked :)

[hoffstadt]

Wait really? Like completely worked? If so, I may try to get a mac m1 this weekend to start building wheels

[Endogen]

Haha yeah I was amazed too :-D

Currently running your demo and it's working fine. Maybe a bit laggy but i went through all the elements in the demo and no issues at all.

[hoffstadt]

Interesting. If you run "show_metrics()" what FPS are you getting?

[Endogen]

Tool rendering is slowly but constantly going up

EDIT: Ok seems to be stable now at 1200

[hoffstadt]

Tool rendering will max out after 30 seconds. But 40fps isn't great. Will debug when I get one. Wht are the specs?

[Endogen]

[HoofedEar]

@Endogen could you elaborate a bit more on the wheel building process? After following the instructions for the wheel build, using macosx-11.0-arm64, and installing the built wheel, I get this error after trying to run the code you have shown in your screenshot:

EDIT:
Mac mini, M1, 8GB, macOS 11.6

[Endogen]

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>

[HoofedEar]

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>

Ahh I did mine with 3.10, I will attempt with 3.9 instead
EDIT: No dice, still same error as above

[kondratk]

@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:

[hoffstadt]

@kondratk Awesome! I appreciate the information. I just need to save up a bit and get an M1 so I can build the wheels for you guys. I imagine it will be a while before github has M1 runners.

[gguemez]

@HoofedEar

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>

Ahh I did mine with 3.10, I will attempt with 3.9 instead EDIT: No dice, still same error as above

You might be mixing architectures ... is your python arm or x86 based?

[gguemez]

@hoffstadt

Thanks for all the effort in building this library ... I set it up just as you described, running perfectly with 60fps. Mac M1 16GB

However, running any other code, including the tutorial code, is producing a segmentation fault

[NickelLiang]

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 dist
But I would like to add that bdist_wheel require pip 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.

[merchantzain]

@NickelLiang I

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.

I'm running examples from the imgui project at a native 120 fps, which makes me think this might be related to the library in some way, though I'm not sure. Just thought to point that out. And yeah, an FPS limiter would be a useful feature to have.

[hoffstadt]

If you want to minimize the power consumption, you can use dpg.configure_app(wait_for_input=True).

[hoffstadt]

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:

Glfw Error 65544: Cocoa: Failed to find service port for display

This is being address (because we are in the process of removing GLFW altogether).

[e055]

Hi

I tried run DearPyGui on my 2 apples but it works only on one of them:

MacBook Air (13-calowy, 2017 r.) - running OK

Apple Imac 12,2 a1312 27" 12gb ram, intel i5 3.1 High Sierra 10.13.6

ImportError: dlopen(.......): Symbol not found: ____chkstk_darwin

Please help me, I really need it on huge screen :(

Maciej

[chi11-0ut]

hi! can u help me? I have troubles with installation dearpygui on my MacBook Pro m1, python 3.1

thx

[hoffstadt]

Hi, you need to make sure you have cmake installed as a command line tool! here

[chi11-0ut]

thx man! all ok! its work!

[e055]

I M afraid you have to buy newer machine :( Dnia 12 stycznia 2024 09:38 Thuva Sooriya ***@***.***> napisał(a): Is the wheel building process automated now?, I see the same error in Python 3.12.1 and 3.11.7 when using pip3 install, will try 3.9 and get back. — Reply to this email directly, github.com view it on GitHub , or github.com unsubscribe . You are receiving this because you commented. Message ID: <hoffstadt/DearPyGui/issues/568/1888660605 @ github . com>