KivyMD
KivyMD copied to clipboard
kivymd
Available versions
$ pip install kivymd==2.0.1
ERROR: Could not find a version that satisfies the requirement kivymd==2.0.1 (from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0) ERROR: No matching distribution found for kivymd==2.0.1 (kivymd-venv) mybox ~/Code/Python Projects/Samples
same result for 2.0.0 on linux mint 20 The 2.0.0 version posted on the main git page is not in the version list, and the master.zip installs what appears to be a dev version: 2.0.1.dev0
Hi Champ, Did that as mentioned in the ticket that the master.zip installs 2.0.1.dev0 which looks like a dev branch.. not stable production. Either way the main git page states the installation as follows: pip install kivymd==2.0.0
Which is NOT in the list of install-able versions when pip installs as previously stated: from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0)
All this started because the 2.0.1.dev0 branch/version is throwing an error on a module that should exist (using the master.zip you mentioned, I had already tried):
from kivymd.uix.tab import MDTabsBase ImportError: cannot import name 'MDTabsBase' from 'kivymd.uix.tab' (/home/paul/.pyenv/versions/kivymd-venv/lib/python3.11/site-packages/kivymd/uix/tab/init.py)
Thank you Yuri for your prompt response, you are very quick! But the original posted issue was about the pip install being broken, and its still broke and that version is unavailable:
$ pip install kivymd==2.0.0 ERROR: Could not find a version that satisfies the requirement kivymd==2.0.0 (from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0) ERROR: No matching distribution found for kivymd==2.0.0
This is still an open issue, especially because the page states that method of install.
Same issue! I also am unable to build the latest version due to an error in materialyoucolor: " materialyoucolor/quantize/celebi.cc:17:10: fatal error: 'cpp/quantize/celebi.h' file not found 17 | #include "cpp/quantize/celebi.h" | ^~~~~~~~~~~~~~~~~~~~~~~ 1 error generated. error: command '/opt/homebrew/bin/clang' failed with exit code 1 " On my M1 mac. It would be nice to have precompiled binaries past 1.2.0
Same issue! I also am unable to build the latest version due to an error in materialyoucolor: " materialyoucolor/quantize/celebi.cc:17:10: fatal error: 'cpp/quantize/celebi.h' file not found 17 | #include "cpp/quantize/celebi.h" | ^~~~~~~~~~~~~~~~~~~~~~~ 1 error generated. error: command '/opt/homebrew/bin/clang' failed with exit code 1 " On my M1 mac. It would be nice to have precompiled binaries past 1.2.0
Please install master version of materialyoucolor and then KivyMD:
pip3 install https://github.com/T-Dynamos/materialyoucolor-python/archive/main.zip
The needs are stable versions to build projects, not continuous evolving masters
The needs are stable versions to build projects, not continuous evolving masters
Version 2.0.0 will no longer break the existing API.
Please stop talking about version 2.0.0 because there is no version 2.0.0 available, as all the comments try to show:
$ pip install kivymd==2.0.0 ERROR: Could not find a version that satisfies the requirement kivymd==2.0.0 (from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0) ERROR: No matching distribution found for kivymd==2.0.0
Ok, this is the source of confusion because kivymd's readme.md states the opposite
The same with ghost version 1.2.0 that does not exist in documentation nor github tags just a magic pip package taken out of nowhere and api breaking mentions in the latest docs. What was the reason to release unsupported version that is not a version? :-(
Please create tags for 1.2.0 and 2.0.0 releases. Master currently shows version 2.0.1.dev0.
I ran away from JavaScript to avoid lack of versioning and maintenance nightmare. Please avoid this here.
Until versioning is resolved KivyMD is NO GO. Once people start developing their own widgets there will be no incentive to go back to KivyMD :-(
I know there may be problems with 2.0.0 but you can safely release a 2.0.0 and make fixes with time. People would at least have a reference ground to work on. This is really important. Please consider many people asking for that and thanks in advance :-)
@HeaTTheatR please do not get angry, we are very close to a first release, its either stay with KivyMD 1.1.1 or try switching to 2.0.0, or avoid it at all. Having a 2.0.0 release would give us a reference point. So far there are two releases announced that does not exist (1.2.0 and 2.0.0) and that does not look good.
The same with ghost version 1.2.0 that does not exist in documentation nor github tags just a magic pip package taken out of nowhere and api breaking mentions in the latest docs. What was the reason to release unsupported version that is not a version? :-(
Please create tags for 1.2.0 and 2.0.0 releases. Master currently shows version 2.0.1.dev0.
I ran away from JavaScript to avoid lack of versioning and maintenance nightmare. Please avoid this here.
Until versioning is resolved KivyMD is NO GO. Once people start developing their own widgets there will be no incentive to go back to KivyMD :-(
I know there may be problems with 2.0.0 but you can safely release a 2.0.0 and make fixes with time. People would at least have a reference ground to work on. This is really important. Please consider many people asking for that and thanks in advance :-)
@HeaTTheatR please do not get angry, we are very close to a first release, its either stay with KivyMD 1.1.1 or try switching to 2.0.0, or avoid it at all. Having a 2.0.0 release would give us a reference point. So far there are two releases announced that does not exist (1.2.0 and 2.0.0) and that does not look good.
Thanks for the feedback. KivyMD version 2 has one serious bug so far - https://github.com/kivymd/KivyMD/issues/1601 This bug is almost fixed. As soon as I merge my local changes with the master branch and we test it for a while, then we can release version 2
Thanks @HeaTTheatR :-)
I am actively working on Kivy + KivyMD application right now.. plan a first test release this week.. small measurable steps.. when the 2.0.0 is out I can switch to that version test it in practice provide feedback help with bugfixes development etc :-)
Have a good day :-)
thanks really @HeaTTheatR i was so glad when i had of the release earlier this year because the documentation looks really promissing with alot of new improvement.
actually one of the issues that drove me back immidiatley was when i couldn't set auto_dismiss=False, it was stated like this in the documentations but it obviously not part of the valid arguement.
thanks really @HeaTTheatR i was so glad when i had of the release earlier this year because the documentation looks really promissing with alot of new improvement.
actually one of the issues that drove me back immidiatley was when i couldn't set auto_dismiss=False, it was stated like this in the documentations but it obviously not part of the valid arguement.
You can create an appropriate issue
As of today (April 30th), the issue still continues and the README file still has the misleading info that doesn't work:
pip install kivymd==2.0.0
Although @HeaTTheatR first comment works like a charm, please consider to amend this in the README file.
Thanks!
Esta história de versões novas quebrarem as construções antigas é muito ruim... MDToolBar não funciona, pois mudou para MD... Outro problema é estar lendo uma Documentação de algo que não funciona!
