1 Answer
I installed kivy by using the following commands.
python -m pip install --upgrade pip wheel setuptools
python -m pip install docutils pygments pypiwin32 kivy.deps.sdl2 kivy.deps.glew
python -m pip install kivy.deps.gstreamer
python -m pip install kivy.deps.angle
python -m pip install pygame
python -m pip install kivy
If this does not work for you I recommend you install all these modules in PyCharm.
Paul Roub
36.4k27 gold badges84 silver badges93 bronze badges
answered May 4, 2020 at 5:36
Welcome_backWelcome_back
1,32712 silver badges20 bronze badges
Npackd itself and also all data about packages [but not the package binaries or associated icons] is licensed under GPLv3 Windows is a registered trademark of Microsoft Corporation in the United States and other countries. GLYPHICONS FREE were used and are released under the Creative Commons Attribution 3.0 Unported License [CC BY 3.0] Bootstrap was used and is released under MIT License jQuery CookieBar Plugin was used and is released under the Creative Commons Attribution 3.0 Unported License [CC BY 3.0]
The main branch is currently the future Python 3.13, and is the only branch that accepts new features. The latest release for each Python version can be found on the download page.
Python release cycle
'08 '09 '10 '11 '12 '13 '14 '15 '16 '17 '18 '19 '20 '21 '22 '23 '24 '25 '26 '27 '28 '29 Python 2.6 end-of-life Python 2.7 end-of-life Python 3.0 end-of-life Python 3.1 end-of-life Python 3.2 end-of-life Python 3.3 end-of-life Python 3.4 end-of-life Python 3.5 end-of-life Python 3.6 end-of-life Python 3.7 end-of-life Python 3.8 security Python 3.9 security Python 3.10 security Python 3.11 bugfix Python 3.12 bugfix Python 3.13 feature
Supported versions
Dates shown in italic are scheduled and can be adjusted.
Branch
Schedule
Status
First release
End of life
Release manager
main
PEP 719
feature
2024-10-01
2029-10
Thomas Wouters
3.12
PEP 693
bugfix
2023-10-02
2028-10
Thomas Wouters
3.11
PEP 664
bugfix
2022-10-24
2027-10
Pablo Galindo Salgado
3.10
PEP 619
security
2021-10-04
2026-10
Pablo Galindo Salgado
3.9
PEP 596
security
2020-10-05
2025-10
Łukasz Langa
3.8
PEP 569
security
2019-10-14
2024-10
Łukasz Langa
Unsupported versions
Branch
Schedule
Status
First release
End of life
Release manager
3.7
PEP 537
end-of-life
2018-06-27
2023-06-27
Ned Deily
3.6
PEP 494
end-of-life
2016-12-23
2021-12-23
Ned Deily
3.5
PEP 478
end-of-life
2015-09-13
2020-09-30
Larry Hastings
3.4
PEP 429
end-of-life
2014-03-16
2019-03-18
Larry Hastings
3.3
PEP 398
end-of-life
2012-09-29
2017-09-29
Georg Brandl, Ned Deily [3.3.7+]
3.2
PEP 392
end-of-life
2011-02-20
2016-02-20
Georg Brandl
3.1
PEP 375
end-of-life
2009-06-27
2012-04-09
Benjamin Peterson
3.0
PEP 361
end-of-life
2008-12-03
2009-06-27
Barry Warsaw
2.7
PEP 373
end-of-life
2010-07-03
2020-01-01
Benjamin Peterson
2.6
PEP 361
end-of-life
2008-10-01
2013-10-29
Barry Warsaw
Status key
feature:
new features, bugfixes, and security fixes are accepted.
prerelease:
feature fixes, bugfixes, and security fixes are accepted for the upcoming feature release.
bugfix:
bugfixes and security fixes are accepted, new binaries are still released. [Also called maintenance mode or stable release]
security:
only security fixes are accepted and no more binaries are released, but new source-only versions can be released
end-of-life:
release cycle is frozen; no further changes can be pushed to it.
See also the page for more information about branches and backporting.
By default, the end-of-life is scheduled 5 years after the first release, but can be adjusted by the release manager of each branch. All Python 2 versions have reached end-of-life.