MidiExplorer icon indicating copy to clipboard operation
MidiExplorer copied to clipboard

Does not install on Windows

Open foamycastle opened this issue 1 year ago • 2 comments

Terminal output:

`Collecting midiexplorer Using cached midiexplorer-0.0.1a5-py3-none-any.whl.metadata (82 kB) Collecting dearpygui-ext~=0.9.5 (from midiexplorer) Using cached dearpygui_ext-0.9.5-py3-none-any.whl.metadata (5.7 kB) INFO: pip is looking at multiple versions of midiexplorer to determine which version is compatible with other requirements. This could take a while. Collecting midiexplorer Using cached midiexplorer-0.0.1a4-py3-none-any.whl.metadata (82 kB) Using cached midiexplorer-0.0.1a3-py3-none-any.whl.metadata (82 kB) Using cached midiexplorer-0.0.1a2-py3-none-any.whl.metadata (55 kB) Using cached midiexplorer-0.0.1a1-py3-none-any.whl.metadata (55 kB) Using cached midiexplorer-0.0.1a0-py3-none-any.whl.metadata (53 kB) ERROR: Cannot install midiexplorer==0.0.1a0, midiexplorer==0.0.1a1, midiexplorer==0.0.1a2, midiexplorer==0.0.1a3, midiexplorer==0.0.1a4 and midiexplorer==0.0.1a5 because these package versions have conflicting dependencies.

The conflict is caused by: midiexplorer 0.0.1a5 depends on dearpygui~=1.8.0 midiexplorer 0.0.1a4 depends on dearpygui~=1.8.0 midiexplorer 0.0.1a3 depends on dearpygui~=1.8.0 midiexplorer 0.0.1a2 depends on dearpygui==1.6.2 midiexplorer 0.0.1a1 depends on dearpygui==1.6.2 midiexplorer 0.0.1a0 depends on dearpygui==1.6.2

To fix this you could try to:

  1. loosen the range of package versions you've specified
  2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts`

foamycastle avatar Mar 31 '25 17:03 foamycastle

Hi, thanks for checking out my software and for the report. Sorry to hear you are having issues installing it.

I suspect you are using a Python version incompatible with the specified dearpygui version.

  1. Which version of Python are you running? (py --version)

  2. Are you following the installation instructions from the README or using pip directly?

If you just want to run the software on Windows, I recommend you try the experimental native build available in the release.

Please keep in mind this is alpha software and it is not feature complete yet.

rdoursenaud avatar Mar 31 '25 23:03 rdoursenaud

I think it's because the requirement can not indeed be satisfied, as dearpygui 1.8 was only made available for Python 3.11 at most. So if @foamycastle is using a more recent Python version, such as Python 3.13, pip is lost.

2.0 has a Py 3.13 version available, so main branch should work, but there's a typo in the dep name.. see #19

gilou avatar Apr 06 '25 21:04 gilou