Python (programming language): Difference between revisions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
imported>Erictleung
Undid revision 1297037589 by Zaamin Khan (talk) Context for GIL is important to understand PEP feature
imported>Hooman Mallahzadeh
Memory management in Infobox.
Line 1: Line 1:
{{Short description|General-purpose programming language}}
{{Multiple issues|{{Update|reason=Information related to stable Python version 3.14.0 is not present|date=October 2025}}{{Cleanup list|date=October 2025}}}}{{Short description|General-purpose programming language}}
{{Use dmy dates|date=November 2021}}
{{Use dmy dates|date=November 2021}}
{{Use American English|date=December 2024}}
{{Use American English|date=December 2024}}
Line 5: Line 5:
| logo = Python-logo-notext.svg
| logo = Python-logo-notext.svg
| logo size = 150px
| logo size = 150px
| paradigm = [[Multi-paradigm]]: [[object-oriented]],<ref>{{Cite web|title=General Python FAQ – Python 3 documentation|url=https://docs.python.org/3/faq/general.html#what-is-python|access-date=2024-07-07|website=docs.python.org}}</ref> [[Procedural programming|procedural]] ([[Imperative programming|imperative]]), [[Functional programming|functional]], [[Structured programming|structured]], [[Reflective programming|reflective]]
| paradigm = [[Multi-paradigm]]: [[Object-oriented programming|object-oriented]],<ref>{{Cite web |title=General Python FAQ – Python 3 documentation |url=https://docs.python.org/3/faq/general.html#what-is-python |access-date=7 July 2024 |website=docs.python.org}}</ref> [[Procedural programming|procedural]] ([[Imperative programming|imperative]]), [[Functional programming|functional]], [[Structured programming|structured]], [[Reflective programming|reflective]]
| released = {{start date and age|1991|02|20|df=y}}<ref name="alt-sources-history">{{cite web |url=https://www.tuhs.org/Usenet/alt.sources/1991-February/001749.html |title=Python 0.9.1 part 01/21 |publisher=alt.sources archives |access-date=2021-08-11 |archive-date=11 August 2021 |archive-url=https://web.archive.org/web/20210811171015/https://www.tuhs.org/Usenet/alt.sources/1991-February/001749.html |url-status=live}}</ref>
| released = {{start date and age|1991|02|20|df=y}}<ref name="alt-sources-history">{{cite web |title=Python 0.9.1 part 01/21 |url=https://www.tuhs.org/Usenet/alt.sources/1991-February/001749.html |url-status=live |archive-url=https://web.archive.org/web/20210811171015/https://www.tuhs.org/Usenet/alt.sources/1991-February/001749.html |archive-date=11 August 2021 |access-date=11 August 2021 |publisher=alt.sources archives}}</ref>
| designer = [[Guido van Rossum]]
| designer = [[Guido van Rossum]]
| developer = [[Python Software Foundation]]
| developer = [[Python Software Foundation]]
| latest release version = {{wikidata|property|P548=Q2804309|P348}}
| latest release version = {{wikidata|property|edit|reference|P548=Q2804309|P348}}
| latest release date = {{start date and age|{{wikidata|qualifier|single|P548=Q2804309|P348|P577}}}}
| latest release date = {{start date and age|{{wikidata|qualifier|single|P548=Q2804309|P348|P577}}}}
| latest preview version = {{wikidata|property|edit|reference|P548=Q51930650|P348}}
| latest preview version = <!-- 3.15.0a1 on 15 October 2025 {{wikidata|property|edit|reference|P548=Q51930650|P348}} doesn't work, nor what AI suggested as fix: {{#invoke:Wikidata | claim | P348 | qualifier = P548:Q51930650 | rank = best }} -->
| latest preview date = {{start date and age|{{wikidata|qualifier|single|P548=Q51930650|P348|P577}}}}
| latest preview date = {{start date and age|2025|08|18|df=y}} <!-- {{start date and age|{{wikidata|qualifier|Q28865 |P548=Q51930650|P348|P577}}}} nor
| typing = [[Duck typing|duck]], [[Dynamic typing|dynamic]], [[Strong and weak typing|strong]];<ref>{{Cite web|title=Why is Python a dynamic language and also a strongly typed language |url=https://wiki.python.org/moin/Why%20is%20Python%20a%20dynamic%20language%20and%20also%20a%20strongly%20typed%20language|access-date=2021-01-27|website=Python Wiki |archive-date=14 March 2021|archive-url=https://web.archive.org/web/20210314173706/https://wiki.python.org/moin/Why%20is%20Python%20a%20dynamic%20language%20and%20also%20a%20strongly%20typed%20language|url-status=live}}</ref> [[Optional typing|optional type annotations]] (since 3.5, but those hints are ignored, except with unofficial tools)<ref name="type_hint-PEP">{{cite web|url=https://www.python.org/dev/peps/pep-0483/|title=PEP 483 – The Theory of Type Hints|website=Python.org|access-date=14 June 2018|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614153558/https://www.python.org/dev/peps/pep-0483/|url-status=live}}</ref>
{{#invoke:Wikidata | qualifier | P348 | P577 | qualifier = P548:Q51930650 | rank = best | formatting = date }}
| implementations = [[CPython]], [[PyPy]], [[Stackless Python]], [[MicroPython]], [[CircuitPython]], [[IronPython]], [[Jython]]
-->
| operating system = {{plainlist|
| typing = [[Duck typing|Duck]], [[Dynamic typing|dynamic]], [[Strong and weak typing|strong]];<ref>{{Cite web |title=Why is Python a dynamic language and also a strongly typed language |url=https://wiki.python.org/moin/Why%20is%20Python%20a%20dynamic%20language%20and%20also%20a%20strongly%20typed%20language |url-status=live |archive-url=https://web.archive.org/web/20210314173706/https://wiki.python.org/moin/Why%20is%20Python%20a%20dynamic%20language%20and%20also%20a%20strongly%20typed%20language |archive-date=14 March 2021 |access-date=27 January 2021 |website=Python Wiki}}</ref> [[Optional typing|optional type annotations]]{{efn|since 3.5, but those hints are ignored, except with unofficial tools<ref name="type_hint-PEP">{{cite web |last1=van Rossum |first1=Guido |last2=Levkivskyi |first2=Ivan |title=PEP 483 – The Theory of Type Hints |url=https://www.python.org/dev/peps/pep-0483/ |url-status=live |archive-url=https://web.archive.org/web/20200614153558/https://www.python.org/dev/peps/pep-0483/ |archive-date=14 June 2020 |access-date=14 June 2018 |website=Python Enhancement Proposals (PEPs)}}</ref>}}
*'''Tier 1''': 64-bit [[Linux]], [[macOS]]; 64- and 32-bit [[Windows]] 10+<ref>{{Cite web |title=PEP 11 – CPython platform support {{!}} peps.python.org |url=https://peps.python.org/pep-0011/ |access-date=2024-04-22 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref><!-- Not "Windows for IoT and embedded systems"; NOT UNIX, it's not listed, nor any Unix-like, maybe implied Possibly Windows 8.1 is also supported on at least Python 3.9? Might also work on latest, seems too minor to mention, for any Python version. Windows 7 and 8 are prevented to work on Python 3.9, though it might not rule out 8.1, also some info like this might be a bit wrong:
| memory management = [[Garbage collection (computer science)|Garbage-collected]]
| implementations = [[CPython]], [[PyPy]], [[MicroPython]], [[CircuitPython]], [[IronPython]], [[Jython]], [[Stackless Python]]
| operating system = [[Cross-platform]] including 32-bit [[Windows&nbsp;10]]<!-- with latest Python 3.14, Win8.1 still supported with older --> and e.g. for mobile; [[Android (operating system)|Android]] and [[iOS]] <small>(both 64-bit)</small><!-- downloadable official Python 3.14 Android binary executable available; still only tier 3 support. Strangely I find only Android, no iOS, official executable download despite it has "arm64-apple-ios" tier 3 support, so only downloadable as source code; and as unofficial iOS/iPadOS download?! -->{{efn|
* '''Tier 1''': 64-bit [[Linux]], [[macOS]]; 64- and 32-bit [[Windows&nbsp;8.1]] and later with older Python versions<!-- Windows 8.1 supported with 3.10 to 3.13 but only Windows 10+ with latest Python 3.14)+<ref>{{Cite web |last1=von Löwis |first1=Martin |last2=Cannon |first2=Brett |title=PEP 11 – CPython platform support |url=https://peps.python.org/pep-0011/ |access-date=22 April 2024 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref><!-- Not "Windows for IoT and embedded systems"; NOT UNIX, it's not listed, nor any Unix-like, maybe implied Possibly Windows 8.1 is also supported on at least Python 3.9? Might also work on latest, seems too minor to mention, for any Python version. Windows 7 and 8 are prevented to work on Python 3.9, though it might not rule out 8.1, also some info like this might be a bit wrong:


"Windows 8 and newer for Python 3.9
"Windows 8 and newer for Python 3.9
Line 22: Line 25:
macOS Snow Leopard (macOS 10.6, 2008) and newer"
macOS Snow Leopard (macOS 10.6, 2008) and newer"
-->
-->
*'''Tier 2''': E.g. 32-bit [[WebAssembly]] (WASI) <!-- (WASI SDK, Wasmtime) meaning wasm32-unknown-wasi; wasm32-unknown-emscripten is unsupported since 3.13. aarch64-pc-windows-msvc and powerpc64le-unknown-linux-gnu -->
* '''Tier 2''': E.g. 32-bit [[WebAssembly]] (WASI) <!-- (WASI SDK, Wasmtime) meaning wasm32-unknown-wasi; wasm32-unknown-emscripten is unsupported since 3.13. aarch64-pc-windows-msvc and powerpc64le-unknown-linux-gnu -->
*'''Tier 3''': 64-bit [[Android (operating system)|Android]]<!-- too much trivia to mention "5.0+", even if true, it seemingly is, and corresponding API levels, but thouse are ancient, possibly even only way more recent is officially supported? -->,<ref>{{Cite web |title=PEP 738 – Adding Android as a supported platform {{!}} peps.python.org |url=https://peps.python.org/pep-0738/ |access-date=2024-05-19 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref> [[iOS]], [[FreeBSD]], and (32-bit) [[Raspberry Pi OS]]<br />Unofficial (or has been known to work): Other [[Unix-like]]/[[BSD]] variants) and a few other platforms<!-- Used to support many more, only few support latest 3.9+ --><ref>{{Cite web |title=Download Python for Other Platforms |url=https://www.python.org/download/other/ |access-date=2023-08-18 |website=Python.org |language=en |archive-date=27 November 2020 |archive-url=https://web.archive.org/web/20201127015815/https://www.python.org/download/other/ |url-status=live}}</ref><ref>{{Cite web |title=test – Regression tests package for Python – Python 3.7.13 documentation |url=https://docs.python.org/3.7/library/test.html?highlight=android#test.support.is_android |access-date=2022-05-17 |website=docs.python.org |archive-date=17 May 2022 |archive-url=https://web.archive.org/web/20220517151240/https://docs.python.org/3.7/library/test.html?highlight=android#test.support.is_android |url-status=live}}</ref><ref>{{Cite web |title=platform – Access to underlying platform's identifying data – Python 3.10.4 documentation |url=https://docs.python.org/3/library/platform.html?highlight=android |access-date=2022-05-17 |website=docs.python.org |archive-date=17 May 2022 |archive-url=https://web.archive.org/web/20220517150826/https://docs.python.org/3/library/platform.html?highlight=android |url-status=live}}</ref>}}
* '''Tier 3''': 64-bit [[Android (operating system)|Android]]<!-- too much trivia to mention "5.0+", even if true, it seemingly is, and corresponding API levels, but thouse are ancient, possibly even only way more recent is officially supported? -->,<ref>{{Cite web |title=PEP 738 – Adding Android as a supported platform {{!}} peps.python.org |url=https://peps.python.org/pep-0738/ |access-date=19 May 2024 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref> [[iOS]], [[FreeBSD]], and (32-bit) [[Raspberry Pi OS]]<br />Unofficial (or has been known to work): Other [[Unix-like]]/[[BSD]] variants) and a few other platforms<!-- Used to support many more, only few support latest 3.9+ --><ref name="DownloadOther">{{Cite web |title=Download Python for Other Platforms |url=https://www.python.org/download/other/ |url-status=live |archive-url=https://web.archive.org/web/20201127015815/https://www.python.org/download/other/ |archive-date=27 November 2020 |access-date=18 August 2023 |website=Python.org |language=en}}</ref><ref>{{Cite web |title=test – Regression tests package for Python |url=https://docs.python.org/3.7/library/test.html?highlight=android#test.support.is_android |url-status=live |archive-url=https://web.archive.org/web/20220517151240/https://docs.python.org/3.7/library/test.html?highlight=android#test.support.is_android |archive-date=17 May 2022 |access-date=17 May 2022 |website=Python 3.7.17 documentation}}</ref><ref>{{Cite web |title=platform – Access to underlying platform's identifying data |url=https://docs.python.org/3.10/library/platform.html?highlight=android |url-status=live |archive-url=https://web.archive.org/web/20220517150826/https://docs.python.org/3/library/platform.html?highlight=android |archive-date=17 May 2022 |access-date=17 May 2022 |website=Python 3.10.4 documentation}}</ref>}}


<!--
<!--
https://mail.python.org/archives/list/python-committers@python.org/thread/K757345KX6W5ZLTWYBUXOXQTJJTL7GW5/
https://mail.python.org/archives/list/python-committers@python.org/thread/K757345KX6W5ZLTWYBUXOXQTJJTL7GW5/
* Alpine / musl is not supported, because our test suite is failing due to bugs and missing features in musl libc.
* Alpine / musl is not supported, because our test suite is failing due to bugs and missing features in musl libc.
* NetBSD and OpenBSD are in a similar state as Alpine: no stable buildbot and AFAIK tests are failing
* NetBSD and OpenBSD are in a similar state as Alpine: no stable buildbot and AFAIK tests are failing
Line 39: Line 41:
..
..


E.g. Android support was even funded by the PSF recently. [outdated]
E.g. Android support was even funded by the PSF recently.[outdated]
Also note that the stdlib does in fact support other Python implementations reusing (parts of) it, e.g. Jython, PyPy and IronPython. Again, without core devs backing these.
Also, note that the stdlib does in fact support other Python implementations reusing (parts of) it, e.g. Jython, PyPy and IronPython. Again, without core devs backing these.
-->
-->| license = [[Python Software Foundation License]]
| license = [[Python Software Foundation License]]
| file ext = .py, .pyw, .pyz,<!-- Too much trivia?: (since 3.5), since 3.8 latest supported and Python 3.5.10 Sept. 5, 2020--><ref>{{cite web |last1=Holth |first1=Daniel |last2=Moore |first2=Paul |date=30 March 2014 |title=PEP 0441 – Improving Python ZIP Application Support |url=https://www.python.org/dev/peps/pep-0441/ |url-status=live |archive-url=https://web.archive.org/web/20181226141117/https://www.python.org/dev/peps/pep-0441/%20 |archive-date=26 December 2018 |access-date=12 November 2015 |website=Python Enhancement Proposals (PEPs)}}</ref><br />
| file ext = .py, .pyw, .pyz,<!-- Too much trivia?: (since 3.5), since 3.8 latest supported and Python 3.5.10 Sept. 5, 2020--><ref>{{cite web |url=https://www.python.org/dev/peps/pep-0441/ |last=Holth |first=Moore |date=30 March 2014 |access-date=12 November 2015 |title=PEP 0441 – Improving Python ZIP Application Support |archive-date=26 December 2018 |archive-url=https://web.archive.org/web/20181226141117/https://www.python.org/dev/peps/pep-0441/%20 |url-status=live}}</ref><br />
.pyi, .pyc, .pyd<!-- too much trivia: .pyo (before 3.5)<ref>File extension .pyo was removed in Python 3.5. See [https://www.python.org/dev/peps/pep-0488/ PEP 0488] {{Webarchive|url=https://web.archive.org/web/20200601133202/https://www.python.org/dev/peps/pep-0488/ |date=1 June 2020}}</ref> -->
.pyi, .pyc, .pyd<!-- too much trivia: .pyo (before 3.5)<ref>File extension .pyo was removed in Python 3.5. See [https://www.python.org/dev/peps/pep-0488/ PEP 0488] {{Webarchive|url=https://web.archive.org/web/20200601133202/https://www.python.org/dev/peps/pep-0488/ |date=1 June 2020}}</ref> -->
| website = {{URL|https://www.python.org/|python.org}}
| website = {{URL|https://www.python.org/|python.org}}
| dialects = [[Cython]], [[RPython]], [[Bazel (software)|Starlark]]<ref>{{cite web|title=Starlark Language|url=https://docs.bazel.build/versions/master/skylark/language.html|access-date=25 May 2019|archive-date=15 June 2020|archive-url=https://web.archive.org/web/20200615140534/https://docs.bazel.build/versions/master/skylark/language.html|url-status=live}}</ref>
| dialects = [[Cython]], [[RPython]], [[Starlark]]<ref>{{cite web |title=Starlark Language |url=https://docs.bazel.build/versions/master/skylark/language.html |url-status=live |archive-url=https://web.archive.org/web/20200615140534/https://docs.bazel.build/versions/master/skylark/language.html |archive-date=15 June 2020 |access-date=25 May 2019 |website=bazel.build}}</ref>
| influenced by = [[ABC (programming language)|ABC]],<ref name="faq-created"/> [[Ada (programming language)|Ada]],<ref>{{cite web |url=https://archive.adaic.com/standards/83lrm/html/lrm-11-03.html#11.3 |title=Ada 83 Reference Manual (raise statement) |access-date=7 January 2020 |archive-date=22 October 2019 |archive-url=https://web.archive.org/web/20191022155758/http://archive.adaic.com/standards/83lrm/html/lrm-11-03.html#11.3 |url-status=live}}</ref> [[ALGOL 68]],<ref name="98-interview"/> <br />[[APL (programming language)|APL]],<ref name="python.org">{{cite web|url=https://docs.python.org/3/library/itertools.html|title=itertools – Functions creating iterators for efficient looping – Python 3.7.1 documentation|website=docs.python.org|access-date=22 November 2016|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614153629/https://docs.python.org/3/library/itertools.html |quote=This module implements a number of iterator building blocks inspired by constructs from APL, Haskell, and SML. |url-status=live}}</ref> [[C (programming language)|C]],<ref name="AutoNT-1"/> [[C++]],<ref name="classmix"/> [[CLU (programming language)|CLU]],<ref name="effbot-call-by-object"/> [[Dylan (programming language)|Dylan]],<ref name="AutoNT-2"/> <br />[[Haskell]],<ref name="AutoNT-3"/><ref name="python.org"/> [[Icon (programming language)|Icon]],<ref name="AutoNT-4"/> [[Lisp (programming language)|Lisp]],<ref name="AutoNT-6"/> {{nowrap|<br />[[Modula-3]]}},{{r|98-interview}}<ref name="classmix"/> [[Perl]],<ref>{{cite web |title=re – Regular expression operations – Python 3.10.6 documentation |url=https://docs.python.org/3/library/re.html |website=docs.python.org |access-date=2022-09-06 |quote=This module provides regular expression matching operations similar to those found in Perl. |archive-date=18 July 2018 |archive-url=https://web.archive.org/web/20180718132241/https://docs.python.org/3/library/re.html |url-status=live}}</ref> [[Standard ML]]<ref name="python.org"/>
| influenced by = [[ABC (programming language)|ABC]],<ref name="faq-created" /> [[Ada (programming language)|Ada]],<ref>{{cite web |title=Ada 83 Reference Manual (raise statement) |url=https://archive.adaic.com/standards/83lrm/html/lrm-11-03.html#11.3 |url-status=live |archive-url=https://web.archive.org/web/20191022155758/http://archive.adaic.com/standards/83lrm/html/lrm-11-03.html#11.3 |archive-date=22 October 2019 |access-date=7 January 2020 |website=archive.adaic.com}}</ref>{{failed verification|date=August 2025|reason=The source does not talk about Python. The "raise" keyword it describes is very similar to the Python version, but this is original research (see WP:OR).}} {{nowrap|[[ALGOL 68]]}},<ref name="98-interview" /> [[APL (programming language)|APL]],<ref name="python.org">{{cite web |title=itertools – Functions creating iterators for efficient looping |url=https://docs.python.org/3.7/library/itertools.html |url-status=live |archive-url=https://web.archive.org/web/20200614153629/https://docs.python.org/3/library/itertools.html |archive-date=14 June 2020 |access-date=22 November 2016 |website=Python 3.7.17 documentation |quote=This module implements a number of iterator building blocks inspired by constructs from APL, Haskell, and SML.}}</ref> [[C (programming language)|C]],<ref name="AutoNT-1" /> [[C++]],<ref name="classmix" /> [[CLU (programming language)|CLU]],<ref name="effbot-call-by-object" /> [[Dylan (programming language)|Dylan]],<ref name="AutoNT-2" /> [[Haskell]],<ref name="AutoNT-3" /><ref name="python.org" /> [[Icon (programming language)|Icon]],<ref name="AutoNT-4" /> [[Lisp (programming language)|Lisp]],<ref name="AutoNT-6" /> {{nowrap|[[Modula-3]]}},{{r |98-interview}}<ref name="classmix" /> [[Perl]],<ref>{{cite web |title=re – Regular expression operations |url=https://docs.python.org/3.10/library/re.html |url-status=live |archive-url=https://web.archive.org/web/20180718132241/https://docs.python.org/3/library/re.html |archive-date=18 July 2018 |access-date=6 September 2022 |website=Python 3.10.6 documentation |quote=This module provides regular expression matching operations similar to those found in Perl.}}</ref> [[Standard ML]]<ref name="python.org" />
| influenced = [[Apache Groovy]], [[Boo (programming language)|Boo]], [[Cobra (programming language)|Cobra]], [[CoffeeScript]],<ref>{{Cite web|url=https://coffeescript.org/|title=CoffeeScript|website=coffeescript.org|access-date=3 July 2018|archive-date=12 June 2020|archive-url=https://web.archive.org/web/20200612100004/http://coffeescript.org/|url-status=live}}</ref> [[D (programming language)|D]], [[F Sharp (programming language)|F#]], [[GDScript]], [[Go (programming language)|Go]], [[JavaScript]],<ref>{{cite web
| influenced = [[Apache Groovy]], [[Boo (programming language)|Boo]], [[Cobra (programming language)|Cobra]], [[CoffeeScript]],<ref>{{Cite web |title=CoffeeScript |url=https://coffeescript.org/ |url-status=live |archive-url=https://web.archive.org/web/20200612100004/http://coffeescript.org/ |archive-date=12 June 2020 |access-date=3 July 2018 |website=coffeescript.org}}</ref> [[D (programming language)|D]], [[F Sharp (programming language)|F#]], [[GDScript]], [[Go (programming language)|Go]], [[JavaScript]],<ref>{{cite web |last=Rauschmayer |first=Axel |date=24 February 2013 |title=Perl and Python influences in JavaScript |url=https://www.2ality.com/2013/02/javascript-influences.html |url-status=live |archive-url=https://web.archive.org/web/20181226141121/http://2ality.com/2013/02/javascript-influences.html%0A |archive-date=26 December 2018 |access-date=15 May 2015 |website=2ality.com}}</ref><ref>{{cite web |last=Rauschmayer |first=Axel |title=Chapter 3: The Nature of JavaScript; Influences |url=https://speakingjs.com/es5/ch03.html |url-status=live |archive-url=https://web.archive.org/web/20181226141123/http://speakingjs.com/es5/ch03.html%0A |archive-date=26 December 2018 |access-date=15 May 2015 |website=Speaking JavaScript |publisher=O'Reilly}}</ref> [[Julia (programming language)|Julia]],<ref name="Julia">{{cite web |last1=Bezanson |first1=Jeff |last2=Karpinski |first2=Stefan |last3=Shah |first3=Viral B. |last4=Edelman |first4=Alan |date=February 2012 |title=Why We Created Julia |url=https://julialang.org/blog/2012/02/why-we-created-julia |url-status=live |archive-url=https://web.archive.org/web/20200502144010/https://julialang.org/blog/2012/02/why-we-created-julia/ |archive-date=2 May 2020 |access-date=5 June 2014 |website=Julia website |quote=We want something as usable for general programming as Python [...]}}</ref> [[Mojo (programming language)|Mojo]],<ref name="Mojo">{{Cite web |last=Krill |first=Paul |date=4 May 2023 |title=Mojo language marries Python and MLIR for AI development |url=https://www.infoworld.com/article/3695588/mojo-language-marries-python-and-mlir-for-ai-development.html |url-status=live |archive-url=https://web.archive.org/web/20230505064554/https://www.infoworld.com/article/3695588/mojo-language-marries-python-and-mlir-for-ai-development.html |archive-date=5 May 2023 |access-date=5 May 2023 |website=InfoWorld |language=en}}</ref> [[Nim (programming language)|Nim]], [[Ring (programming language)|Ring]],<ref name="The Ring programming language and other languages">{{cite web |author=Ring Team |date=4 December 2017 |title=Ring and other languages |url=https://ring-lang.sourceforge.net/doc1.6/introduction.html#ring-and-other-languages |url-status=dead |archive-url=https://web.archive.org/web/20181225175312/http://ring-lang.sourceforge.net/doc1.6/introduction.html#ring-and-other-languages |archive-date=25 December 2018 |access-date=4 December 2017 |work=ring-lang.net |publisher=[[ring-lang]]}}</ref> [[Ruby (programming language)|Ruby]],<ref name="bini" /> [[Swift (programming language)|Swift]],<ref name="lattner2014">{{Cite web |last=Lattner |first=Chris |date=3 June 2014 |title=Chris Lattner's Homepage |url=http://nondot.org/sabre/ |url-status=live |archive-url=https://web.archive.org/web/20181225175312/http://nondot.org/sabre/ |archive-date=25 December 2018 |access-date=3 June 2014 |publisher=Chris Lattner |quote=The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.}}</ref> [[V (programming language)|V]]<ref name="vpeople">{{Cite web |title=V documentation (Introduction) |url=https://github.com/vlang/v/blob/master/doc/docs.md#introduction |access-date=24 December 2024 |website=GitHub |language=en}}</ref>
  |title=Perl and Python influences in JavaScript
<!-- Do not put in as there's a pure Java implementation (Jython): | programming language = [[C (programming language)|C]] -->| wikibooks = Python Programming
  |date=24 February 2013
  |website=www.2ality.com
  |url=https://www.2ality.com/2013/02/javascript-influences.html
  |access-date=15 May 2015
  |archive-date=26 December 2018
  |archive-url=https://web.archive.org/web/20181226141121/http://2ality.com/2013/02/javascript-influences.html%0A
  |url-status=live
  }}</ref><ref>{{cite web
  |title=Chapter 3: The Nature of JavaScript; Influences
  |last=Rauschmayer
  |first=Axel
  |website=O'Reilly, Speaking JavaScript
  |url=http://speakingjs.com/es5/ch03.html
  |access-date=15 May 2015
  |archive-date=26 December 2018
  |archive-url=https://web.archive.org/web/20181226141123/http://speakingjs.com/es5/ch03.html%0A
  |url-status=live
  }}</ref> [[Julia (programming language)|Julia]],<ref name=Julia/> [[Mojo (programming language)|Mojo]],<ref name="Mojo">{{Cite web |last=Krill |first=Paul |date=2023-05-04 |title=Mojo language marries Python and MLIR for AI development |url=https://www.infoworld.com/article/3695588/mojo-language-marries-python-and-mlir-for-ai-development.html |access-date=2023-05-05 |website=InfoWorld |language=en |archive-date=5 May 2023 |archive-url=https://web.archive.org/web/20230505064554/https://www.infoworld.com/article/3695588/mojo-language-marries-python-and-mlir-for-ai-development.html |url-status=live}}</ref> [[Nim (programming language)|Nim]], [[Ring (programming language)|Ring]],<ref name="The Ring programming language and other languages">{{cite web |url=https://ring-lang.sourceforge.net/doc1.6/introduction.html#ring-and-other-languages |title=Ring and other languages |author=Ring Team |date=4 December 2017 |work=ring-lang.net |publisher=[[ring-lang]] |access-date=4 December 2017 |archive-date=25 December 2018 |archive-url=https://web.archive.org/web/20181225175312/http://ring-lang.sourceforge.net/doc1.6/introduction.html#ring-and-other-languages |url-status=live}}</ref> [[Ruby (programming language)|Ruby]],<ref name="bini"/> [[Swift (programming language)|Swift]],<ref name="lattner2014">{{Cite web |url=http://nondot.org/sabre/ |title=Chris Lattner's Homepage |last=Lattner |first=Chris |date=3 June 2014 |access-date=3 June 2014 |publisher=Chris Lattner |quote=The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list. |archive-date=25 December 2018 |archive-url=https://web.archive.org/web/20181225175312/http://nondot.org/sabre/ |url-status=live}}</ref> [[V (programming language)|V]]<ref name="vpeople">{{Cite web |title=V documentation (Introduction) |url=https://github.com/vlang/v/blob/master/doc/docs.md#introduction |access-date=2024-12-24|website=GitHub |language=en}}</ref>
<!-- Do not put in as there's also a pure Java implementation (Jython): | programming language = [[C (programming language)|C]] -->
| wikibooks = Python Programming
}}
}}
{{Template:Python sidebar}}


'''Python''' is a [[high-level programming language|high-level]], [[general-purpose programming language]]. Its design philosophy emphasizes [[code readability]] with the use of [[significant indentation]].<ref name="AutoNT-7"/>
'''Python''' is a [[high-level programming language|high-level]], [[general-purpose programming language]]. Its design philosophy emphasizes [[code readability]] with the use of [[significant indentation]].<ref name="AutoNT-7" /> Python is [[type system#DYNAMIC|dynamically type-checked]] and [[garbage collection (computer science)|garbage-collected]]. It supports multiple [[programming paradigm]]s, including [[structured programming|structured]] (particularly [[procedural programming|procedural]]), [[Object-oriented programming|object-oriented]] and [[functional programming]].
 
Python is [[type system#DYNAMIC|dynamically type-checked]] and [[garbage collection (computer science)|garbage-collected]]. It supports multiple [[programming paradigm]]s, including [[structured programming|structured]] (particularly [[procedural programming|procedural]]), [[object-oriented]] and [[functional programming]]. It is often described as a "batteries included" language due to its comprehensive [[standard library]].<ref name="About"/><ref>{{Cite web|title=PEP 206 – Python Advanced Library|url=https://www.python.org/dev/peps/pep-0206/|url-status=live|archive-url=https://web.archive.org/web/20210505003659/https://www.python.org/dev/peps/pep-0206/|archive-date=5 May 2021|access-date=11 October 2021|website=Python.org}}</ref>


[[Guido van Rossum]] began working on Python in the late 1980s as a successor to the [[ABC (programming language)|ABC]] programming language, and he first released it in 1991 as Python&nbsp;0.9.0.<ref>{{Cite web|last=Rossum|first=Guido Van|date=2009-01-20|title=The History of Python: A Brief Timeline of Python|url=https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html|access-date=2021-03-05|website=The History of Python|archive-date=5 June 2020|archive-url=https://web.archive.org/web/20200605032200/https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html|url-status=live}}</ref> Python&nbsp;2.0 was released in 2000. Python&nbsp;3.0, released in 2008, was a major revision not completely [[backward-compatible]] with earlier versions. Python&nbsp;2.7.18, released in 2020, was the last release of Python&nbsp;2.<ref>{{Cite web|url=https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html|title= Python 2.7.18, the last release of Python 2|last=Peterson|first=Benjamin|date=20 April 2020|website=Python Insider|access-date=27 April 2020|archive-date=26 April 2020|archive-url=https://web.archive.org/web/20200426204118/https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html|url-status=live}}</ref>
[[Guido van Rossum]] began working on Python in the late 1980s as a successor to the [[ABC (programming language)|ABC]] programming language. Python&nbsp;3.0, released in 2008, was a major revision and not completely [[backward-compatible]] with earlier versions. Beginning with Python 3.5,<ref>{{cite web |title=PEP 484 – Type Hints |url=https://peps.python.org/pep-0484/ |website=Python Enhancement Proposals |access-date=27 October 2025 |language=en}}</ref> capabilities and keywords for typing were added to the language, allowing optional [[static typing]].<ref>{{Cite web |title=mypy – Optional Static Typing for Python |url=https://mypy-lang.org/ |access-date=17 August 2025 |website=mypy-lang.org}}</ref> Currently only versions in the 3.x series are supported.


Python consistently ranks as one of the most popular programming languages, and it has gained widespread use in the [[machine learning]] community.<ref>{{Cite web |title=Stack Overflow Developer Survey 2022 |url=https://survey.stackoverflow.co/2022/ |access-date=2022-08-12 |website=Stack Overflow |language=en |archive-date=27 June 2022 |archive-url=https://web.archive.org/web/20220627175307/https://survey.stackoverflow.co/2022/ |url-status=live}}</ref><ref>{{Cite web|title=The State of Developer Ecosystem in 2020 Infographic|url=https://www.jetbrains.com/lp/devecosystem-2020/|access-date=2021-03-05|website=JetBrains: Developer Tools for Professionals and Teams|language=en|archive-date=1 March 2021|archive-url=https://web.archive.org/web/20210301062411/https://www.jetbrains.com/lp/devecosystem-2020/|url-status=live}}</ref><ref name="tiobecurrent">{{cite web |title=TIOBE Index |publisher=TIOBE |url=https://www.tiobe.com/tiobe-index/ |access-date=3 January 2023 |quote=The TIOBE Programming Community index is an indicator of the popularity of programming languages |archive-date=25 February 2018 |archive-url=https://web.archive.org/web/20180225101948/https://www.tiobe.com/tiobe-index/ |url-status=live}} Updated as required.</ref><ref>{{Cite web|title=PYPL PopularitY of Programming Language index|url=https://pypl.github.io/PYPL.html|access-date=2021-03-26|website=pypl.github.io|language=en|archive-date=14 March 2017|archive-url=https://web.archive.org/web/20170314232030/https://pypl.github.io/PYPL.html|url-status=live}}</ref>
Python has gained widespread use in the [[machine learning]] community.<ref>{{Cite web |title=Stack Overflow Developer Survey 2022 |url=https://survey.stackoverflow.co/2022/ |url-status=live |archive-url=https://web.archive.org/web/20220627175307/https://survey.stackoverflow.co/2022/ |archive-date=27 June 2022 |access-date=12 August 2022 |website=Stack Overflow |language=en}}</ref><ref>{{Cite web |title=The State of Developer Ecosystem in 2020 Infographic |url=https://www.jetbrains.com/lp/devecosystem-2020/ |url-status=live |archive-url=https://web.archive.org/web/20210301062411/https://www.jetbrains.com/lp/devecosystem-2020/ |archive-date=1 March 2021 |access-date=5 March 2021 |website=JetBrains |language=en}}</ref><ref name="tiobecurrent">{{cite web |title=TIOBE Index |url=https://www.tiobe.com/tiobe-index/ |url-status=live |archive-url=https://web.archive.org/web/20180225101948/https://www.tiobe.com/tiobe-index/ |archive-date=25 February 2018 |access-date=3 January 2023 |publisher=TIOBE |quote=The TIOBE Programming Community index is an indicator of the popularity of programming languages}} Updated as required.</ref><ref>{{Cite journal |last1=Healy |first1=John |last2=McInnes |first2=Leland |last3=Weir |first3=Colin |date=2017 |title=Bridging the Cyber-Analysis Gap: The Democratization of Data Science |journal=The Cyber Defense Review |volume=2 |issue=1 |pages=109–118 |issn=2474-2120 |jstor=26267404 |quote="Python is the lingua franca of data science and machine learning."}}</ref> It is widely taught as an introductory programming language.<ref>{{Cite journal |last1=Sultana |first1=Simon G. |last2=Reed |first2=Philip A. |date=2017 |title=Curriculum for an Introductory Computer Science Course: Identifying Recommendations from Academia and Industry |journal=The Journal of Technology Studies |volume=43 |issue=2 |pages=80–92 |doi=10.21061/jots.v43i2.a.3 |issn=1071-6084 |jstor=90023144}}</ref> Since 2003, Python has consistently ranked in the top ten of the most popular programming languages in the [[TIOBE Programming Community Index]], which ranks based on searches in 24 platforms.<ref>{{cite web |title=TIOBE Index |publisher=TIOBE |url=https://www.tiobe.com/tiobe-index/ |access-date=3 January 2023 |quote=The TIOBE Programming Community index is an indicator of the popularity of programming languages |archive-date=25 February 2018 |archive-url=https://web.archive.org/web/20180225101948/https://www.tiobe.com/tiobe-index/ |url-status=live}}</ref>


==History==
== History ==
{{Main|History of Python}}
{{Main|History of Python}}
[[File:Guido van Rossum in PyConUS24.jpg|thumb|311x311px|The designer of Python, [[Guido van Rossum]], at PyCon US 2024]]
[[File:Guido van Rossum in PyConUS24.jpg|thumb|311x311px|The designer of Python, [[Guido van Rossum]], at [[PyCon]] US 2024]]
Python was conceived in the late 1980s<ref name="venners-interview-pt-1"/> by [[Guido van Rossum]] at [[Centrum Wiskunde & Informatica]] (CWI) in the [[Netherlands]]; it was conceived as a successor to the [[ABC (programming language)|ABC]] programming language, which was inspired by [[SETL]],<ref name="AutoNT-12"/> capable of [[exception handling]] and interfacing with the [[Amoeba (operating system)|Amoeba]] operating system.<ref name="faq-created"/> Python implementation began in December,&nbsp;1989.<ref name="timeline-of-python"/> Van Rossum assumed sole responsibility for the project, as the lead developer, until 12 July 2018, when he announced his "permanent vacation" from responsibilities as Python's "[[benevolent dictator for life]]" (BDFL); this title was bestowed on him by the Python community to reflect his long-term commitment as the project's chief decision-maker.<ref name="lj-bdfl-resignation"/> (He has since come out of retirement and is self-titled "BDFL-emeritus"<!-- on his Twitter-->.) In January,&nbsp;2019, active Python core developers elected a five-member Steering Council to lead the project.<ref>{{cite web |title=PEP 8100 |url=https://www.python.org/dev/peps/pep-8100/ |publisher=Python Software Foundation |access-date=4 May 2019 |archive-date=4 June 2020 |archive-url=https://web.archive.org/web/20200604235027/https://www.python.org/dev/peps/pep-8100/ |url-status=live}}</ref><ref>{{Cite web|title=PEP 13 – Python Language Governance|url=https://www.python.org/dev/peps/pep-0013/|access-date=2021-08-25|website=Python.org|language=en|archive-date=27 May 2021|archive-url=https://web.archive.org/web/20210527000035/https://www.python.org/dev/peps/pep-0013/|url-status=live}}</ref>
Python was conceived in the late 1980s<ref name="venners-interview-pt-1" /> by [[Guido van Rossum]] at [[Centrum Wiskunde & Informatica]] (CWI) in the [[Netherlands]].<ref name="timeline-of-python" /> It was designed as a successor to the [[ABC (programming language)|ABC]] programming language, which was inspired by [[SETL]],<ref name="AutoNT-12" /> capable of [[exception handling]] and interfacing with the [[Amoeba (operating system)|Amoeba]] operating system.<ref name="faq-created" /> Python implementation began in December&nbsp;1989.<ref name="timeline-of-python" /> Van Rossum first released it in 1991 as Python&nbsp;0.9.0.<ref name="timeline-of-python" /> Van Rossum assumed sole responsibility for the project, as the lead developer, until 12 July 2018, when he announced his "permanent vacation" from responsibilities as Python's "[[benevolent dictator for life]]" (BDFL); this title was bestowed on him by the Python community to reflect his long-term commitment as the project's chief decision-maker.<ref name="lj-bdfl-resignation" /> (He has since come out of retirement and is self-titled "BDFL-emeritus"<!-- on his Twitter-->.) In January&nbsp;2019, active Python core developers elected a five-member Steering Council to lead the project.<ref>{{cite web |last1=Smith |first1=Nathaniel J. |last2=Durbin |first2=Ee |title=PEP 8100 – January 2019 Steering Council election |url=https://peps.python.org/pep-8100/ |url-status=live |archive-url=https://web.archive.org/web/20200604235027/https://www.python.org/dev/peps/pep-8100/ |archive-date=4 June 2020 |access-date=4 May 2019 |website=Python Enhancement Proposals (PEPs) |publisher=Python Software Foundation}}</ref><ref>{{Cite web |author=The Python core team and community |title=PEP 13 – Python Language Governance |url=https://peps.python.org/pep-0013/ |url-status=live |archive-url=https://web.archive.org/web/20210527000035/https://www.python.org/dev/peps/pep-0013/ |archive-date=27 May 2021 |access-date=25 August 2021 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref>
 
The name ''Python'' is said to derive from the British comedy series [[Monty Python's Flying Circus]].<ref name=":0">{{Cite book |last1=Briggs |first1=Jason R. |title=Python for kids: a playful introduction to programming |last2=Lipovača |first2=Miran |date=2013 |publisher=No Starch Press |isbn=978-1-59327-407-8 |location=San Francisco, Calif}}</ref>
 
Python 2.0 was released on 16 October 2000, with many major new features such as [[list comprehension]]s, [[cycle detection|cycle-detecting]] garbage collection, [[reference counting]], and [[Unicode]] support.<ref name="newin-2.0"/> Python 2.7's [[end-of-life product|end-of-life]] was initially set for 2015, and then postponed to 2020 out of concern that a large body of existing code could not easily be forward-ported to Python&nbsp;3.<ref>{{cite web |url=https://legacy.python.org/dev/peps/pep-0373/ |title=PEP 373 – Python 2.7 Release Schedule |work=python.org |access-date=9 January 2017 |archive-date=19 May 2020 |archive-url=https://web.archive.org/web/20200519075520/https://legacy.python.org/dev/peps/pep-0373/ |url-status=live}}</ref><ref>{{cite web |url=https://www.python.org/dev/peps/pep-0466/ |title=PEP 466 – Network Security Enhancements for Python 2.7.x |work=python.org |access-date=9 January 2017 |archive-date=4 June 2020 |archive-url=https://web.archive.org/web/20200604232833/https://www.python.org/dev/peps/pep-0466/ |url-status=live}}</ref> It no longer receives security patches or updates.<ref>{{Cite web|url=https://www.python.org/doc/sunset-python-2/|title=Sunsetting Python 2|website=Python.org|language=en|access-date=22 September 2019|archive-date=12 January 2020|archive-url=https://web.archive.org/web/20200112080903/https://www.python.org/doc/sunset-python-2/|url-status=live}}</ref><ref>{{Cite web|url=https://www.python.org/dev/peps/pep-0373/|title=PEP 373 – Python 2.7 Release Schedule|website=Python.org|language=en|access-date=22 September 2019|archive-date=13 January 2020|archive-url=https://web.archive.org/web/20200113033257/https://www.python.org/dev/peps/pep-0373/|url-status=live}}</ref> While Python 2.7 and older versions are officially unsupported, a different unofficial Python implementation, [[PyPy]], continues to support Python 2, i.e., "2.7.18+" (plus 3.10), with the plus signifying (at least some) "[[backporting|backported]] security updates".<ref>{{Cite web |last=mattip |date=2023-12-25 |title=PyPy v7.3.14 release |url=https://www.pypy.org/posts/2023/12/pypy-v7314-release.html |access-date=2024-01-05 |website=PyPy |language=en |archive-date=5 January 2024 |archive-url=https://web.archive.org/web/20240105132820/https://www.pypy.org/posts/2023/12/pypy-v7314-release.html |url-status=live}}</ref>
 
Python&nbsp;3.0 was released on 3 December 2008, with some new semantics and changed syntax. At least every Python release since (the now unsupported) 3.5 has added some syntax to the language; a few later releases have removed outdated modules and have changed semantics, at least in a minor way.
 
{{As of|2025|04|08|since=n}}, Python 3.13.3 is the latest stable release (it's highly recommended to upgrade to it, or upgrade any other older 3.x release). This version currently receives full bug-fix and security updates, while Python 3.12—released in October 2023—had active bug-fix support only until April 2025, and since then only security fixes. Python 3.9<ref>{{Cite web |last=Langa |first=Łukasz |date=2022-05-17 |title=Python 3.9.13 is now available |url=https://pythoninsider.blogspot.com/2022/05/python-3913-is-now-available.html |access-date=2022-05-21 |website=Python Insider |archive-date=17 May 2022 |archive-url=https://web.archive.org/web/20220517173546/https://pythoninsider.blogspot.com/2022/05/python-3913-is-now-available.html |url-status=live}}</ref> is the oldest supported version of Python (albeit in the 'security support' phase), because Python 3.8 has become an end-of-life product.<ref>{{Cite web |title=Status of Python versions |url=https://devguide.python.org/versions/ |access-date=2024-10-07 |website=Python Developer's Guide |language=en}}</ref><ref>{{Cite web |date=8 October 2024 |title=Python |url=https://endoflife.date/python |access-date=2024-11-20 |website=endoflife.date |language=en-US }}</ref> Starting with Python 3.13, it and later versions receive two years of full support (which has increased from one and a half years), followed by three years of security support; this is the same total duration of support as previously.
 
Security updates were expedited in 2021 and again twice in 2022. More issues were fixed in 2023 and in September 2024 (for Python versions 3.8.20 through 3.12.6)—all versions (including 2.7)<ref>{{Cite web|title=CVE-2021-3177 |url=https://access.redhat.com/security/cve/cve-2021-3177|access-date=2021-02-26|website=Red Hat Customer Portal |archive-date=6 March 2021|archive-url=https://web.archive.org/web/20210306183700/https://access.redhat.com/security/cve/cve-2021-3177|url-status=live}}</ref> had been insecure because of issues leading to possible [[remote code execution]]<ref>{{Cite web|title=CVE-2021-3177|url=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3177|access-date=2021-02-26|website=CVE|archive-date=27 February 2021|archive-url=https://web.archive.org/web/20210227192918/https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3177|url-status=live}}</ref> and [[cache poisoning|web-cache poisoning]].<ref>{{Cite web|title=CVE-2021-23336|url=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23336|access-date=2021-02-26|website=CVE|archive-date=24 February 2021|archive-url=https://web.archive.org/web/20210224160700/https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23336|url-status=live}}</ref> <!-- In 2022, Python&nbsp;3.10.4 and 3.9.12 were expedited<ref>{{Cite web |last=Langa |first=Łukasz |date=2022-03-24 |title=Python 3.10.4 and 3.9.12 are now available out of schedule |url=https://pythoninsider.blogspot.com/2022/03/python-3104-and-3912-are-now-available.html |access-date=2022-04-19 |website=Python Insider |archive-date=21 April 2022 |archive-url=https://web.archive.org/web/20220421205820/https://pythoninsider.blogspot.com/2022/03/python-3104-and-3912-are-now-available.html |url-status=live}}</ref> and 3.8.13, because of many security issues.<ref>{{Cite web |last=Langa |first=Łukasz |date=2022-03-16 |title=Python 3.10.3, 3.9.11, 3.8.13, and 3.7.13 are now available with security content |url=https://pythoninsider.blogspot.com/2022/03/python-3103-3911-3813-and-3713-are-now.html |access-date=2022-04-19 |website=Python Insider |archive-date=17 April 2022 |archive-url=https://web.archive.org/web/20220417215022/https://pythoninsider.blogspot.com/2022/03/python-3103-3911-3813-and-3713-are-now.html |url-status=live}}</ref> -->  <!-- On 7 September 2022, four new releases were made due to a potential [[denial-of-service attack]]: 3.10.7, 3.9.14, 3.8.14, and 3.7.14.<ref>{{Cite web |title=Python releases 3.10.7, 3.9.14, 3.8.14, and 3.7.14 are now available |work=Python Insider |first1=Łukasz |last1=Langa |date=7 September 2022 |access-date=16 September 2022 |url=https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html |archive-date=13 September 2022 |archive-url=https://web.archive.org/web/20220913001104/https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html |url-status=live}}</ref><ref>{{Cite web |title=CVE-2020-10735 |work=CVE |access-date=16 September 2022 |url=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735 |archive-date=20 September 2022 |archive-url=https://web.archive.org/web/20220920170528/https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735 |url-status=live}}</ref> -->
 
Python 3.10 added the <code>|</code> union type operator<ref>{{cite web | url=https://docs.python.org/3/library/stdtypes.html#types-union | title=Built-in Types }}</ref> and added structural [[pattern matching]] capability to the language, with the new <code>match</code> and <code>case</code> keywords.<ref>{{Cite web |title=PEP 634 – Structural Pattern Matching: Specification |url=https://www.python.org/dev/peps/pep-0634/ |url-status=live |archive-url=https://web.archive.org/web/20210506005315/https://www.python.org/dev/peps/pep-0634/ |archive-date=6 May 2021 |access-date=2021-02-14 |website=Python.org |language=en}}</ref> Python 3.11 expanded [[exception handling (programming)|exception handling]] functionality. Python 3.12 added the new keyword <code>type</code>. Notable changes from version 3.10 to 3.11 include increased program execution speed and improved error reporting.<ref>{{Cite web |title=Python 3.11 released [LWN.net] |author=corbet |work=lwn.net |date=24 October 2022 |access-date=15 November 2022 |url=https://lwn.net/Articles/912216/}}</ref> Python 3.11 is claimed to be 10–60% faster than Python 3.10, and Python 3.12 increases by an additional 5%. Python 3.12 also includes improved error messages (again improved in 3.14) and many other changes.
 
Python 3.13 introduced more syntax for types; a new and improved interactive interpreter ([[read–eval–print loop|REPL]]), featuring multi-line editing and color support; an incremental garbage collector, which results in shorter pauses for collection in programs that have many objects, as well as increasing the improved speed in 3.11 and 3.12); <!-- "A modified version of mimalloc is now included, optional but enabled by default if supported by the platform, and required for the free-threaded build mode." --> an ''experimental'' [[just-in-time compilation|just-in-time (JIT) compiler]] (such features need to be enabled specifically for the increase in speed);<ref>{{Cite web |title=What's New In Python 3.13 |url=https://docs.python.org/3.13/whatsnew/3.13.html#experimental-jit-compiler |access-date=2024-04-30 |website=Python documentation |language=en}}</ref> and an ''experimental'' free-threaded build mode, which disables the [[global interpreter lock]] (GIL), allowing threads to run more concurrently, as enabled in<code>python3.13t</code> or <code>python3.13t.exe</code>.
 
Python Enhancement Proposal (PEP) 711 proposes PyBI—a standard format for distributing Python binaries.<!--
"Like wheels, but instead of a pre-built python package, it's a pre-built python interpreter"
"A .pybi file is a zip file, that can be unpacked directly into an arbitrary location and then used as a self-contained Python environment. [..]
The "arbitrary location" part is important: the pybi can't contain any hardcoded absolute paths. In particular, any preinstalled scripts MUST NOT embed absolute paths in their shebang lines."--><ref>{{Cite web |date=2023-04-07 |title=PEP 711: PyBI: a standard format for distributing Python Binaries |url=https://discuss.python.org/t/pep-711-pybi-a-standard-format-for-distributing-python-binaries/25547 |access-date=2024-11-20 |website=Discussions on Python.org |language=en}}</ref>
 
Python 3.14.0 is now in the beta 1 phase (introduces e.g. a new opt-in interpreter, up to 30% faster).
 
Python 3.15 will "Make UTF-8 mode default";<ref>{{Cite web |title=PEP 686 – Make UTF-8 mode default {{!}} peps.python.org |url=https://peps.python.org/pep-0686/ |access-date=2024-11-20 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref> This mode is supported in all current Python versions, but it currently must be opted into. [[UTF-8]] is already used by default on Windows (and other operating systems) for most purposes; an exception is opening files. Enabling UTF-8 also makes code fully cross-platform.
 
;Potentially breaking changes
Python 3.0 introduced very breaking changes, but all breaking changes in 3.x discussed below, are designed to affect few users.
 
Python 3.12 dropped some outdated modules, and more will be dropped in the future, deprecated as of 3.13; already deprecated array 'u' format code will emit <code>DeprecationWarning</code> since 3.13 and will be removed in Python 3.16. The 'w' format code should be used instead. Part of ctypes is also deprecated and <code>http.server.CGIHTTPRequestHandler</code> will emit a DeprecationWarning, and will be removed in 3.15. Using that code already has a high potential for both security and functionality bugs. Parts of the typing module are deprecated, e.g. creating a <code>typing.NamedTuple</code> class using keyword arguments to denote the fields and such (and more) will be disallowed in Python 3.15. Python 3.12 removed <code>wstr</code> meaning Python extensions<ref>{{Cite web |title=1. Extending Python with C or C++ – Python 3.9.1 documentation |url=https://docs.python.org/3/extending/extending.html |url-status=live |archive-url=https://web.archive.org/web/20200623232830/https://docs.python.org/3/extending/extending.html |archive-date=23 June 2020 |access-date=2021-02-14 |website=docs.python.org}}</ref> need to be modified.<ref>{{Cite web |title=PEP 623 – Remove wstr from Unicode |url=https://www.python.org/dev/peps/pep-0623/ |url-status=live |archive-url=https://web.archive.org/web/20210305153214/https://www.python.org/dev/peps/pep-0623/ |archive-date=5 March 2021 |access-date=2021-02-14 |website=Python.org |language=en}}</ref>
 
Python 3.13 introduces some changes in behavior, i.e., new "well-defined semantics", fixing bugs, and removing many deprecated classes, functions and methods (as well as some of the Python/C API and outdated modules). <!-- PEP 594 (Removing dead batteries from the standard library) scheduled removals of many deprecated modules: aifc, audioop, chunk, cgi, cgitb, crypt, imghdr, mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau, telnetlib, uu, xdrlib, lib2to3.
Many other removals of deprecated classes, functions and methods in various standard library modules.
C API removals and deprecations.
-->"<!--In early versions of Python all namespaces, whether in functions, classes or modules, were all implemented the same way: as a dictionary.
..
-->The <!-- current --> old implementation of <code>locals()</code> and <code>frame.f_locals</code> was slow, inconsistent and buggy, <!--. We want to make it faster, consistent, and most importantly fix the bugs.
..
Worse than that, the current behavior can result in strange bugs.
There are no compensating advantages for the current behavior; it is unreliable and slow.
..
The current implementation --> and it had many corner cases and oddities. Code that works around those may need revising; code that uses <code>locals()</code> for simple templating or print debugging should continue to work correctly.<!-- Debuggers and other tools that use <code>f_locals</code> to modify local variables, will now work correctly, even in the presence of threaded code, coroutines and generators. -->"<ref>{{Cite web |title=PEP 667 – Consistent views of namespaces {{!}} peps.python.org |url=https://peps.python.org/pep-0667/ |access-date=2024-10-07 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref>
 
Python 3.13 introduces the experimental free-threaded build mode, which disables the Global Interpreter Lock (GIL); the GIL is a feature of CPython that previously prevented multiple threads from executing Python bytecode simultaneously. This optional build, introduced through PEP 703, enables better exploitation of multi-core CPUs. By allowing multiple threads to run Python code in parallel, the free-threaded mode addresses long-standing performance bottlenecks associated with the GIL. This change offers a new path for parallelism in Python, without resorting to multiprocessing or external concurrency frameworks.<ref>{{Cite web |title=PEP 703 – Making the GIL Optional in CPython |url=https://peps.python.org/pep-0703/ |access-date=2025-03-30 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref>
 
Regarding annotations in upcoming Python version: <!-- has changes for annotations, and more/PEP 765 <!- "PEP 563 [for Python 3.7 also] changed the semantics of annotations. ->, with PEP 649 "[preserving] nearly all existing behavior of annotations from stock semantics<!- .. This will print <class 'str'> with stock semantics and <class 'int'> when this PEP is active. This is therefore a backwards-incompatible change. However, this example is poor programming style, so this change seems acceptable. ->".<ref>{{Cite web |title=PEP 649 – Deferred Evaluation Of Annotations Using Descriptors {{!}} peps.python.org |url=https://peps.python.org/pep-0649/ |access-date=2024-10-16 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref>


PEP 649 is an "Accepted PEP" and implemented in 3.14:
The name ''Python'' derives from the British comedy series [[Monty Python's Flying Circus]].<ref name=":0">{{Cite book |last1=Briggs |first1=Jason R. |url=https://archive.org/details/pythonforkidspla0000brig |title=Python for kids: a playful introduction to programming |last2=Lipovača |first2=Miran |date=2013 |publisher=No Starch Press |isbn=978-1-59327-407-8 |location=San Francisco, California, USA |lccn=2012044047 |oclc=825076499 |ol=26119645M}}</ref> (See {{section link||Naming}}.)
-->"In Python 3.14, <code>from __future__ import annotations</code> will continue to work as it did before, converting annotations into strings."<!-- I think there's a minor breaking change if this is *omitted*, though I'm not sure omitting it was valid before while using annotations.
 
"Since PEP 649 was written, Python 3.12 and 3.13 gained support for several new features that also use deferred evaluation, similar to the behavior this PEP proposes for annotations:"--><ref>{{Cite web |title=PEP 749 – Implementing PEP 649 {{!}} peps.python.org |url=https://peps.python.org/pep-0749/ |access-date=2024-11-20 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref>
<!--
I.e. I'm not sure this is still valid, needing a warning here:
https://peps.python.org/pep-0649/ "This PEP preserves nearly all existing behavior of annotations from stock semantics: ..


Since delaying the evaluation of annotations until they are introspected changes the semantics of the language, it's observable from within the language. Therefore it's ''possible'' to write code that behaves differently based on whether annotations are evaluated at binding time or at access time"
Python 2.0 was released on 16 October 2000, featuring many new features such as [[list comprehension]]s, [[cycle detection|cycle-detecting]] garbage collection, [[reference counting]], and [[Unicode]] support.<ref name="newin-2.0" /> Python 2.7's [[end-of-life product|end-of-life]] was initially set for 2015, and then postponed to 2020 out of concern that a large body of existing code could not easily be forward-ported to Python&nbsp;3.<ref>{{cite web |last=Peterson |first=Benjamin |title=PEP 373 – Python 2.7 Release Schedule |url=https://legacy.python.org/dev/peps/pep-0373/ |url-status=live |archive-url=https://web.archive.org/web/20200519075520/https://legacy.python.org/dev/peps/pep-0373/ |archive-date=19 May 2020 |access-date=9 January 2017 |work=python.org}}</ref><ref>{{cite web |last=Coghlan |first=Alyssa |title=PEP 466 – Network Security Enhancements for Python 2.7.x |url=https://peps.python.org/pep-0466/ |url-status=live |archive-url=https://web.archive.org/web/20200604232833/https://www.python.org/dev/peps/pep-0466/ |archive-date=4 June 2020 |access-date=9 January 2017 |website=Python Enhancement Proposals (PEPs)}}</ref> It no longer receives security patches or updates.<ref>{{Cite web |title=Sunsetting Python 2 |url=https://www.python.org/doc/sunset-python-2/ |url-status=live |archive-url=https://web.archive.org/web/20200112080903/https://www.python.org/doc/sunset-python-2/ |archive-date=12 January 2020 |access-date=22 September 2019 |website=Python.org |language=en}}</ref><ref>{{Cite web |last=Peterson |first=Benjamin |title=PEP 373 – Python 2.7 Release Schedule |url=https://peps.python.org/pep-0373/ |url-status=live |archive-url=https://web.archive.org/web/20200113033257/https://www.python.org/dev/peps/pep-0373/ |archive-date=13 January 2020 |access-date=22 September 2019 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref> While Python 2.7 and older versions are officially unsupported, a different unofficial Python implementation, [[PyPy]], continues to support Python 2, i.e., "2.7.18+" (plus 3.11<!-- PyPy docs in Nov 2025: "Python 2.7.18 and 3.11.11", not mentioning later 3.11.14 -->), with the plus signifying (at least some) "[[backporting|backported]] security updates".<ref>{{Cite web |last=mattip |date=25 December 2023 |title=PyPy v7.3.14 release |url=https://www.pypy.org/posts/2023/12/pypy-v7314-release.html |url-status=live |archive-url=https://web.archive.org/web/20240105132820/https://www.pypy.org/posts/2023/12/pypy-v7314-release.html |archive-date=5 January 2024 |access-date=5 January 2024 |website=PyPy |language=en}}</ref>
-->


Python 3.14 drops the [[Pretty Good Privacy|PGP]] digital verification signatures, it had deprecated in version 3.11, when its replacement Sigstore was added for all CPython artifacts; the use of PGP has been criticized by security practitioners<!-- "for years now" -->.<ref>{{Cite web |title=PEP 761 – Deprecating PGP signatures for CPython artifacts {{!}} peps.python.org |url=https://peps.python.org/pep-0761/ |access-date=2025-01-06 |website=Python Enhancement Proposals (PEPs) |language=en}}</ref>
Python&nbsp;3.0 was released on 3 December 2008, and was a major revision and not completely [[backward-compatible]] with earlier versions, with some new semantics and changed syntax. Python&nbsp;2.7.18, released in 2020, was the last release of Python&nbsp;2.<ref>{{Cite web |last=Peterson |first=Benjamin |date=20 April 2020 |title=Python 2.7.18, the last release of Python 2 |url=https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html |url-status=live |archive-url=https://web.archive.org/web/20200426204118/https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html |archive-date=26 April 2020 |access-date=27 April 2020 |website=Python Insider}}</ref> Several releases in the Python 3.x series have added new syntax to the language, and made a few (considered very minor) backward-incompatible changes.


Some additional standard-library modules will be removed in Python 3.15 or 3.16, as will be many deprecated classes, functions and methods.<ref>{{Cite web |last=Wouters |first=Thomas |date=2024-04-09 |title=Python Insider: Python 3.12.3 and 3.13.0a6 released |url=https://pythoninsider.blogspot.com/2024/04/python-3123-and-3130a6-released.html |access-date=2024-04-29 |website=Python Insider}}</ref><ref>{{cite web |title=PEP 594 – Removing dead batteries from the standard library |url=https://peps.python.org/pep-0594/ |website=Python Enhancement Proposals |publisher=Python Software Foundation |date=20 May 2019}}</ref>
{{As of|2025|11}}, Python 3.14.0 is the latest stable release, and Python 3.13.9 was released a week later, all older 3.x versions had a security update down to Python 3.9.24 then again with 3.9.25, the final version in 3.9 series. Python 3.10 is, since November 2025, the oldest supported branch.<ref>{{Cite web |title=Status of Python versions |url=https://devguide.python.org/versions/ |access-date=12 November 2025 |website=Python Developer's Guide |language=en}}</ref> Python 3.15 has an alpha released, and Android has a official downloadable executable available for Python 3.14. Releases receive two years of full support followed by three years of security support.


==Design philosophy and features==
==Design philosophy and features==
Python is a [[multi-paradigm programming language]]. Object-oriented programming and structured programming are fully supported, and many of their features support functional programming and [[aspect-oriented programming]] (including [[metaprogramming]]<ref name="AutoNT-13"/> and [[metaobject]]s).<ref name="AutoNT-14"/> Many other paradigms are supported via extensions, including [[design by contract]]<ref name="AutoNT-15"/><ref name="AutoNT-16"/> and [[logic programming]].<ref name="AutoNT-17"/> Python is often referred to as a ''[[glue language|<nowiki/>'glue language]]'''<ref>{{Cite web |title=Glue It All Together With Python |url=https://www.python.org/doc/essays/omg-darpa-mcc-position/ |access-date=2024-09-30 |website=Python.org |language=en}}</ref> because it can seamlessly integrate components written in other languages.
Python is a [[multi-paradigm programming language]]. Object-oriented programming and structured programming are fully supported, and many of their features support functional programming and [[aspect-oriented programming]] including [[metaprogramming]]<ref name=AutoNT-13/> and [[metaobject]]s.<ref name=AutoNT-14/> Many other paradigms are supported via extensions, including [[design by contract]]<ref name=AutoNT-15/><ref name=AutoNT-16/> and [[logic programming]].<ref name=AutoNT-17/> Python is often referred to as a ''[[glue language|<nowiki/>'glue language']]''<ref>{{cite web |title=Glue it all together with Python |url=https://www.python.org/doc/essays/omg-darpa-mcc-position/ |access-date=2024-09-30 |website=Python.org |language=en}}</ref> because it is purposely designed to be able to integrate components written in other languages.


Python uses dynamic typing and a combination of [[reference counting]] and a cycle-detecting garbage collector for [[memory management]].<ref name="Reference_counting">{{Cite web |url=https://docs.python.org/extending/extending.html#reference-counts |title=Extending and Embedding the Python Interpreter: Reference Counts |publisher=Docs.python.org |language=en |access-date=5 June 2020 |quote=Since Python makes heavy use of <code>malloc()</code> and <code>free()</code>, it needs a strategy to avoid memory leaks as well as the use of freed memory. The chosen method is called ''reference counting''. |archive-date=18 October 2012 |archive-url=https://web.archive.org/web/20121018063230/http://docs.python.org/extending/extending.html#reference-counts |url-status=live}}</ref> It uses dynamic [[Name resolution (programming languages)|name resolution]] ([[late binding]]), which binds method and variable names during program execution.
Python uses dynamic typing and a combination of [[reference counting]] and a cycle-detecting garbage collector for [[memory management]].<ref name=Reference_counting>{{cite web |title=Reference counts |department=Extending and embedding the Python interpreter |website=Docs.python.org |language=en |url=https://docs.python.org/extending/extending.html#reference-counts |url-status=live |access-date=5 June 2020 |quote=Since Python makes heavy use of <code>malloc()</code> and <code>free()}</code>, it needs a strategy to avoid memory leaks as well as the re‑use of freed memory. The method chosen is called ''reference counting''. |archive-url=https://web.archive.org/web/20121018063230/http://docs.python.org/extending/extending.html#reference-counts |archive-date=18 October 2012 }}</ref> It uses dynamic [[Name resolution (programming languages)|name resolution]] ([[late binding]]), which binds method and variable names during program execution.


Python's design offers some support for functional programming in the [[Lisp (programming language)|Lisp]] tradition. It has {{codes|filter|map|reduce|d=and}} functions; [[list comprehension]]s, [[Associative array|dictionaries]], sets, and [[generator (computer programming)|generator]] expressions.<ref name="AutoNT-59"/> The standard library has two modules ({{codes|itertools}} and {{codes|functools}}) that implement functional tools borrowed from [[Haskell]] and [[Standard ML]].<ref name="AutoNT-18"/>
Python's design offers some support for functional programming in the "[[Lisp (programming language)|Lisp]] tradition". It has {{code|filter}}, {{code|map}}, and {{code|reduce}} functions; [[list comprehension]]s, [[associative array|dictionaries]], [[set (mathematics)|sets]], and [[generator (computer programming)|generator]] expressions.<ref name=AutoNT-59/> The standard library has two modules ({{codes|itertools}} and {{codes|functools}}) that implement functional tools borrowed from [[Haskell]] and [[Standard ML]].<ref name=AutoNT-18/>


Python's core philosophy is summarized in the [[Zen of Python]] (PEP 20), which includes aphorisms such as these:<ref name="PEP20"/>
Python's core philosophy is summarized in the [[Zen of Python]] (PEP 20) written by [[Tim Peters (software engineer)|Tim Peters]], which includes aphorisms such as these:<ref name=PEP20/>
<!-- Note this isn't a full list, just some of the more significant aphorisms -->
* Beautiful is better than ugly.
* Explicit is better than implicit.
* Explicit is better than implicit.
* Simple is better than complex.
* Simple is better than complex.
* Complex is better than complicated.
* Readability counts.
* Readability counts.
* Special cases aren't special enough to break the rules.
* Although practicality beats purity.
* Errors should never pass silently.
* Unless explicitly silenced.
* There should be one-- and preferably only one --obvious way to do it.
<!-- Note this isn't a full list, just some of the more significant aphorisms -->


However, Python features regularly violate these principles and have received criticism for adding unnecessary language bloat.<ref name="Python-Changes-2014">{{cite web |url=https://learning-python.com/python-changes-2014-plus.html |title=Python Changes 2014+ |last=Lutz |first=Mark |date=January 2022 |website=Learning Python |access-date=2024-02-25 |archive-date=15 March 2024 |archive-url=https://web.archive.org/web/20240315075935/https://learning-python.com/python-changes-2014-plus.html |url-status=live}}</ref> Responses to these criticisms note that the Zen of Python is a guideline rather than a rule.<ref name="Confusion-regarding-a-rule-in-the-Zen-of-Python">{{cite web |url=https://discuss.python.org/t/confusion-regarding-a-rule-in-the-zen-of-python/15927 |title=Confusion regarding a rule in The Zen of Python |author=<!--Not stated--> |date=2022-05-03 |website=Python Help - Discussions on Python.org |access-date=2024-02-25 |archive-date=25 February 2024 |archive-url=https://web.archive.org/web/20240225221142/https://discuss.python.org/t/confusion-regarding-a-rule-in-the-zen-of-python/15927 |url-status=live}}</ref> The addition of some new features had been controversial: Guido van Rossum resigned as Benevolent Dictator for Life after conflict about adding the assignment expression operator in Python 3.8.<ref name="The-Most-Controversial-Python-Walrus-Operator">{{cite web |url=https://pythonsimplified.com/the-most-controversial-python-walrus-operator/ |title=The Most Controversial Python Walrus Operator |last=Ambi |first=Chetan |date=2021-07-04 |website=Python Simplified |access-date=2024-02-05 |archive-date=27 August 2023 |archive-url=https://web.archive.org/web/20230827154931/https://pythonsimplified.com/the-most-controversial-python-walrus-operator/ |url-status=live}}</ref><ref name="The-Controversy-Behind-The-Walrus-Operator-in-Python">{{cite web |url=https://therenegadecoder.com/code/the-controversy-behind-the-walrus-operator-in-python/ |title=The Controversy Behind The Walrus Operator in Python |last=Grifski |first=Jeremy |date=2020-05-24 |website=The Renegade Coder |access-date=2024-02-25 |archive-date=28 December 2023 |archive-url=https://web.archive.org/web/20231228135749/https://therenegadecoder.com/code/the-controversy-behind-the-walrus-operator-in-python/ |url-status=live}}</ref>
However, Python has received criticism for violating these principles and adding unnecessary language bloat.<ref name=Python-Changes-2014>{{cite web |last=Lutz |first=Mark |date=January 2022 |website=Learning Python |title=Python changes 2014+ |url=https://learning-python.com/python-changes-2014-plus.html |url-status=live |access-date=25 February 2024 |archive-url=https://web.archive.org/web/20240315075935/https://learning-python.com/python-changes-2014-plus.html |archive-date=15 March 2024 }}</ref> Responses to these criticisms note that the Zen of Python is a guideline rather than a rule.<ref name=Confusion-regarding-a-rule-in-the-Zen-of-Python>{{cite web |url=https://discuss.python.org/t/confusion-regarding-a-rule-in-the-zen-of-python/15927 |title=Confusion regarding a rule in 'the Zen of Python' |date=2022-05-03 |department=Discussions |series=Python help |website=Python.org |access-date=2024-02-25 |archive-date=25 February 2024 |archive-url=https://web.archive.org/web/20240225221142/https://discuss.python.org/t/confusion-regarding-a-rule-in-the-zen-of-python/15927 |url-status=live}}</ref> The addition of some new features had been controversial: Guido van Rossum resigned as ''Benevolent Dictator for Life'' after conflict about adding the assignment expression operator in {{nobr|Python 3.8&thinsp;.}}<ref name=The-Most-Controversial-Python-Walrus-Operator>{{cite web |last=Ambi |first=Chetan |date=2021-07-04 |title=The most controversial Python 'walrus operator' |website=Python simplified (pythonsimplified.com) |url=https://pythonsimplified.com/the-most-controversial-python-walrus-operator/ |url-status=live |access-date=2024-02-05 |archive-url=https://web.archive.org/web/20230827154931/https://pythonsimplified.com/the-most-controversial-python-walrus-operator/ |archive-date=27 August 2023 }}</ref><ref name=The-Controversy-Behind-The-Walrus-Operator-in-Python>{{cite web |last=Grifski |first=Jeremy |date=2020-05-24 |title=The controversy behind the 'walrus operator' in Python |website=The Renegade Coder (therenegadecoder.com) |url=https://therenegadecoder.com/code/the-controversy-behind-the-walrus-operator-in-python/ |url-status=live |access-date=2024-02-25 |archive-url=https://web.archive.org/web/20231228135749/https://therenegadecoder.com/code/the-controversy-behind-the-walrus-operator-in-python/ |archive-date=28 December 2023 }}</ref>


Nevertheless, rather than building all functionality into its core, Python was designed to be highly [[extensible]] via modules. This compact modularity has made it particularly popular as a means of adding programmable interfaces to existing applications. Van Rossum's vision of a small core language with a large standard library and easily extensible interpreter stemmed from his frustrations with ABC, which represented the opposite approach.<ref name="venners-interview-pt-1"/>
Nevertheless, rather than building all functionality into its core, Python was designed to be highly [[extensible]] via modules. This compact modularity has made it particularly popular as a means of adding programmable interfaces to existing applications. Van Rossum's vision of a small core language with a large standard library and easily extensible interpreter stemmed from his frustrations with ABC, which represented the opposite approach.<ref name=venners-interview-pt-1/>


Python claims to strive for a simpler, less-cluttered syntax and grammar, while giving developers a choice in their coding methodology. In contrast to [[Perl]]'s motto "[[there is more than one way to do it]]", Python advocates an approach where "there should be one—and preferably only one—obvious way to do it."<!-- the "—" spacing here, although inconsistent with Wikipedia MOS, is quoted text and must be maintained as is; do not "correct" it -->.<ref name="PEP20"/> In practice, however, Python provides many ways to achieve a given goal. There are, for example, at least three ways to format a string literal, with no certainty as to which one a programmer should use.<ref name="Python-String-Formatting-Best-Practices">{{cite web |url=https://realpython.com/python-string-formatting/ |title=Python String Formatting Best Practices |last=Bader |first=Dan |website=Real Python |access-date=2024-02-25 |archive-date=18 February 2024 |archive-url=https://web.archive.org/web/20240218083506/https://realpython.com/python-string-formatting/ |url-status=live}}</ref> [[Alex Martelli]] is a [[Fellow]] at the [[Python Software Foundation]] and Python book author; he wrote that "To describe something as 'clever' is ''not'' considered a compliment in the Python culture."<ref name="AutoNT-19"/>
Python claims to strive for a simpler, less-cluttered syntax and grammar, while giving developers a choice in their coding methodology. Python lacks do while loops, which [[Guido Van Rossum|Rossum]] considered harmful.<ref>{{cite web|url=https://mail.python.org/pipermail/python-ideas/2013-June/021610.html|title=[Python-ideas] PEP 315: do-while |date=26 June 2013 }}</ref> In contrast to [[Perl]]'s motto "[[there is more than one way to do it]]", Python advocates an approach where "there should be one – and preferably only one – obvious way to do it".<!-- removed comment with specious demand to leave punctuation contrary to Wikipedia MOS unchanged: Reason given, to duplicate lack of spaces in quote, is a grotesquely false justification. --><ref name=PEP20/> In practice, however, Python provides many ways to achieve a given goal. There are at least three ways to format a string literal, with no certainty as to which one a programmer should use.<ref name=Python-String-Formatting-Best-Practices>{{cite web |last=Bader |first=Dan |title=Python string formatting best practices |website=Real Python (realpython.com) |url=https://realpython.com/python-string-formatting/ |url-status=live |access-date=2024-02-25 |archive-url=https://web.archive.org/web/20240218083506/https://realpython.com/python-string-formatting/ |archive-date=18 February 2024 }}</ref> [[Alex Martelli]] is a [[Fellow]] at the [[Python Software Foundation]] and Python book author; he wrote that "To describe something as 'clever' is ''not'' considered a compliment in the Python culture."<ref name=AutoNT-19/>


Python's developers usually try to avoid [[premature optimization]]; they also reject patches to non-critical parts of the [[CPython]] reference implementation that would offer marginal increases in speed at the cost of clarity.<ref name="AutoNT-20"/> Execution speed can be improved by moving speed-critical functions to extension modules written in languages such as C, or by using a [[just-in-time compiler]] like [[PyPy]]. It is also possible to [[#Cross-compilers to other languages|cross-compile to other languages]]; but this approach either fails to achieve the expected speed-up, since Python is a very [[dynamic language]], or only a restricted subset of Python is compiled (with potential minor semantic changes).<ref name=PyJL/>
Python's developers typically prioritise readability over performance. For example, they reject patches to non-critical parts of the [[CPython]] reference implementation that would offer increases in speed that do not justify the cost of clarity and readability.<ref name="AutoNT-20"/>{{Failed verification|date=August 2025|reason=The referenced source did not mention that information. A better source should be found.}} Execution speed can be improved by moving speed-critical functions to extension modules written in languages such as [[C (programming language)|C]], or by using a [[just-in-time compiler]] like [[PyPy]]. Also, it is possible to transpile to other languages. However, this approach either fails to achieve the expected speed-up, since Python is a very [[dynamic language]], or only a restricted subset of Python is compiled (with potential minor semantic changes).<ref name=PyJL/>


Python's developers aim for the language to be fun to use. This goal is reflected in the name—a tribute to the British comedy group [[Monty Python]]<ref name="whyname"/>—and in playful approaches to some tutorials and reference materials. For instance, some code examples use the terms "spam" and "eggs" (in reference to [[Spam (Monty Python)|a Monty Python sketch]]), rather than the typical terms [[foobar|"foo" and "bar"]].<ref>{{Cite web|url=https://insidetech.monster.com/training/articles/8114-15-ways-python-is-a-powerful-force-on-the-web|title=15 Ways Python Is a Powerful Force on the Web|access-date=3 July 2018|archive-date=11 May 2019|archive-url=https://web.archive.org/web/20190511065650/http://insidetech.monster.com/training/articles/8114-15-ways-python-is-a-powerful-force-on-the-web|url-status=dead}}</ref><ref>{{Cite web |title=pprint – Data pretty printer – Python 3.11.0 documentation |url=https://docs.python.org/3/library/pprint.html |access-date=2022-11-05 |website=docs.python.org |quote=stuff=['spam', 'eggs', 'lumberjack', 'knights', 'ni'] |archive-date=22 January 2021 |archive-url=https://web.archive.org/web/20210122224848/https://docs.python.org/3/library/pprint.html |url-status=live}}</ref> A common [[neologism]] in the Python community is ''pythonic'', which has a wide range of meanings related to program style. Pythonic code may use Python [[Programming idiom|idioms]] well; be natural or show fluency in the language; or conform with Python's minimalist philosophy and emphasis on readability.<ref>{{Cite web|url=https://docs.python-guide.org/writing/style|title=Code Style – The Hitchhiker's Guide to Python|website=docs.python-guide.org|access-date=20 January 2021|archive-date=27 January 2021|archive-url=https://web.archive.org/web/20210127154341/https://docs.python-guide.org/writing/style/|url-status=live}}</ref>
Python is meant to be a fun language to use. This goal is reflected in the name – a tribute to the British comedy group [[Monty Python]]<ref name=whyname/> – and in playful approaches to some tutorials and reference materials. For instance, some code examples use the terms "spam" and "eggs" (in reference to [[Spam (Monty Python)|a Monty Python sketch]]), rather than the typical terms [[foobar|"foo" and "bar"]].<ref>{{cite web |title=15&nbsp;ways Python is a powerful force on the web |url=https://insidetech.monster.com/training/articles/8114-15-ways-python-is-a-powerful-force-on-the-web |access-date=3 July 2018 |archive-url=https://web.archive.org/web/20190511065650/http://insidetech.monster.com/training/articles/8114-15-ways-python-is-a-powerful-force-on-the-web |archive-date=11 May 2019 }}</ref><ref name=pprint-doc>{{cite web |title=<code>pprint</code> data pretty printer – {{nobr|Python 3.11.0}} documentation |website=docs.python.org |quote=<code>stuff {{=}} ['spam', 'eggs', 'lumberjack', 'knights', 'ni']</code> |url=https://docs.python.org/3/library/pprint.html |url-status=live |access-date=2022-11-05 |archive-url=https://web.archive.org/web/20210122224848/https://docs.python.org/3/library/pprint.html |archive-date=22 January 2021 }}</ref>
 
A common [[neologism]] in the Python community is ''pythonic'', which has a broad range of meanings related to program style: Pythonic code may use Python [[Programming idiom|idioms]] well; be natural or show fluency in the language; or conform with Python's minimalist philosophy and emphasis on readability.<ref>{{cite web |title=Code style |department=The hitchhiker's guide to Python |website=docs.python-guide.org |url=https://docs.python-guide.org/writing/style |url-status=live |access-date=20 January 2021 |archive-url=https://web.archive.org/web/20210127154341/https://docs.python-guide.org/writing/style/ |archive-date=27 January 2021 }}</ref>


==Syntax and semantics==
==Syntax and semantics==
{{Main|Python syntax and semantics}}
{{Main|Python syntax and semantics}}
[[File:Hello World in Python.png|alt=Block of Python code showing sample source code|thumb|231x231px|An example of Python code and indentation]]
[[File:Af-Helloworld (C Sharp).svg|alt=C code featuring curly braces and semicolon|thumb|233x233px|Example of [[C Sharp (programming language)|C#]] code with curly braces and semicolons]]
Python is meant to be an easily readable language. Its formatting is visually uncluttered and often uses English keywords where other languages use punctuation. Unlike many other languages, it does not use [[curly bracket programming language|curly brackets]] to delimit blocks, and semicolons after statements are allowed but rarely used. It has fewer syntactic exceptions and special cases than [[C (programming language)|C]] or [[Pascal (programming language)|Pascal]].<ref name="AutoNT-52"/>
Python is meant to be an easily readable language. Its formatting is visually uncluttered and often uses English keywords where other languages use punctuation. Unlike many other languages, it does not use [[curly bracket programming language|curly brackets]] to delimit blocks, and semicolons after statements are allowed but rarely used. It has fewer syntactic exceptions and special cases than [[C (programming language)|C]] or [[Pascal (programming language)|Pascal]].<ref name="AutoNT-52"/>


===Indentation===
===Indentation===
{{Main|Python syntax and semantics#Indentation}}
{{Further|Python syntax and semantics#Indentation}}


Python uses [[whitespace character|whitespace]] indentation, rather than curly brackets or keywords, to delimit [[block (programming)|blocks]]. An increase in indentation comes after certain statements; a decrease in indentation signifies the end of the current block.<ref name="AutoNT-53"/> Thus, the program's visual structure accurately represents its semantic structure.<ref name=guttag>{{Cite book |publisher=MIT Press |isbn=978-0-262-52962-4 |last=Guttag |first=John V. |title=Introduction to Computation and Programming Using Python: With Application to Understanding Data |date=12 August 2016}}</ref> This feature is sometimes termed the [[off-side rule]]. Some other languages use indentation this way; but in most, indentation has no semantic meaning. The recommended indent size is four spaces.<ref>{{Cite web|url=https://www.python.org/dev/peps/pep-0008/|title=PEP 8 – Style Guide for Python Code|website=Python.org|access-date=26 March 2019|archive-date=17 April 2019|archive-url=https://web.archive.org/web/20190417223549/https://www.python.org/dev/peps/pep-0008/|url-status=live}}</ref>
Python uses [[whitespace character|whitespace]] indentation, rather than curly brackets or keywords, to delimit [[block (programming)|blocks]]. An increase in indentation comes after certain statements; a decrease in indentation signifies the end of the current block.<ref name="AutoNT-53"/> Thus, the program's visual structure accurately represents its semantic structure.<ref name=guttag>{{Cite book |publisher=MIT Press |isbn=978-0-262-52962-4 |last=Guttag |first=John V. |title=Introduction to Computation and Programming Using Python: With Application to Understanding Data |date=12 August 2016}}</ref> This feature is sometimes termed the [[off-side rule]]. Some other languages use indentation this way; but in most, indentation has no semantic meaning. The recommended indent size is four spaces.<ref name="pep8">{{Cite web |first1=Guido  |last1= van Rossum |first2= Barry |last2=Warsaw |url=https://www.python.org/dev/peps/pep-0008/|title=PEP 8 – Style Guide for Python Code|website=Python Enhancement Proposals (PEPs)|access-date=26 March 2019|archive-date=17 April 2019|archive-url=https://web.archive.org/web/20190417223549/https://www.python.org/dev/peps/pep-0008/|url-status=live}}</ref>


===Statements and control flow===
===Statements and control flow===
Python's [[statement (computer science)|statements]] include the following:
Python's [[statement (computer science)|statements]] include the following:
* The [[Assignment (computer science)|assignment]] statement, using a single equals sign <code>=</code>
* The [[Assignment (computer science)|assignment]] statement, using a single equals sign <code>=</code>
* The <code>[[if-then-else|if]]</code> statement, which conditionally executes a block of code, along with <code>else</code> and <code>elif</code> (a contraction of <code>else if</code>)
* The <code>[[if-then-else|if]]</code> statement, which conditionally executes a block of code, along with <code>[[Conditional (computer programming)#If–then(–else)|else]]</code> and <code>elif</code> (a contraction of <code>[[Conditional (computer programming)#Else if|else if]]</code>)
* The <code>[[Foreach#Python|for]]</code> statement, which iterates over an ''iterable'' object, capturing each element to a local variable for use by the attached block
* The <code>[[Foreach#Python|for]]</code> statement, which iterates over an ''iterable'' object, capturing each element to a variable for use by the attached block; the variable is not deleted when the loop finishes
* The <code>[[While loop#Python|while]]</code> statement, which executes a block of code as long as boolean condition is true
* The <code>[[While loop#Python|while]]</code> statement, which executes a block of code as long as boolean condition is true
* The <code>[[Exception handling syntax#Python|try]]</code> statement, which allows exceptions raised in its attached code block to be caught and handled by <code>except</code> clauses (or new syntax <code>except*</code> in Python 3.11 for exception groups<ref>{{Cite web |title=8. Errors and Exceptions – Python 3.12.0a0 documentation |url=https://docs.python.org/3.11/tutorial/errors.html |access-date=2022-05-09 |website=docs.python.org |archive-date=9 May 2022 |archive-url=https://web.archive.org/web/20220509145745/https://docs.python.org/3.11/tutorial/errors.html |url-status=live}}</ref>); the <code>try</code> statement also ensures that clean-up code in a <code>finally</code> block is always run regardless of how the block exits
* The <code>[[Exception handling syntax#Python|try]]</code> statement, which allows exceptions raised in its attached code block to be caught and handled by <code>except</code> clauses (or new syntax <code>except*</code> in Python 3.11 for exception groups);<ref>{{Cite web |title=8. Errors and Exceptions – Python 3.12.0a0 documentation |url=https://docs.python.org/3.11/tutorial/errors.html |access-date=2022-05-09 |website=docs.python.org |archive-date=9 May 2022 |archive-url=https://web.archive.org/web/20220509145745/https://docs.python.org/3.11/tutorial/errors.html |url-status=live}}</ref> the <code>try</code> statement also ensures that clean-up code in a <code>finally</code> block is always run regardless of how the block exits
* The <code>raise</code> statement, used to raise a specified exception or re-raise a caught exception
* The <code>raise</code> statement, used to raise a specified exception or re-raise a caught exception
* The <code>class</code> statement, which executes a block of code and attaches its local namespace to a [[class (computer science)|class]], for use in object-oriented programming
* The <code>class</code> statement, which executes a block of code and attaches its local namespace to a [[class (computer science)|class]], for use in object-oriented programming
Line 211: Line 142:
* Python uses the <code>+</code> operator for string concatenation. The language uses the <code>*</code> operator for duplicating a string a specified number of times.
* Python uses the <code>+</code> operator for string concatenation. The language uses the <code>*</code> operator for duplicating a string a specified number of times.
* The <code>@</code> infix operator<!-- was introduced in Python 3.5--> is intended to be used by libraries such as [[NumPy]] for [[matrix multiplication]].<ref name=PEP465>{{cite web |title=PEP 0465 – A dedicated infix operator for matrix multiplication |url=https://www.python.org/dev/peps/pep-0465/ |website=python.org |access-date=1 January 2016 |archive-date=4 June 2020 |archive-url=https://web.archive.org/web/20200604224255/https://www.python.org/dev/peps/pep-0465/ |url-status=live}}</ref><ref name=Python3.5Changelog>{{cite web |title=Python 3.5.1 Release and Changelog |url=https://www.python.org/downloads/release/python-351/ |website=python.org |access-date=1 January 2016 |archive-date=14 May 2020 |archive-url=https://web.archive.org/web/20200514034938/https://www.python.org/downloads/release/python-351/ |url-status=live}}</ref>
* The <code>@</code> infix operator<!-- was introduced in Python 3.5--> is intended to be used by libraries such as [[NumPy]] for [[matrix multiplication]].<ref name=PEP465>{{cite web |title=PEP 0465 – A dedicated infix operator for matrix multiplication |url=https://www.python.org/dev/peps/pep-0465/ |website=python.org |access-date=1 January 2016 |archive-date=4 June 2020 |archive-url=https://web.archive.org/web/20200604224255/https://www.python.org/dev/peps/pep-0465/ |url-status=live}}</ref><ref name=Python3.5Changelog>{{cite web |title=Python 3.5.1 Release and Changelog |url=https://www.python.org/downloads/release/python-351/ |website=python.org |access-date=1 January 2016 |archive-date=14 May 2020 |archive-url=https://web.archive.org/web/20200514034938/https://www.python.org/downloads/release/python-351/ |url-status=live}}</ref>
* The syntax <code>:=</code>, called the "walrus operator", was introduced in Python 3.8. This operator assigns values to variables as part of a larger expression.<ref name=Python3.8Changelog>{{cite web |title=What's New in Python 3.8 |url=https://docs.python.org/3.8/whatsnew/3.8.html |access-date=14 October 2019 |archive-date=8 June 2020 |archive-url=https://web.archive.org/web/20200608124345/https://docs.python.org/3.8/whatsnew/3.8.html |url-status=live}}</ref>
* The syntax <code>:=</code>, called the "{{va|walrus operator}}", was introduced in Python 3.8. This operator assigns values to variables as part of a larger expression.<ref name=Python3.8Changelog>{{cite web |title=What's New in Python 3.8 |url=https://docs.python.org/3.8/whatsnew/3.8.html |access-date=14 October 2019 |archive-date=8 June 2020 |archive-url=https://web.archive.org/web/20200608124345/https://docs.python.org/3.8/whatsnew/3.8.html |url-status=live}}</ref>
* In Python, <code>==</code> compares two objects by value. Python's <code>is</code> operator may be used to compare object identities (i.e., comparison by reference), and comparisons may be chained—for example, {{code|lang=python|code=a <= b <= c}}.
* In Python, <code>==</code> compares two objects by value. Python's <code>is</code> operator may be used to compare object identities (i.e., comparison by reference), and comparisons may be chained—for example, {{code|lang=python|code=a <= b <= c}}.
* Python uses <code>and</code>, <code>or</code>, and <code>not</code> as Boolean operators.
* Python uses <code>and</code>, <code>or</code>, and <code>not</code> as Boolean operators.
Line 233: Line 164:


A statement cannot be part of an expression; because of this restriction, expressions such as list and <code>dict</code> comprehensions (and lambda expressions) cannot contain statements. As a particular case, an assignment statement such as {{code|lang=python|code=a = 1}} cannot be part of the conditional expression of a conditional statement.
A statement cannot be part of an expression; because of this restriction, expressions such as list and <code>dict</code> comprehensions (and lambda expressions) cannot contain statements. As a particular case, an assignment statement such as {{code|lang=python|code=a = 1}} cannot be part of the conditional expression of a conditional statement.
===Methods===
[[Method (computer programming)|Methods]] of objects are functions attached to the object's class; the syntax for normal methods and functions, {{code|lang=python|code=instance.method(argument)}}, is [[syntactic sugar]] for {{code|lang=python|code=Class.method(instance, argument)}}. Python methods have an explicit <code>[[this (computer programming)|self]]</code> parameter to access [[instance data]], in contrast to the implicit self (or <code>this</code>) parameter in some object-oriented programming languages (e.g., [[C++]], [[Java (programming language)|Java]], [[Objective-C]], [[Ruby (programming language)|Ruby]]).<ref name="AutoNT-61"/> Python also provides methods, often called ''dunder methods'' (because their names begin and end with double underscores); these methods allow user-defined classes to modify how they are handled by native operations including length, comparison, [[arithmetic operations|arithmetic]], and type conversion.<ref>{{cite book |last1=Sweigart |first1=Al |title=Beyond the Basic Stuff with Python: Best Practices for Writing Clean Code |year=2020 |publisher=No Starch Press |isbn=978-1-59327-966-0 |page=322 |url=https://books.google.com/books?id=7GUKEAAAQBAJ&pg=PA322 |language=en |access-date=7 July 2021 |archive-date=13 August 2021 |archive-url=https://web.archive.org/web/20210813194312/https://books.google.com/books?id=7GUKEAAAQBAJ&pg=PA322 |url-status=live}}</ref>


===Typing===
===Typing===
Line 245: Line 173:
Before version 3.0, Python had two kinds of classes, both using the same syntax: ''old-style'' and ''new-style''.<ref name="classy"/> Current Python versions support the semantics of only the new style.
Before version 3.0, Python had two kinds of classes, both using the same syntax: ''old-style'' and ''new-style''.<ref name="classy"/> Current Python versions support the semantics of only the new style.


Python supports [[optional typing|optional type annotations]].<ref name="type_hint-PEP"/><ref>{{Cite web |title=PEP 484 – Type Hints {{!}} peps.python.org |url=https://peps.python.org/pep-0484/ |access-date=2023-11-29 |website=peps.python.org |archive-date=27 November 2023 |archive-url=https://web.archive.org/web/20231127205023/https://peps.python.org/pep-0484/ |url-status=live}}</ref> These annotations are not enforced by the language, but may be used by external tools such as '''mypy''' to catch errors.<ref>{{cite web |title=typing — Support for type hints |url=https://docs.python.org/3/library/typing.html |website=Python documentation |publisher=Python Software Foundation |access-date=22 December 2023 |archive-date=21 February 2020 |archive-url=https://web.archive.org/web/20200221184042/https://docs.python.org/3/library/typing.html |url-status=live}}</ref><ref>{{cite web |url=http://mypy-lang.org/ |title=mypy – Optional Static Typing for Python |access-date=28 January 2017 |archive-date=6 June 2020 |archive-url=https://web.archive.org/web/20200606192012/http://mypy-lang.org/ |url-status=live}}</ref> Mypy also supports a Python compiler called mypyc, which leverages type annotations for optimization.<ref>{{cite web |title=Introduction |url=https://mypyc.readthedocs.io/en/latest/introduction.html |website=mypyc.readthedocs.io |access-date=22 December 2023 |archive-date=22 December 2023 |archive-url=https://web.archive.org/web/20231222000457/https://mypyc.readthedocs.io/en/latest/introduction.html |url-status=live}}</ref>
Python supports [[optional typing|optional type annotations]].<ref name="type_hint-PEP"/><ref>{{Cite web |title=PEP 484 – Type Hints {{!}} peps.python.org |url=https://peps.python.org/pep-0484/ |access-date=2023-11-29 |website=peps.python.org |archive-date=27 November 2023 |archive-url=https://web.archive.org/web/20231127205023/https://peps.python.org/pep-0484/ |url-status=live}}</ref> These annotations are not enforced by the language, but may be used by external tools such as '''mypy''' to catch errors. Python includes a module <code>typing</code> including several type names for type annotations.<ref>{{cite web |title=typing — Support for type hints |url=https://docs.python.org/3/library/typing.html |website=Python documentation |publisher=Python Software Foundation |access-date=22 December 2023 |archive-date=21 February 2020 |archive-url=https://web.archive.org/web/20200221184042/https://docs.python.org/3/library/typing.html |url-status=live}}</ref><ref>{{cite web |url=http://mypy-lang.org/ |title=mypy – Optional Static Typing for Python |access-date=28 January 2017 |archive-date=6 June 2020 |archive-url=https://web.archive.org/web/20200606192012/http://mypy-lang.org/ |url-status=live}}</ref> Also, Mypy supports a Python compiler called mypyc, which leverages type annotations for optimization.<ref>{{cite web |title=Introduction |url=https://mypyc.readthedocs.io/en/latest/introduction.html |website=mypyc.readthedocs.io |access-date=22 December 2023 |archive-date=22 December 2023 |archive-url=https://web.archive.org/web/20231222000457/https://mypyc.readthedocs.io/en/latest/introduction.html |url-status=live}}</ref>


{|class="wikitable"
{|class="wikitable"
Line 273: Line 201:
| immutable
| immutable
| [[Complex number]] with real and imaginary parts
| [[Complex number]] with real and imaginary parts
| {{code|lang=python|3+2.7j}}<br />{{code|lang=python|3 + 2.7j}}
| {{code|lang=python|3+2.7j}}<br />{{code|lang=python|3 + 2.7j}}<br />{{code|lang=python|5j}}
|-
|-
| <code>dict</code>
| <code>dict</code>
Line 303: Line 231:
| immutable
| immutable
| Unordered [[set (computer science)|set]], contains no duplicates; can contain mixed types, if hashable
| Unordered [[set (computer science)|set]], contains no duplicates; can contain mixed types, if hashable
| {{nobr|{{code|lang=python|frozenset([4.0, 'string', True])}}}}
| {{code|lang=python|frozenset({4.0, 'string', True})}}
{{code|lang=python|frozenset()}}
|-
|-
| <code>int</code>
| <code>int</code>
Line 340: Line 269:
| {{code|lang=python|'Wikipedia'}}<br />{{code|lang=python|"Wikipedia"}}<syntaxhighlight lang="python">"""Spanning
| {{code|lang=python|'Wikipedia'}}<br />{{code|lang=python|"Wikipedia"}}<syntaxhighlight lang="python">"""Spanning
multiple
multiple
lines"""</syntaxhighlight><syntaxhighlight lang="python">
lines"""</syntaxhighlight>
Spanning
multiple
lines
</syntaxhighlight>
|-
|-
| <code>tuple</code>
| <code>tuple</code>
Line 353: Line 278:


===Arithmetic operations===
===Arithmetic operations===
Python includes conventional symbols for arithmetic operators (<code>+</code>, <code>-</code>, <code>*</code>, <code>/</code>), the floor-division operator <code>//</code>, and the [[modulo operation|modulo operator]] <code>%</code>. (With the module operator, a remainder can be negative,<!--unlike in C language depending on compiler,<ref>{{Cite web|url=https://stackoverflow.com/questions/11720656/modulo-operation-with-negative-numbers/42131603|title=c – Modulo operation with negative numbers|quote=Note that, in C89, whether the result round upward or downward is implementation-defined.|website=Stack Overflow|access-date=25 September 2019}}</ref>--> e.g., <code>4 % -3 == -2</code>.) Python also offers the <code>**</code> symbol for [[exponentiation]], e.g. <code>5**3 == 125</code> and <code>9**0.5 == 3.0</code>; it also offers the matrix‑multiplication operator <code>@</code> .<ref>{{cite web |url=https://legacy.python.org/dev/peps/pep-0465/ |title=PEP 465 – A dedicated infix operator for matrix multiplication |work=python.org |access-date=3 July 2018 |archive-date=29 May 2020 |archive-url=https://web.archive.org/web/20200529200310/https://legacy.python.org/dev/peps/pep-0465/ |url-status=live}}</ref> These operators work as in traditional mathematics; with the same [[order of operations|precedence rules]], the [[infix notation|infix]] operators <code>+</code> and <code>-</code> can also be [[unary operation|unary]], to represent positive and negative numbers respectively.
Python includes conventional symbols for arithmetic operators (<code>+</code>, <code>-</code>, <code>*</code>, <code>/</code>), the floor-division operator <code>//</code>, and the [[modulo operation|modulo operator]] <code>%</code>. (With the modulo operator, a remainder can be negative,<!--unlike in C language depending on compiler,<ref>{{Cite web|url=https://stackoverflow.com/questions/11720656/modulo-operation-with-negative-numbers/42131603|title=c – Modulo operation with negative numbers|quote=Note that, in C89, whether the result round upward or downward is implementation-defined.|website=Stack Overflow|access-date=25 September 2019}}</ref>--> e.g., <code>4 % -3 == -2</code>.) Also, Python offers the <code>**</code> symbol for [[exponentiation]], e.g. <code>5**3 == 125</code> and <code>9**0.5 == 3.0</code>. Also, it offers the matrix‑multiplication operator <code>@</code> .<ref>{{cite web |url=https://legacy.python.org/dev/peps/pep-0465/ |title=PEP 465 – A dedicated infix operator for matrix multiplication |work=python.org |access-date=3 July 2018 |archive-date=29 May 2020 |archive-url=https://web.archive.org/web/20200529200310/https://legacy.python.org/dev/peps/pep-0465/ |url-status=live}}</ref> These operators work as in traditional mathematics; with the same [[order of operations|precedence rules]], the [[infix notation|infix]] operators <code>+</code> and <code>-</code> can also be [[unary operation|unary]], to represent positive and negative numbers respectively.


Division between integers produces floating-point results. The behavior of division has changed significantly over time:<ref name="pep0238"/>
Division between integers produces floating-point results. The behavior of division has changed significantly over time:<ref name="pep0238"/>
* The current version of Python (i.e., since 3.0) changed <code>the /</code> operator to always represent floating-point division, e.g., {{code|class=nowrap|2=python|1=5/2 == 2.5}}.
* The current version of Python (i.e., since 3.0) changed the <code>/</code> operator to always represent floating-point division, e.g., {{code|class=nowrap|2=python|1=5/2 == 2.5}}.
* The floor division <code>//</code> operator was introduced. Thus <code>7//3 == 2</code>, <code>-7//3 == -3</code>, <code>7.5//3 == 2.0</code>, and <code>-7.5//3 == -3.0</code>. For outdated Python 2.7 adding the {{code|class=nowrap|2=python2|1=from __future__ import division}} statement causes a module in Python 2.7 to use Python&nbsp;3.0 rules for division instead (see above).
* The floor division <code>//</code> operator was introduced, meaning that <code>7//3 == 2</code>, <code>-7//3 == -3</code>, <code>7.5//3 == 2.0</code>, and <code>-7.5//3 == -3.0</code>. For Python 2.7, adding the {{code|class=nowrap|2=python2|1=from __future__ import division}} statement allows a module in Python 2.7 to use Python 3.x rules for division (see above).


In Python terms, the <code>/</code> operator represents ''true division'' (or simply ''division''), while the <code>//</code> operator represents ''floor division.'' Before version 3.0, the <code>/</code> operator represents ''classic division''.<ref name="pep0238"/>
In Python terms, the <code>/</code> operator represents ''true division'' (or simply ''division''), while the <code>//</code> operator represents ''floor division.'' Before version 3.0, the <code>/</code> operator represents ''classic division''.<ref name="pep0238"/>


[[Rounding]] towards negative infinity, though a different method than in most languages, adds consistency to Python. For instance, this rounding implies that the equation {{code|class=nowrap|2=python|1=(a + b)//b == a//b + 1}} is always true. The rounding also implies that the equation {{code|class=nowrap|2=python|1=b*(a//b) + a%b == a}} is valid for both positive and negative values of <code>a</code>. As expected, the result of <code>a%b</code> lies in the [[half-open interval]] [0, ''b''), where <code>b</code> is a positive integer; however, maintaining the validity of the equation requires that the result must lie in the interval (''b'', 0] when <code>b</code> is negative.<ref name="AutoNT-62"/>
[[Rounding]] towards negative infinity, though a different method than in most languages, adds consistency to Python. For instance, this rounding implies that the equation {{code|class=nowrap|2=python|1=(a + b)//b == a//b + 1}} is always true. Also, the rounding implies that the equation {{code|class=nowrap|2=python|1=b*(a//b) + a%b == a}} is valid for both positive and negative values of <code>a</code>. As expected, the result of <code>a%b</code> lies in the [[half-open interval]] [0, ''b''), where <code>b</code> is a positive integer; however, maintaining the validity of the equation requires that the result must lie in the interval (''b'', 0] when <code>b</code> is negative.<ref name="AutoNT-62"/>


Python provides a <code>round</code> function for rounding a float to the nearest integer. For [[Rounding#Tie-breaking|tie-breaking]], Python&nbsp;3 uses the ''round to even'' method: <code>round(1.5)</code> and <code>round(2.5)</code> both produce <code>2</code>.<ref name="AutoNT-64"/> Python versions before 3 used the [[Rounding#Rounding away from zero|round-away-from-zero]] method: <code>round(0.5)</code> is <code>1.0</code>, and <code>round(-0.5)</code> is <code>−1.0</code>.<ref name="AutoNT-63"/>
Python provides a <code>round</code> function for rounding a float to the nearest integer. For [[Rounding#Tie-breaking|tie-breaking]], Python&nbsp;3 uses the ''round to even'' method: <code>round(1.5)</code> and <code>round(2.5)</code> both produce <code>2</code>.<ref name="AutoNT-64"/> Python versions before 3 used the [[Rounding#Rounding away from zero|round-away-from-zero]] method: <code>round(0.5)</code> is <code>1.0</code>, and <code>round(-0.5)</code> is <code>−1.0</code>.<ref name="AutoNT-63"/>
Line 369: Line 294:
Python uses [[arbitrary-precision arithmetic]] for all integer operations. The <code>Decimal</code> type/class in the <code>decimal</code> module provides [[decimal floating point|decimal floating-point numbers]] to a pre-defined arbitrary precision with several rounding modes.<ref name="AutoNT-88"/> The <code>Fraction</code> class in the <code>fractions</code> module provides arbitrary precision for [[rational number]]s.<ref>{{cite web|title=What's New in Python 2.6 |url=https://docs.python.org/2.6/whatsnew/2.6.html|website=Python v2.6.9 documentation |date=Oct 29, 2013 |access-date=26 September 2015|archive-date=23 December 2019|archive-url=https://web.archive.org/web/20191223213856/https://docs.python.org/2.6/whatsnew/2.6.html|url-status=live}}</ref>
Python uses [[arbitrary-precision arithmetic]] for all integer operations. The <code>Decimal</code> type/class in the <code>decimal</code> module provides [[decimal floating point|decimal floating-point numbers]] to a pre-defined arbitrary precision with several rounding modes.<ref name="AutoNT-88"/> The <code>Fraction</code> class in the <code>fractions</code> module provides arbitrary precision for [[rational number]]s.<ref>{{cite web|title=What's New in Python 2.6 |url=https://docs.python.org/2.6/whatsnew/2.6.html|website=Python v2.6.9 documentation |date=Oct 29, 2013 |access-date=26 September 2015|archive-date=23 December 2019|archive-url=https://web.archive.org/web/20191223213856/https://docs.python.org/2.6/whatsnew/2.6.html|url-status=live}}</ref>


Due to Python's extensive mathematics library and the third-party library [[NumPy]], the language is frequently used for scientific scripting in tasks such as numerical data processing and manipulation.<ref>{{Cite web|url=https://www.stat.washington.edu/~hoytak/blog/whypython.html|title=10 Reasons Python Rocks for Research (And a Few Reasons it Doesn't) – Hoyt Koepke|website=University of Washington Department of Statistics |access-date=3 February 2019|archive-date=31 May 2020|archive-url=https://web.archive.org/web/20200531211840/https://www.stat.washington.edu/~hoytak/blog/whypython.html|url-status=dead}}</ref><ref>{{Cite web|url=https://engineering.ucsb.edu/~shell/che210d/python.pdf|title=An introduction to Python for scientific computing|last=Shell|first=Scott|date=17 June 2014|access-date=3 February 2019|archive-date=4 February 2019|archive-url=https://web.archive.org/web/20190204014642/https://engineering.ucsb.edu/~shell/che210d/python.pdf|url-status=live}}</ref>
Due to Python's extensive mathematics library and the third-party library [[NumPy]], the language is frequently used for scientific scripting in tasks such as numerical data processing and manipulation.<ref>{{Cite web|url=https://www.stat.washington.edu/~hoytak/blog/whypython.html|title=10 Reasons Python Rocks for Research (And a Few Reasons it Doesn't) – Hoyt Koepke|website=University of Washington Department of Statistics |access-date=3 February 2019|archive-date=31 May 2020|archive-url=https://web.archive.org/web/20200531211840/https://www.stat.washington.edu/~hoytak/blog/whypython.html}}</ref><ref>{{Cite web|url=https://engineering.ucsb.edu/~shell/che210d/python.pdf|title=An introduction to Python for scientific computing|last=Shell|first=Scott|date=17 June 2014|access-date=3 February 2019|archive-date=4 February 2019|archive-url=https://web.archive.org/web/20190204014642/https://engineering.ucsb.edu/~shell/che210d/python.pdf|url-status=live}}</ref>


===Function syntax===
===Function syntax===
[[Function (computer programming)|Functions]] are created in Python by using the <code>def</code> keyword. A function is defined similarly to how it is called, by first providing the function name and then the required parameters. Here is an example of a function that prints its inputs:
[[Function (computer programming)|Functions]] are created in Python by using the <code>def</code> keyword. A function is defined similarly to how it is called, by first providing the function name and then the required parameters. Here is an example of a function that prints its inputs:
<syntaxhighlight lang="python3">
<syntaxhighlight lang="python3">
def printer(input1, input2="already there"):
def printer(input1, input2 = "already there"):
     print(input1)
     print(input1)
     print(input2)
     print(input2)
Line 388: Line 313:
[["Hello, World!" program]]:
[["Hello, World!" program]]:
<syntaxhighlight lang="python">
<syntaxhighlight lang="python">
print('Hello, world!')
print('Hello, World!')
</syntaxhighlight>
</syntaxhighlight>


Program to calculate the [[factorial]] of a positive integer:
Program to calculate the [[factorial]] of a non-negative integer:
<syntaxhighlight lang="python" line="1">
<syntaxhighlight lang="python" line="1">
n = int(input('Type a number, and its factorial will be printed: '))
text = input('Type a number, and its factorial will be printed: ')
n = int(text)


if n < 0:
if n < 0:
Line 415: Line 341:
Some parts of the standard library are covered by specifications—for example, the [[Web Server Gateway Interface]] (WSGI) implementation <code>wsgiref</code> follows PEP 333<ref name="AutoNT-89"/>—but most parts are specified by their code, internal documentation, and [[test suite]]s. However, because most of the standard library is cross-platform Python code, only a few modules must be altered or rewritten for variant implementations.
Some parts of the standard library are covered by specifications—for example, the [[Web Server Gateway Interface]] (WSGI) implementation <code>wsgiref</code> follows PEP 333<ref name="AutoNT-89"/>—but most parts are specified by their code, internal documentation, and [[test suite]]s. However, because most of the standard library is cross-platform Python code, only a few modules must be altered or rewritten for variant implementations.


{{As of|2025|03|13|post=,}} the [[Python Package Index]] (PyPI), the official repository for third-party Python software, contains over 614,339<ref name="PyPI">{{cite web |date=2025-03-13 |title=PyPI |url=https://pypi.org/ |url-status=live |archive-url=https://web.archive.org/web/20250222013445/https://pypi.org/ |archive-date=2025-02-22 |website=PyPI}}</ref> packages. These have a wide range of functionality, including the following:
{{As of|2025|03|13|post=,}} the [[Python Package Index]] (PyPI), the official repository for third-party Python software, contains over 614,339<ref name="PyPI">{{cite web |date=2025-03-13 |title=PyPI |url=https://pypi.org/ |url-status=live |archive-url=https://web.archive.org/web/20250222013445/https://pypi.org/ |archive-date=2025-02-22 |website=PyPI}}</ref> packages.
 
{{columns-list|colwidth=30em|
* [[Automation]]
* [[Data analytics]]
* [[Database]]s
* [[Documentation]]
* [[Graphical user interface]]s
* [[Image processing]]
* [[Machine learning]]
* [[Mobile app]]s
* [[Multimedia]]
* [[Computer networking]]
* [[Scientific computing]]
* [[System administration]]
* [[Test framework]]s
* [[Text processing]]
* [[Web framework]]s
* [[Web scraping]]
}}


==Development environments==
==Development environments==
{{See also|Comparison of integrated development environments#Python}}
{{See also|Comparison of integrated development environments#Python}}


Most Python implementations (including CPython) include a [[read–eval–print loop]] (REPL); this permits the environment to function as a [[command line interpreter]], with which users enter statements sequentially and receive results immediately.
Most{{which?|date=August 2025}} Python implementations (including CPython) include a [[read–eval–print loop]] (REPL); this permits the environment to function as a [[command line interpreter]], with which users enter statements sequentially and receive results immediately.<ref>{{cite web |title=Glossary: interactive |url=https://docs.python.org/3/glossary.html#term-interactive |website=Python documentation |access-date=31 August 2025 |language=en |version=v3.13.7}}</ref>


Python is also bundled with an [[integrated development environment|integrated development environment (IDE)]] called [[IDLE]], which is oriented toward beginners.
Also, CPython is bundled with an [[integrated development environment|integrated development environment (IDE)]] called [[IDLE]],<ref name="idle">{{cite web |title=IDLE — Python editor and shell |url=https://docs.python.org/3/library/idle.html |website=Python documentation |version=v3.13.7 |access-date=31 August 2025 |language=en |quote=IDLE is Python's Integrated Development and Learning Environment.}}</ref> which is oriented toward beginners.{{cn|date=August 2025}}


Other shells, including [[IDLE]] and [[IPython]], add additional capabilities such as improved auto-completion, session-state retention, and [[syntax highlighting]].
Other shells, including [[IDLE]] and [[IPython]], add additional capabilities such as improved auto-completion, session-state retention, and [[syntax highlighting]].<ref name="idle" /><ref>{{cite web |title=IPython Documentation |url=https://ipython.readthedocs.io/en/stable/ |access-date=31 August 2025 |archive-url=https://web.archive.org/web/20250831204721/https://ipython.readthedocs.io/en/stable/ |archive-date=2025-08-31 |language=en |version=v9.5.0 |date=August 29, 2025 |url-status=live}}</ref>


Standard desktop IDEs include PyCharm, IntelliJ Idea, Visual Studio Code; there are also [[web browser]]-based IDEs, such as the following environments:
Standard desktop IDEs include [[PyCharm]], [[Spyder (software)|Spyder]], and [[Visual Studio Code]];{{cn|date=August 2025}} there are [[web browser]]-based IDEs, such as the following environments:


* [[SageMath]], for developing science- and math-related programs;
* [[Project Jupyter|Jupyter Notebooks]], an open-source interactive computing platform;<ref>{{cite web |title=Project Jupyter |url=https://jupyter.org |website=Jupyter.org |access-date=2 April 2025 |archive-date=12 October 2023 |archive-url=https://web.archive.org/web/20231012055917/https://jupyter.org/ |url-status=live}}</ref>
* [[Project Jupyter|Jupyter Notebooks]], an open-source interactive computing platform;
* [[PythonAnywhere]], a browser-based IDE and hosting environment; and
* [[PythonAnywhere]], a browser-based IDE and hosting environment; and
* Canopy IDE, a commercial IDE that emphasizes [[scientific computing]].<ref>{{cite web|last1=Enthought|first1=Canopy|title=Canopy|url=https://www.enthought.com/products/canopy/|website=www.enthought.com|access-date=20 August 2016|archive-date=15 July 2017|archive-url=https://web.archive.org/web/20170715151703/https://www.enthought.com/products/canopy/|url-status=dead}}</ref><ref>{{cite web |title=Project Jupyter |url=https://jupyter.org |website=Jupyter.org |access-date=2 April 2025 |archive-date=12 October 2023 |archive-url=https://web.archive.org/web/20231012055917/https://jupyter.org/ |url-status=live}}</ref>
* Canopy, a commercial IDE from [[Enthought]] that emphasizes [[scientific computing]].<ref>{{cite web |last1=Harper |first1=Doug |title=Enthought Canopy |url=http://physics.wku.edu/phys316/software/canopy/ |website=WKU Physics 316 |publisher=[[Western Kentucky University]] |access-date=31 August 2025 |archive-url=https://web.archive.org/web/20240818041226/http://physics.wku.edu/phys316/software/canopy/ |archive-date=2024-08-18 |language=en |date=Spring 2024 |url-status=live}}</ref><ref>{{cite web|title=Enthought Canopy|url=https://www.enthought.com/products/canopy/|website=[[Enthought]]|access-date=20 August 2016|archive-date=15 July 2017|archive-url=https://web.archive.org/web/20170715151703/https://www.enthought.com/products/canopy/}}</ref>


==Implementations==
==Implementations==
Line 456: Line 362:


===Reference implementation===
===Reference implementation===
[[CPython]] is the [[reference implementation]] of Python. This implementation is written in C, meeting the [[C11 (C standard revision)|C11]] standard<ref>{{Cite web |title=PEP 7 – Style Guide for C Code {{!}} peps.python.org |url=https://peps.python.org/pep-0007/ |access-date=2022-04-28 |website=peps.python.org |archive-date=24 April 2022 |archive-url=https://web.archive.org/web/20220424202827/https://peps.python.org/pep-0007/ |url-status=live}}</ref> (since version 3.11, older versions use the [[C89 (C version)|C89]] standard with several select [[C99]] features), but third-party extensions are not limited to older C versions—e.g., they can be implemented using C11 or C++.<ref>{{Cite web|title=4. Building C and C++ Extensions – Python 3.9.2 documentation|url=https://docs.python.org/3/extending/building.html|access-date=2021-03-01|website=docs.python.org|archive-date=3 March 2021|archive-url=https://web.archive.org/web/20210303002519/https://docs.python.org/3/extending/building.html|url-status=live}}</ref><ref name="AutoNT-66"/> CPython [[compiler|compiles]] Python programs into an intermediate [[bytecode]],<ref name="AutoNT-67"/> which is then executed by a [[virtual machine]].<ref name="AutoNT-68"/> CPython is distributed with a large standard library written in a combination of C and native Python.
[[CPython]] is the [[reference implementation]] of Python. This implementation is written in C, meeting the [[C11 (C standard revision)|C11]] standard<ref>{{Cite web |title=PEP 7 – Style Guide for C Code {{!}} peps.python.org |url=https://peps.python.org/pep-0007/ |access-date=2022-04-28 |website=peps.python.org |archive-date=24 April 2022 |archive-url=https://web.archive.org/web/20220424202827/https://peps.python.org/pep-0007/ |url-status=live}}</ref> since version 3.11. Older versions use the [[C89 (C version)|C89]] standard with several select [[C99]] features, but third-party extensions are not limited to older C versions—e.g., they can be implemented using C11 or C++.<ref>{{Cite web|title=4. Building C and C++ Extensions – Python 3.9.2 documentation|url=https://docs.python.org/3/extending/building.html|access-date=2021-03-01|website=docs.python.org|archive-date=3 March 2021|archive-url=https://web.archive.org/web/20210303002519/https://docs.python.org/3/extending/building.html|url-status=live}}</ref><ref name="AutoNT-66"/> CPython [[compiler|compiles]] Python programs into an intermediate [[bytecode]],<ref name="AutoNT-67"/> which is then executed by a [[virtual machine]].<ref name="AutoNT-68"/> CPython is distributed with a large standard library written in a combination of C and native Python.


CPython is available for many platforms, including Windows and most modern [[Unix-like]] systems, including macOS (and [[Apple M1]] Macs, since Python&nbsp;3.9.1, using an experimental installer). <!-- "Windows Vista support dropped in Python 3.7" -->Starting with Python&nbsp;3.9, the Python installer intentionally fails to install on [[Windows 7]] and 8<!-- but not 8.1? -->;<ref>{{Cite web |title=Changelog – Python 3.9.0 documentation |url=https://docs.python.org/release/3.9.0/whatsnew/changelog.html#changelog |url-status=live |archive-url=https://web.archive.org/web/20210207001142/https://docs.python.org/release/3.9.0/whatsnew/changelog.html#changelog |archive-date=7 February 2021 |access-date=2021-02-08 |website=docs.python.org}}</ref><ref>{{Cite web |title=Download Python |url=https://www.python.org/downloads/release/python-391 |url-status=live |archive-url=https://web.archive.org/web/20201208045225/https://www.python.org/downloads/release/python-391/ |archive-date=8 December 2020 |access-date=2020-12-13 |website=Python.org |language=en}}</ref> [[Windows XP]] was supported until Python&nbsp;3.5<!--"Windows XP support dropped in Python 3.5"-->, with unofficial support for [[OpenVMS|VMS]].<!--"Put online a new version of Python 3.10.0a (IA64only)"--><ref>{{Cite web|title=history [vmspython]|url=https://www.vmspython.org/doku.php?id=history|access-date=2020-12-04|website=www.vmspython.org|archive-date=2 December 2020|archive-url=https://web.archive.org/web/20201202194743/https://www.vmspython.org/doku.php?id=history|url-status=live}}</ref> Platform portability was one of Python's earliest priorities.<ref name="AutoNT-69" /> During development of Python&nbsp;1 and 2, even [[OS/2]] and [[Solaris (operating system)|Solaris]] were supported;<!-- Also python-3.2.2 at http://unixpackages.com/packages/package-list --><ref>{{Cite web|title=Download Python for Other Platforms|url=https://www.python.org/download/other/|access-date=2020-12-04|website=Python.org|language=en|archive-date=27 November 2020|archive-url=https://web.archive.org/web/20201127015815/https://www.python.org/download/other/|url-status=live}}</ref> since that time, support has been dropped for many platforms.<!--
CPython is available for many platforms, including Windows and most modern [[Unix-like]] systems, including macOS (and [[Apple M1]] Macs, since Python&nbsp;3.9.1, using an experimental installer). <!-- "Windows Vista support dropped in Python 3.7" -->Starting with Python&nbsp;3.9, the Python installer intentionally fails to install on [[Windows 7]] and 8<!-- but not 8.1? -->;<ref>{{Cite web |title=Changelog – Python 3.9.0 documentation |url=https://docs.python.org/release/3.9.0/whatsnew/changelog.html#changelog |url-status=live |archive-url=https://web.archive.org/web/20210207001142/https://docs.python.org/release/3.9.0/whatsnew/changelog.html#changelog |archive-date=7 February 2021 |access-date=2021-02-08 |website=docs.python.org}}</ref><ref>{{Cite web |title=Download Python |url=https://www.python.org/downloads/release/python-391 |url-status=live |archive-url=https://web.archive.org/web/20201208045225/https://www.python.org/downloads/release/python-391/ |archive-date=8 December 2020 |access-date=2020-12-13 |website=Python.org |language=en}}</ref> [[Windows XP]] was supported until Python&nbsp;3.5<!--"Windows XP support dropped in Python 3.5"-->, with unofficial support for [[OpenVMS|VMS]].<!--"Put online a new version of Python 3.10.0a (IA64only)"--><ref>{{Cite web|title=history [vmspython]|url=https://www.vmspython.org/doku.php?id=history|access-date=2020-12-04|website=www.vmspython.org|archive-date=2 December 2020|archive-url=https://web.archive.org/web/20201202194743/https://www.vmspython.org/doku.php?id=history|url-status=live}}</ref> Platform portability was one of Python's earliest priorities.<ref name="AutoNT-69" /> During development of Python&nbsp;1 and 2, even [[OS/2]] and [[Solaris (operating system)|Solaris]] were supported;<!-- Also python-3.2.2 at http://unixpackages.com/packages/package-list --><ref name="DownloadOther"/><!-- older reference have access-date=2020-12-04 archive-date=27 November 2020 --> since that time, support has been dropped for many platforms.<!--


Starting with CPython 3.7.0, *nix platforms are expected to provide at least one of C.UTF-8 (full locale), C.utf8 (full locale) or UTF-8 (LC_CTYPE-only locale) as an alternative to the legacy C locale.
Starting with CPython 3.7.0, *nix platforms are expected to provide at least one of C.UTF-8 (full locale), C.utf8 (full locale) or UTF-8 (LC_CTYPE-only locale) as an alternative to the legacy C locale.
Line 464: Line 370:


All current Python versions (since 3.7) support only operating systems that feature multithreading<!-- (then in 3.7 removing support for [[IRIX]]; and before many other operating systems such as [[OS/2]] and [[VMS]]) -->, by now supporting not nearly as many operating systems (dropping many outdated) than in the past.
All current Python versions (since 3.7) support only operating systems that feature multithreading<!-- (then in 3.7 removing support for [[IRIX]]; and before many other operating systems such as [[OS/2]] and [[VMS]]) -->, by now supporting not nearly as many operating systems (dropping many outdated) than in the past.
===Limitations of the reference implementation===
* The energy usage of Python with CPython for typically written code is much worse than C by a factor of 75.88.<ref name=":1">{{Cite book |last1=Pereira |first1=Rui |last2=Couto |first2=Marco |last3=Ribeiro |first3=Francisco |last4=Rua |first4=Rui |last5=Cunha |first5=Jácome |last6=Fernandes |first6=João Paulo |last7=Saraiva |first7=João |chapter=Energy efficiency across programming languages: How do energy, time, and memory relate? |date=2017-10-23 |title=Proceedings of the 10th ACM SIGPLAN International Conference on Software Language Engineering |chapter-url=https://doi.org/10.1145/3136014.3136031 |series=SLE 2017 |location=New York, NY, USA |publisher=Association for Computing Machinery |pages=256–267 |doi=10.1145/3136014.3136031 |isbn=978-1-4503-5525-4 |url=http://repositorio.inesctec.pt/handle/123456789/5492 }}</ref>
* The throughput of Python with CPython for typically written code is worse than C by a factor of 71.9.<ref name=":1" />
* The average memory usage of CPython for typically written code is worse than C by a factor of 2.4.<ref name=":1" />


===Other implementations===
===Other implementations===
All alternative implementations have at least slightly different semantic. For example, an alternative may include unordered dictionaries<!-- like with Codon; also PyPy? Cython? -->, in contrast to other current Python versions. As another example in the larger Python ecosystem, PyPy does not support the full C Python API. Alternative implementations include the following:
All alternative implementations have at least slightly different semantics. For example, an alternative may include unordered dictionaries<!-- like with Codon; also PyPy? Cython? -->, in contrast to other current Python versions. As another example in the larger Python ecosystem, PyPy does not support the full C Python API.


* [[PyPy]] is a fast, compliant interpreter of Python&nbsp;2.7 and <!-- 3.8 (both are outdated CPython versions) --> 3.10.<ref name="AutoNT-70"/><ref>{{Cite web|last=Team|first=The PyPy|date=2019-12-28|title=Download and Install|url=https://www.pypy.org/download.html|access-date=2022-01-08|website=PyPy|language=en|archive-date=8 January 2022|archive-url=https://web.archive.org/web/20220108212951/https://www.pypy.org/download.html|url-status=live}}</ref> PyPy's [[just-in-time compiler]] often improves speed significantly relative to CPython, but PyPy does not support some libraries written in C.<ref name="AutoNT-71"/> PyPy offers support for the [[RISC-V]] instruction-set architecture.
Creating an executable with Python often is done by bundling an entire Python interpreter into the executable, which causes binary sizes to be massive for small programs,<ref>{{cite web|url=https://pyinstaller.org/en/stable/operating-mode.html|title=What PyInstaller Does and How It Does It}}</ref> yet there exist implementations that are capable of truly compiling Python. Alternative implementations include the following:
* Codon is an implentation with an [[ahead-of-time compilation|ahead-of-time (AOT) compiler]], which compiles a statically-typed Python-like language whose "syntax and semantics are nearly identical to Python's, there are some notable differences"<ref>{{Cite web |title=Codon: Differences with Python |url=https://docs.exaloop.io/codon/general/differences |url-status=live |archive-url=https://web.archive.org/web/20230525002540/https://docs.exaloop.io/codon/general/differences |archive-date=2023-05-25 |access-date=2023-08-28}}</ref> For example, Codon uses 64-bit machine integers for speed, not arbitrarily as with Python; Codon developers claim that speedups over CPython are usually on the order of ten to a hundred times. Codon compiles to machine code (via [[LLVM]]) and supports native multithreading.<ref>{{Cite web |last=Lawson |first=Loraine |date=2023-03-14 |title=MIT-Created Compiler Speeds up Python Code |url=https://thenewstack.io/mit-created-compiler-speeds-up-python-code/ |url-status=live |archive-url=https://web.archive.org/web/20230406054200/https://thenewstack.io/mit-created-compiler-speeds-up-python-code/ |archive-date=2023-04-06 |access-date=2023-08-28 |website=The New Stack |language=en-US}}</ref> <!-- It's compile has a restrictive BSL licence, but it doesn't affect generated code: --> Codon can also compile to Python extension modules that can be imported and used from Python.
 
* [[PyPy]] is a faster, compliant interpreter of Python&nbsp;2.7 and <!-- 3.8 (both are outdated CPython versions) --> 3.10.<ref name="AutoNT-70"/><ref>{{Cite web|last=Team|first=The PyPy|date=2019-12-28|title=Download and Install|url=https://www.pypy.org/download.html|access-date=2022-01-08|website=PyPy|language=en|archive-date=8 January 2022|archive-url=https://web.archive.org/web/20220108212951/https://www.pypy.org/download.html|url-status=live}}</ref> PyPy's [[just-in-time compiler]] often improves speed significantly relative to CPython, but PyPy does not support some libraries written in C.<ref name="AutoNT-71"/> PyPy offers support for the [[RISC-V]] instruction-set architecture.
* Codon is an implementation with an [[ahead-of-time compilation|ahead-of-time (AOT) compiler]], which compiles a statically-typed Python-like language whose "syntax and semantics are nearly identical to Python's, there are some notable differences"<ref>{{Cite web |title=Codon: Differences with Python |url=https://docs.exaloop.io/codon/general/differences |url-status=live |archive-url=https://web.archive.org/web/20230525002540/https://docs.exaloop.io/codon/general/differences |archive-date=2023-05-25 |access-date=2023-08-28}}</ref> For example, Codon uses 64-bit machine integers for speed, not arbitrarily as with Python; Codon developers claim that speedups over CPython are usually on the order of ten to a hundred times. Codon compiles to machine code (via [[LLVM]]) and supports native multithreading.<ref>{{Cite web |last=Lawson |first=Loraine |date=2023-03-14 |title=MIT-Created Compiler Speeds up Python Code |url=https://thenewstack.io/mit-created-compiler-speeds-up-python-code/ |url-status=live |archive-url=https://web.archive.org/web/20230406054200/https://thenewstack.io/mit-created-compiler-speeds-up-python-code/ |archive-date=2023-04-06 |access-date=2023-08-28 |website=The New Stack |language=en-US}}</ref> <!-- It's compile has a restrictive BSL licence, but it doesn't affect generated code: --> Codon can also compile to Python extension modules that can be imported and used from Python.
* [[MicroPython]] and [[CircuitPython]] are Python&nbsp;3 variants that are optimized for [[microcontroller]]s, including the [[Lego Mindstorms EV3]].<ref>{{Cite web|url=https://education.lego.com/en-us/support/mindstorms-ev3/python-for-ev3|title=Python-for-EV3|website=LEGO Education|language=en|access-date=17 April 2019|archive-date=7 June 2020|archive-url=https://web.archive.org/web/20200607234814/https://education.lego.com/en-us/support/mindstorms-ev3/python-for-ev3|url-status=live}}</ref>
* [[MicroPython]] and [[CircuitPython]] are Python&nbsp;3 variants that are optimized for [[microcontroller]]s, including the [[Lego Mindstorms EV3]].<ref>{{Cite web|url=https://education.lego.com/en-us/support/mindstorms-ev3/python-for-ev3|title=Python-for-EV3|website=LEGO Education|language=en|access-date=17 April 2019|archive-date=7 June 2020|archive-url=https://web.archive.org/web/20200607234814/https://education.lego.com/en-us/support/mindstorms-ev3/python-for-ev3|url-status=live}}</ref>
* Pyston is a variant of the Python runtime that uses just-in-time compilation to speed up execution of Python programs.<ref>{{cite news|url=https://www.infoworld.com/article/3587591/pyston-returns-from-the-dead-to-speed-python.html|title=Pyston returns from the dead to speed Python|last=Yegulalp|first=Serdar|date=29 October 2020|website=[[InfoWorld]]|access-date=26 January 2021|archive-date=27 January 2021|archive-url=https://web.archive.org/web/20210127113233/https://www.infoworld.com/article/3587591/pyston-returns-from-the-dead-to-speed-python.html|url-status=live}}</ref>
* Pyston is a variant of the Python runtime that uses just-in-time compilation to speed up execution of Python programs.<ref>{{cite news|url=https://www.infoworld.com/article/3587591/pyston-returns-from-the-dead-to-speed-python.html|title=Pyston returns from the dead to speed Python|last=Yegulalp|first=Serdar|date=29 October 2020|website=[[InfoWorld]]|access-date=26 January 2021|archive-date=27 January 2021|archive-url=https://web.archive.org/web/20210127113233/https://www.infoworld.com/article/3587591/pyston-returns-from-the-dead-to-speed-python.html|url-status=live}}</ref>
Line 483: Line 396:
* [[PyS60]] was a Python&nbsp;2 interpreter for [[Series 60]] mobile phones, which was released by [[Nokia]] in 2005. The interpreter implemented many modules from Python's standard library, as well as additional modules for integration with the [[Symbian]] operating system. The Nokia [[N900]] also supports Python through the [[GTK]] widget library, allowing programs to be written and run on the target device.<ref>{{cite web|title=Python on the Nokia N900|url=http://www.stochasticgeometry.ie/2010/04/29/python-on-the-nokia-n900/|website=Stochastic Geometry|date=29 April 2010|access-date=9 July 2015|archive-date=20 June 2019|archive-url=https://web.archive.org/web/20190620000053/http://www.stochasticgeometry.ie/2010/04/29/python-on-the-nokia-n900/|url-status=live}}</ref>
* [[PyS60]] was a Python&nbsp;2 interpreter for [[Series 60]] mobile phones, which was released by [[Nokia]] in 2005. The interpreter implemented many modules from Python's standard library, as well as additional modules for integration with the [[Symbian]] operating system. The Nokia [[N900]] also supports Python through the [[GTK]] widget library, allowing programs to be written and run on the target device.<ref>{{cite web|title=Python on the Nokia N900|url=http://www.stochasticgeometry.ie/2010/04/29/python-on-the-nokia-n900/|website=Stochastic Geometry|date=29 April 2010|access-date=9 July 2015|archive-date=20 June 2019|archive-url=https://web.archive.org/web/20190620000053/http://www.stochasticgeometry.ie/2010/04/29/python-on-the-nokia-n900/|url-status=live}}</ref>


===Cross-compilers to other languages===
===Transpilers to other languages===
There are several compilers/[[transpiler]]s to high-level object languages; the source language is unrestricted Python, a subset of Python, or a language similar to Python:
There are several compilers/[[transpiler]]s to high-level object languages; the source language is unrestricted Python, a subset of Python, or a language similar to Python:
* Brython,<ref>{{Cite web|title=Brython|url=https://brython.info/|access-date=2021-01-21|website=brython.info|archive-date=3 August 2018|archive-url=https://web.archive.org/web/20180803065954/http://brython.info/|url-status=live}}</ref> Transcrypt,<ref>{{cite web|title=Transcrypt – Python in the browser|url=https://www.transcrypt.org|access-date=22 December 2020|website=transcrypt.org|language=en|archive-date=19 August 2018|archive-url=https://web.archive.org/web/20180819133303/http://www.transcrypt.org/|url-status=live}}</ref><ref>{{Cite web|url=https://www.infoq.com/articles/transcrypt-python-javascript-compiler/|title=Transcrypt: Anatomy of a Python to JavaScript Compiler|website=InfoQ|access-date=20 January 2021|archive-date=5 December 2020|archive-url=https://web.archive.org/web/20201205193339/https://www.infoq.com/articles/transcrypt-python-javascript-compiler/|url-status=live}}</ref> and [[Pyjs]] compile Python to [[JavaScript]]. (The latest release of Pyjs was in 2012.)
* Brython<ref>{{Cite web|title=Brython|url=https://brython.info/|access-date=2021-01-21|website=brython.info|archive-date=3 August 2018|archive-url=https://web.archive.org/web/20180803065954/http://brython.info/|url-status=live}}</ref> and Transcrypt<ref>{{cite web|title=Transcrypt – Python in the browser|url=https://www.transcrypt.org|access-date=22 December 2020|website=transcrypt.org|language=en|archive-date=19 August 2018|archive-url=https://web.archive.org/web/20180819133303/http://www.transcrypt.org/|url-status=live}}</ref><ref>{{Cite web|url=https://www.infoq.com/articles/transcrypt-python-javascript-compiler/|title=Transcrypt: Anatomy of a Python to JavaScript Compiler|website=InfoQ|access-date=20 January 2021|archive-date=5 December 2020|archive-url=https://web.archive.org/web/20201205193339/https://www.infoq.com/articles/transcrypt-python-javascript-compiler/|url-status=live}}</ref> compile Python to [[JavaScript]].
* [[Cython]] compiles a superset of Python<!-- actually 2.7 by default, but Python 3 by override --> to C. The resulting code can be used with Python via direct C-level API calls into the Python interpreter.
* [[Cython]] compiles a superset of Python<!-- actually 2.7 by default, but Python 3 by override --> to C. The resulting code can be used with Python via direct C-level API calls into the Python interpreter.
* PyJL compiles/transpiles a subset of Python to "human-readable, maintainable, and high-performance Julia source code".<ref name=PyJL>{{Cite web|title=Transpiling Python to Julia using PyJL|url=https://web.ist.utl.pt/antonio.menezes.leitao/ADA/documents/publications_docs/2022_TranspilingPythonToJuliaUsingPyJL.pdf|quote=After manually modifying one line of code by specifying the necessary type information, we obtained a speedup of 52.6×, making the translated Julia code 19.5× faster than the original Python code.|access-date=20 September 2023|archive-date=19 November 2023|archive-url=https://web.archive.org/web/20231119071525/https://web.ist.utl.pt/antonio.menezes.leitao/ADA/documents/publications_docs/2022_TranspilingPythonToJuliaUsingPyJL.pdf|url-status=live}}</ref> Despite the developers' performance claims, this is not possible for ''arbitrary'' Python code; that is, compiling to a faster language or machine code is known to be impossible in the general case. The semantics of Python might potentially be changed, but in many cases speedup is possible with few or no changes in the Python code. The faster Julia source code can then be used from Python or compiled to machine code.
* PyJL compiles/transpiles a subset of Python to "human-readable, maintainable, and high-performance Julia source code".<ref name=PyJL>{{Cite web|title=Transpiling Python to Julia using PyJL|url=https://web.ist.utl.pt/antonio.menezes.leitao/ADA/documents/publications_docs/2022_TranspilingPythonToJuliaUsingPyJL.pdf|quote=After manually modifying one line of code by specifying the necessary type information, we obtained a speedup of 52.6×, making the translated Julia code 19.5× faster than the original Python code.|access-date=20 September 2023|archive-date=19 November 2023|archive-url=https://web.archive.org/web/20231119071525/https://web.ist.utl.pt/antonio.menezes.leitao/ADA/documents/publications_docs/2022_TranspilingPythonToJuliaUsingPyJL.pdf|url-status=live}}</ref> Despite the developers' performance claims, this is not possible for ''arbitrary'' Python code; that is, compiling to a faster language or machine code is known to be impossible in the general case. The semantics of Python might potentially be changed, but in many cases speedup is possible with few or no changes in the Python code. The faster Julia source code can then be used from Python or compiled to machine code.
* [[Nuitka]] compiles Python into C<!-- "is the optimizing Python compiler written in Python that creates executables that run without a separate installer"-->.<ref>{{cite web|title=Nuitka Home {{!}} Nuitka Home|url=http://nuitka.net/|access-date=18 August 2017|website=nuitka.net|language=en|archive-date=30 May 2020|archive-url=https://web.archive.org/web/20200530211233/https://nuitka.net/|url-status=live}}</ref> This compiler works with Python 3.4 to 3.12 (and 2.6 and 2.7) for Python's main supported platforms (and Windows 7 or even Windows XP) and for Android. The compiler developers claim full support for Python 3.10, <!-- "also finishes full compatibility with the match statements of 3.10"  "From here on, we need to re-visit compatibility. A few more obscured 3.10 features are missing, the 3.11 compatibility is not yet complete" -->partial support for Python 3.11 and 3.12, <!-- "This release bumps the long-awaited 3.12 support to a complete level. Now, Nuitka behaves identically to CPython 3.12 for the most part. .. After being late with 3.12 support, we will now be early with 3.13 support if all goes well." --> and experimental support for Python 3.13. Nuitka supports macOS including Apple Silicon-based versions. <!-- "While arm64 (M1) only builds and x86_64 (Intel) only builds work, the value universal which of course implies twice the size, and as such has other disadvantages, is not yet supported. --> The compiler is free of cost, though it has commercial add-ons (e.g., for hiding source code).<!-- "Container Builds (public + commercial)" -->
* [[Nuitka]] compiles Python into C<!-- "is the optimizing Python compiler written in Python that creates executables that run without a separate installer"-->.<ref>{{cite web|title=Nuitka Home {{!}} Nuitka Home|url=http://nuitka.net/|access-date=18 August 2017|website=nuitka.net|language=en|archive-date=30 May 2020|archive-url=https://web.archive.org/web/20200530211233/https://nuitka.net/|url-status=live}}</ref> This compiler works with Python 3.4 to 3.13 (and 2.6 and 2.7) for Python's main supported platforms (and Windows 7 or even Windows XP) and for Android. The compiler developers claim full support for Python 3.10, <!-- "also finishes full compatibility with the match statements of 3.10"  "From here on, we need to re-visit compatibility. A few more obscured 3.10 features are missing, the 3.11 compatibility is not yet complete" -->partial support for Python 3.11 and 3.12, <!-- "This release bumps the long-awaited 3.12 support to a complete level. Now, Nuitka behaves identically to CPython 3.12 for the most part. .. After being late with 3.12 support, we will now be early with 3.13 support if all goes well." --> and experimental support for Python 3.13. Nuitka supports macOS including Apple Silicon-based versions. <!-- "While arm64 (M1) only builds and x86_64 (Intel) only builds work, the value universal which of course implies twice the size, and as such has other disadvantages, is not yet supported. --> The compiler is free of cost, though it has commercial add-ons (e.g., for hiding source code).<!-- "Container Builds (public + commercial)" -->
* [[Numba]] is a JIT compiler that is used from Python; the compiler translates a subset of Python and NumPy code into fast machine code. This tool is enabled by adding a decorator to the relevant Python code.
* [[Numba]] is a JIT compiler that is used from Python; the compiler translates a subset of Python and NumPy code into fast machine code. This tool is enabled by adding a decorator to the relevant Python code.
* Pythran compiles a subset of Python&nbsp;3 to C++ ([[C++11]]).<ref name="Guelton Brunet Amini Merlini 2015 p=014001">{{cite journal |last1=Guelton |first1=Serge |last2=Brunet |first2=Pierrick |last3=Amini |first3=Mehdi |last4=Merlini |first4=Adrien |last5=Corbillon |first5=Xavier |last6=Raynaud |first6=Alan |title=Pythran: enabling static optimization of scientific Python programs |journal=Computational Science & Discovery |publisher=IOP Publishing |volume=8 |issue=1 |date=16 March 2015 |issn=1749-4699 |doi=10.1088/1749-4680/8/1/014001|doi-access=free |page=014001 |bibcode=2015CS&D....8a4001G}}</ref>
* Pythran compiles a subset of Python&nbsp;3 to C++ ([[C++11]]).<ref name="Guelton Brunet Amini Merlini 2015 p=014001">{{cite journal |last1=Guelton |first1=Serge |last2=Brunet |first2=Pierrick |last3=Amini |first3=Mehdi |last4=Merlini |first4=Adrien |last5=Corbillon |first5=Xavier |last6=Raynaud |first6=Alan |title=Pythran: enabling static optimization of scientific Python programs |journal=Computational Science & Discovery |publisher=IOP Publishing |volume=8 |issue=1 |date=16 March 2015 |issn=1749-4699 |doi=10.1088/1749-4680/8/1/014001|doi-access=free |article-number=014001 |bibcode=2015CS&D....8a4001G}}</ref>
* [[RPython]] can be compiled to C, and it is used to build the PyPy interpreter for Python.
* [[RPython]] can be compiled to C, and it is used to build the PyPy interpreter for Python.
* The Python → 11l → C++ transpiler<ref>{{Cite web |url=https://11l-lang.org/transpiler |title=The Python → 11l → C++ transpiler |access-date=17 July 2022 |archive-date=24 September 2022 |archive-url=https://web.archive.org/web/20220924233728/https://11l-lang.org/transpiler/ |url-status=live}}</ref> compiles a subset of Python&nbsp;3 to C++ ([[C++17]]).
* The Python → 11l → C++ transpiler<ref>{{Cite web |url=https://11l-lang.org/transpiler |title=The Python → 11l → C++ transpiler |access-date=17 July 2022 |archive-date=24 September 2022 |archive-url=https://web.archive.org/web/20220924233728/https://11l-lang.org/transpiler/ |url-status=live}}</ref> compiles a subset of Python&nbsp;3 to C++ ([[C++17]]).
Line 504: Line 417:


===Performance===
===Performance===
A perforance comparison among various Python implementations, using a non-numerical (combinatorial) workload, was presented at EuroSciPy '13.<ref>{{cite conference |title=Performance of Python runtimes on a non-numeric scientific code |last=Murri |first=Riccardo |conference=European Conference on Python in Science (EuroSciPy) |year=2013 |arxiv=1404.6388|bibcode=2014arXiv1404.6388M}}</ref> In addition, Python's performance relative to other programming languages is benchmarked by [[The Computer Language Benchmarks Game]].<ref>{{cite web|title=The Computer Language Benchmarks Game|url=https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/python.html|access-date=30 April 2020|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614210246/https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/python.html|url-status=live}}</ref>
A performance comparison among various Python implementations, using a non-numerical (combinatorial) workload, was presented at EuroSciPy '13.<ref>{{cite conference |title=Performance of Python runtimes on a non-numeric scientific code |last=Murri |first=Riccardo |conference=European Conference on Python in Science (EuroSciPy) |year=2013 |arxiv=1404.6388|bibcode=2014arXiv1404.6388M}}</ref> In addition, Python's performance relative to other programming languages is benchmarked by [[The Computer Language Benchmarks Game]].<ref>{{cite web|title=The Computer Language Benchmarks Game|url=https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/python.html|access-date=30 April 2020|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614210246/https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/python.html|url-status=live}}</ref>


There are several approaches to optimizing Python performance, given the inherent slowness of an [[interpreted language]]. These approaches include the following strategies or tools:
There are several approaches to optimizing Python performance, despite the inherent slowness of an [[interpreted language]]. These approaches include the following strategies or tools:


* [[Just-in-time compilation]]: Dynamically compiling Python code just before it is executed. This technique is used in libraries such as [[Numba]] and [[PyPy]].
* [[Just-in-time compilation]]: Dynamically compiling parts of a Python program during the execution of the program. This technique is used in libraries such as [[Numba]] and [[PyPy]].
* [[Compiler|Static compilation]]: Python code is compiled into machine code sometime before execution. An example of this approach is Cython, which compiles Python into C.
* [[Compiler|Static compilation]]: Sometimes, Python code can be compiled into machine code sometime before execution. An example of this approach is [[Cython]], which compiles Python into C.
* Concurrency and parallelism: Multiple tasks can be run simultaneously. Python contains modules such as `multiprocessing` to support this form of parallelism. Moreover, this approach helps to overcome limitations of the [[Global interpreter lock|Global Interpreter Lock]] (GIL) in CPU tasks.
* [[Concurrent computing|Concurrency]] and [[Parallel computing|parallelism]]: Multiple tasks can be run simultaneously. Python contains modules such as `multiprocessing` to support this form of parallelism. Moreover, this approach helps to overcome limitations of the [[Global interpreter lock|Global Interpreter Lock]] (GIL) in CPU tasks.
* Efficient data structures: Performance can also be improved by using data types such as <code>Set</code> for membership tests, or <code>deque</code> from <code>collections</code> for [[Queueing theory|queue]] operations.
* Efficient [[data structures]]: Performance can also be improved by using data types such as <code>Set</code> for membership tests, or <code>deque</code> from <code>collections</code> for [[Queueing theory|queue]] operations.
* Performance gains can be observed by utilizing libraries such as [[NumPy]]. Most high performance Python libraries use [[C (programming language)|C]] or [[Fortran]] under the hood instead of the Python interpreter.<ref>{{Cite web |last=Python |first=Real |title=Look Ma, No for Loops: Array Programming With NumPy – Real Python |url=https://realpython.com/numpy-array-programming/ |access-date=2025-10-15 |website=realpython.com |language=en}}</ref> 


==Language Development==
==Language Development==
Python's development is conducted largely through the ''Python Enhancement Proposal'' (PEP) process; this process is the primary mechanism for proposing major new features, collecting community input on issues, and documenting Python design decisions.<ref name="PepCite000"/> Python coding style is covered in PEP&nbsp;8.<ref>{{cite web|url=https://www.python.org/dev/peps/pep-0008/|title=PEP 8 – Style Guide for Python Code|website=Python.org|access-date=26 March 2019|archive-date=17 April 2019|archive-url=https://web.archive.org/web/20190417223549/https://www.python.org/dev/peps/pep-0008/|url-status=live}}</ref> Outstanding PEPs are reviewed and commented on by the Python community and the steering council.<ref name="PepCite000"/>
Python's development is conducted mostly through the ''Python Enhancement Proposal'' (PEP) process; this process is the primary mechanism for proposing major new features, collecting community input on issues, and documenting Python design decisions.<ref name="PepCite000"/> Python coding style is covered in PEP&nbsp;8.<ref name="pep8"/> Outstanding PEPs are reviewed and commented on by the Python community and the steering council.<ref name="PepCite000"/>


Enhancement of the language corresponds with development of the CPython reference implementation. The mailing list python-dev is the primary forum for the language's development. Specific issues were originally discussed in the [[Roundup (issue tracker)|Roundup]] [[bug tracker]] hosted by the foundation.<ref name="AutoNT-21"/> In 2022, all issues and discussions were migrated to [[GitHub]].<ref>{{cite web |url=https://lwn.net/Articles/885854/ |title=Moving Python's bugs to GitHub &#91;LWN.net&#93; |access-date=2 October 2022 |archive-date=2 October 2022 |archive-url=https://web.archive.org/web/20221002183818/https://lwn.net/Articles/885854/ |url-status=live}}</ref> Development originally took place on a [[Self-hosting (web services)|self-hosted]] source-code repository running [[Mercurial]], until Python moved to [[GitHub]] in January 2017.<ref name=py_dev_guide>{{Cite web|url=https://devguide.python.org/|title=Python Developer's Guide – Python Developer's Guide|website=devguide.python.org|access-date=17 December 2019|archive-date=9 November 2020|archive-url=https://web.archive.org/web/20201109032501/https://devguide.python.org/|url-status=live}}</ref>
Enhancement of the language corresponds with development of the CPython reference implementation. The mailing list python-dev is the primary forum for the language's development. Specific issues were originally discussed in the [[Roundup (issue tracker)|Roundup]] [[bug tracker]] hosted by the foundation.<ref name="AutoNT-21"/> In 2022, all issues and discussions were migrated to [[GitHub]].<ref>{{cite web |last1=Edge |first1=Jake |url=https://lwn.net/Articles/885854/ |title=Moving Python's bugs to GitHub &#91;LWN.net&#93; |date=23 February 2022 |access-date=2 October 2022 |archive-date=2 October 2022 |archive-url=https://web.archive.org/web/20221002183818/https://lwn.net/Articles/885854/ |url-status=live}}</ref> Development originally took place on a [[Self-hosting (web services)|self-hosted]] source-code repository running [[Mercurial]], until Python moved to [[GitHub]] in January 2017.<ref name=py_dev_guide>{{Cite web|url=https://devguide.python.org/|title=Python Developer's Guide – Python Developer's Guide|website=devguide.python.org|access-date=17 December 2019|archive-date=9 November 2020|archive-url=https://web.archive.org/web/20201109032501/https://devguide.python.org/|url-status=live}}</ref>


CPython's public releases have three types, distinguished by which part of the version number is incremented:
CPython's public releases have three types, distinguished by which part of the version number is incremented:
* ''Backward-incompatible versions'', where code is expected to break and must be manually [[ported]]. The first part of the version number is incremented. These releases happen infrequently—version 3.0 was released 8 years after 2.0. According to Guido van Rossum, a version 4.0 will probably never exist.<ref>{{Cite web |last=Hughes |first=Owen |date=2021-05-24 |title=Programming languages: Why Python 4.0 might never arrive, according to its creator |url=https://www.techrepublic.com/article/programming-languages-why-python-4-0-will-probably-never-arrive-according-to-its-creator/ |access-date=2022-05-16 |website=TechRepublic |language=en-US |archive-date=14 July 2022 |archive-url=https://web.archive.org/web/20220714201302/https://www.techrepublic.com/article/programming-languages-why-python-4-0-will-probably-never-arrive-according-to-its-creator/ |url-status=live}}</ref>
* ''Backward-incompatible versions'', where code is expected to break and must be manually [[ported]]. The first part of the version number is incremented. These releases happen infrequently—version 3.0 was released 8 years after 2.0. According to Guido van Rossum, a version 4.0 will probably never exist.<ref>{{Cite web |last=Hughes |first=Owen |date=2021-05-24 |title=Programming languages: Why Python 4.0 might never arrive, according to its creator |url=https://www.techrepublic.com/article/programming-languages-why-python-4-0-will-probably-never-arrive-according-to-its-creator/ |access-date=2022-05-16 |website=TechRepublic |language=en-US |archive-date=14 July 2022 |archive-url=https://web.archive.org/web/20220714201302/https://www.techrepublic.com/article/programming-languages-why-python-4-0-will-probably-never-arrive-according-to-its-creator/ |url-status=live}}</ref>
* ''Major or "feature" releases'' are largely compatible with the previous version but introduce new features. The second part of the version number is incremented. Starting with Python&nbsp;3.9, these releases are expected to occur annually.<ref>{{Cite web|url=https://www.python.org/dev/peps/pep-0602/|title=PEP 602 – Annual Release Cycle for Python|website=Python.org|language=en|access-date=6 November 2019|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614202755/https://www.python.org/dev/peps/pep-0602/|url-status=live}}</ref><ref>{{Cite web|url=https://lwn.net/Articles/802777/|title=Changing the Python release cadence [LWN.net]|website=lwn.net|access-date=6 November 2019|archive-date=6 November 2019|archive-url=https://web.archive.org/web/20191106170153/https://lwn.net/Articles/802777/|url-status=live}}</ref> Each major version is supported by bug fixes for several years after its release.<ref name="release-schedule"/>
* ''Major or "feature" releases'' are largely compatible with the previous version but introduce new features. The second part of the version number is incremented. Starting with Python&nbsp;3.9, these releases are expected to occur annually.<ref>{{Cite web|url=https://www.python.org/dev/peps/pep-0602/|title=PEP 602 – Annual Release Cycle for Python|website=Python.org|language=en|access-date=6 November 2019|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614202755/https://www.python.org/dev/peps/pep-0602/|url-status=live}}</ref><ref>{{Cite web|last1=Edge |first1=Jake |url=https://lwn.net/Articles/802777/|title=Changing the Python release cadence [LWN.net]|website=lwn.net|date=23 October 2019 |access-date=6 November 2019|archive-date=6 November 2019|archive-url=https://web.archive.org/web/20191106170153/https://lwn.net/Articles/802777/|url-status=live}}</ref> Each major version is supported by bug fixes for several years after its release.<ref name="release-schedule"/>
* ''Bug fix releases'',<ref name="AutoNT-22"/> which introduce no new features, occur approximately every three months; these releases are made when a sufficient number of bugs have been fixed [[Upstream (software development)|upstream]] since the last release. Security vulnerabilities are also patched in these releases. The third and final part of the version number is incremented.<ref name="AutoNT-22"/>
* ''Bug fix releases'',<ref name="AutoNT-22"/> which introduce no new features, occur approximately every three months; these releases are made when a sufficient number of bugs have been fixed [[Upstream (software development)|upstream]] since the last release. Security vulnerabilities are also patched in these releases. The third and final part of the version number is incremented.<ref name="AutoNT-22"/>


Many [[beta release|alpha, beta, and release-candidates]] are also released as previews and for testing before final releases. Although there is a rough schedule for releases, they are often delayed if the code is not ready yet. Python's development team monitors the state of the code by running a large [[unit test]] suite during development.<ref name="AutoNT-23"/>
Many [[beta release|alpha, beta, and release-candidates]] are also released as previews and for testing before final releases. Although there is a rough schedule for releases, they are often delayed if the code is not ready yet. Python's development team monitors the state of the code by running a large [[unit test]] suite during development.<ref name="AutoNT-23"/>


The major [[academic conference]] on Python is [[PyCon]]. There are also special Python mentoring programs, such as [[PyLadies]].
The major [[academic conference]] on Python is [[PyCon]]. Also, there are special Python mentoring programs, such as [[PyLadies]].
 
==API documentation generators==
Tools that can generate documentation for Python [[API]] include [[pydoc]] (available as part of the standard library); [[Sphinx (documentation generator)|Sphinx]]; and [[Pdoc]] and its forks, [[Doxygen]] and [[Graphviz]].<ref>{{Cite web |title=Documentation Tools |url=https://wiki.python.org/moin/DocumentationTools |access-date=2021-03-22 |website=Python.org |language=en |archive-date=11 November 2020 |archive-url=https://web.archive.org/web/20201111173635/https://wiki.python.org/moin/DocumentationTools |url-status=live}}</ref>


==Naming==
==Naming==
Python's name is inspired by the British comedy group [[Monty Python]], whom Python creator Guido van Rossum enjoyed while developing the language. Monty Python references appear frequently in Python code and culture;<ref name="tutorial-chapter1"/> for example, the [[metasyntactic variable]]s often used in Python literature are [[Spam (Monty Python)|''spam'' and ''eggs'']], rather than the traditional [[foobar|''foo'' and ''bar'']].<ref name="tutorial-chapter1"/><ref name="AutoNT-26"/> The official Python documentation also contains various references to Monty Python routines.<ref>{{cite book |last1=Lutz |first1=Mark |title=Learning Python: Powerful Object-Oriented Programming |year=2009 |publisher=O'Reilly Media, Inc. |isbn=9781449379322 |page=17 |url=https://books.google.com/books?id=1HxWGezDZcgC&pg=PA17 |language=en |access-date=9 May 2017 |archive-date=17 July 2017 |archive-url=https://web.archive.org/web/20170717044012/https://books.google.com/books?id=1HxWGezDZcgC&pg=PA17 |url-status=live}}</ref><ref>{{cite book |last1=Fehily |first1=Chris |title=Python |year=2002 |publisher=Peachpit Press |isbn=9780201748840 |page=xv |url=https://books.google.com/books?id=carqdIdfVlYC&pg=PR15 |language=en |access-date=9 May 2017 |archive-date=17 July 2017 |archive-url=https://web.archive.org/web/20170717044040/https://books.google.com/books?id=carqdIdfVlYC&pg=PR15 |url-status=live}}</ref> Python users are sometimes referred to as "Pythonistas".<ref name="introducing_python">{{Cite book |publisher=Sebastopol, CA : O'Reilly Media |isbn=978-1-4493-5936-2 |last=Lubanovic |first=Bill |title=Introducing Python |access-date=2023-07-31 |date=2014 |url=http://archive.org/details/introducingpytho0000luba |page=305}}</ref>
Python's name is inspired by the British comedy group [[Monty Python]], whom Python creator Guido van Rossum enjoyed while developing the language. Monty Python references appear frequently in Python code and culture;<ref name="tutorial-chapter1"/> for example, the [[metasyntactic variable]]s often used in Python literature are [[Spam (Monty Python)|''spam'' and ''eggs'']], rather than the traditional [[foobar|''foo'' and ''bar'']].<ref name="tutorial-chapter1"/><ref name="AutoNT-26"/> Also, the official Python documentation contains various references to Monty Python routines.{{sfn|Lutz|2013|p=17}}<ref>{{cite book |last1=Fehily |first1=Chris |title=Python |year=2002 |publisher=Peachpit Press |isbn=978-0-201-74884-0 |page=xv |url=https://books.google.com/books?id=carqdIdfVlYC&pg=PR15 |language=en |access-date=9 May 2017 |archive-date=17 July 2017 |archive-url=https://web.archive.org/web/20170717044040/https://books.google.com/books?id=carqdIdfVlYC&pg=PR15 |url-status=live}}</ref> Python users are sometimes referred to as "Pythonistas".<ref name="introducing_python">{{Cite book |publisher=Sebastopol, CA : O'Reilly Media |isbn=978-1-4493-5936-2 |last=Lubanovic |first=Bill |title=Introducing Python |access-date=2023-07-31 |date=2014 |url=http://archive.org/details/introducingpytho0000luba |page=305}}</ref>
 
The [[affix]] ''Py'' is often used when naming Python applications or libraries. Some examples include the following:
 
* [[Pygame]], a [[language binding|binding]] of [[Simple DirectMedia Layer]] to Python (commonly used to create games);
* [[PyQt]] and [[PyGTK]], which bind [[Qt (software)|Qt]] and GTK to Python respectively;
* [[PyPy]], a Python implementation originally written in Python;
* [[NumPy]], a Python library for numerical processing.
 
==Popularity==
Since 2003, Python has consistently ranked in the top ten of the most popular programming languages in the [[TIOBE Programming Community Index]]; {{as of|2022|12|lc=y}}, Python was the most popular language.<ref name=tiobecurrent/> Python was selected as Programming Language of the Year (for "the highest rise in ratings in a year") in 2007, 2010, 2018, and 2020—the only language to have done so four times {{as of|2020|lc=true}}<ref>{{Cite web|last=Blake|first=Troy|date=2021-01-18|title=TIOBE Index for January 2021|url=https://seniordba.wordpress.com/2021/01/18/tiobe-index-for-january-2021/|access-date=2021-02-26|website=Technology News and Information by SeniorDBA|language=en|archive-date=21 March 2021|archive-url=https://web.archive.org/web/20210321143253/https://seniordba.wordpress.com/2021/01/18/tiobe-index-for-january-2021/|url-status=live}}</ref>). In the TIOBE Index, monthly rankings are based on the volume of searches for programming languages on Google, Amazon, Wikipedia, Bing, and 20 other platforms. According to the accompanying graph, Python has shown a marked upward trend since the early 2000s, eventually passing more established languages such as C, C++, and Java. This trend can be attributed to Python's readable syntax, comprehensive standard library, and application in data science and machine learning fields.<ref>{{Cite web |title=TIOBE Index |url=https://www.tiobe.com/tiobe-index/ |access-date=2025-03-31 |website=TIOBE |language=en-US}}</ref>
[[File:Tiobeindex.png|thumb|TIOBE Index Chart showing Python's popularity compared to other programming languages]]
 
Large organizations that use Python include [[Wikipedia]], [[Google]],<ref name="quotes-about-python"/> [[Yahoo!]],<ref name="AutoNT-29"/> [[CERN]],<ref name="AutoNT-30"/> [[NASA]],<ref name="AutoNT-31"/> [[Facebook]],<ref>{{Cite web|url=https://developers.facebook.com/blog/post/301|title=Tornado: Facebook's Real-Time Web Framework for Python – Facebook for Developers|website=Facebook for Developers|language=en-US|access-date=19 June 2018|archive-date=19 February 2019|archive-url=https://web.archive.org/web/20190219031313/https://developers.facebook.com/blog/post/301|url-status=live}}</ref> [[Amazon (company)|Amazon]], [[Instagram]],<ref>{{cite web |url=https://instagram-engineering.com/what-powers-instagram-hundreds-of-instances-dozens-of-technologies-adf2e22da2ad |title=What Powers Instagram: Hundreds of Instances, Dozens of Technologies |date=11 December 2016 |publisher=Instagram Engineering |access-date=27 May 2019 |archive-date=15 June 2020 |archive-url=https://web.archive.org/web/20200615183410/https://instagram-engineering.com/what-powers-instagram-hundreds-of-instances-dozens-of-technologies-adf2e22da2ad |url-status=live}}</ref> [[Spotify]],<ref>{{Cite web|url=https://labs.spotify.com/2013/03/20/how-we-use-python-at-spotify/|title=How we use Python at Spotify|website=Spotify Labs|language=en-US|access-date=25 July 2018|date=20 March 2013|archive-date=10 June 2020|archive-url=https://web.archive.org/web/20200610005143/https://labs.spotify.com/2013/03/20/how-we-use-python-at-spotify/|url-status=live}}</ref> and some smaller entities such as [[Industrial Light & Magic]]<ref name="AutoNT-32"/> and [[ITA Software|ITA]].<ref name="AutoNT-33"/> The social news networking site [[Reddit]] was developed mostly in Python.<ref>{{Citation|title=GitHub – reddit-archive/reddit: historical code from reddit.com.|url=https://github.com/reddit-archive/reddit|publisher=The Reddit Archives|access-date=20 March 2019|archive-date=1 June 2020|archive-url=https://web.archive.org/web/20200601104939/https://github.com/reddit-archive/reddit|url-status=live}}</ref> Organizations that partly use Python include [[Discord]]<ref>{{cite web | url=https://elixir-lang.org/blog/2020/10/08/real-time-communication-at-scale-with-elixir-at-discord/ | title=Real time communication at scale with Elixir at Discord | date=8 October 2020 }}</ref> and [[Baidu]].<ref>{{cite web | url=https://www.freelancinggig.com/blog/2018/07/05/what-programming-language-is-baidu-built-in/#:~:text=Even%20though%20Baidu%20has%20used,part%20JavaScript%20has%20been%20applied | title=What Programming Language is Baidu Built In? | date=5 July 2018 }}</ref>
 
==Types of Use==
{{Main|List of Python software}}
[[File:Python Powered.png|thumb|Software that is powered by Python]]
 
Python has many uses, including the following:
 
* [[Scripting language|Scripting]] for [[web application]]s
* Scientific computing
* [[Artificial intelligence|Artificial-intelligence]] and [[Machine learning|machine-learning]] projects
* [[Graphical user interface|Graphical user interfaces]] and [[Desktop environment|desktop environments]]
* Embedded scripting in software and hardware products
* Operating systems
* [[Information security]]
 
Python can serve as a scripting language for web applications, e.g., via the {{Not a typo|[[mod_wsgi]]}} module for the [[Apache webserver|Apache web server]].<ref name="AutoNT-35" /> With [[Web Server Gateway Interface]], a standard API has evolved to facilitate these applications. [[Web framework]]s such as [[Django (web framework)|Django]], [[Pylons (web framework)|Pylons]], [[Pyramid (web framework)|Pyramid]], [[TurboGears]], [[web2py]], [[Tornado (web server)|Tornado]], [[Flask (web framework)|Flask]], Bottle, and [[Zope]] support developers in the design and maintenance of complex applications. Pyjs and [[IronPython]] can be used to develop the client-side of Ajax-based applications. [[SQLAlchemy]] can be used as a [[Data mapper pattern|data mapper]] to a relational database. [[Twisted (software)|Twisted]] is a framework to program communication between computers; this framework is used by [[Dropbox]], for example.
 
Libraries such as [[NumPy]], [[SciPy]] and [[Matplotlib]] allow the effective use of Python in scientific computing,<ref name="cise">{{cite journal |last=Oliphant |first=Travis |title=Python for Scientific Computing |journal=Computing in Science and Engineering |volume=9 |issue=3 |pages=10–20 |year=2007 |url=https://www.h2desk.com/blog/python-scientific-computing/ |doi=10.1109/MCSE.2007.58 |citeseerx=10.1.1.474.6460 |bibcode=2007CSE.....9c..10O |s2cid=206457124 |access-date=10 April 2015 |archive-date=15 June 2020 |archive-url=https://web.archive.org/web/20200615193226/https://www.h2desk.com/blog/python-scientific-computing/ |url-status=live| issn=1521-9615 }}</ref><ref name="millman">{{cite journal |first1=K. Jarrod |last1=Millman |first2=Michael |last2=Aivazis |title=Python for Scientists and Engineers |journal=Computing in Science and Engineering |volume=13 |number=2 |pages=9–12 |year=2011 |url=http://www.computer.org/csdl/mags/cs/2011/02/mcs2011020009.html |doi=10.1109/MCSE.2011.36 |bibcode=2011CSE....13b...9M |access-date=7 July 2014 |archive-date=19 February 2019 |archive-url=https://web.archive.org/web/20190219031439/https://www.computer.org/csdl/mags/cs/2011/02/mcs2011020009.html |url-status=live}}</ref> with specialized libraries such as [[Biopython]] and [[Astropy]] providing domain-specific functionality. [[SageMath]] is a [[computer algebra system]] with a [[notebook interface]] that is programmable in Python; the SageMath library covers many aspects of [[mathematics]], including [[algebra]], [[combinatorics]], [[numerical mathematics]], [[number theory]], and [[calculus]].<ref name="ICSE" >{{Citation|title=Science education with SageMath|url=http://visual.icse.us.edu.pl/methodology/why_Sage.html|publisher=Innovative Computing in Science Education|access-date=22 April 2019|archive-date=15 June 2020|archive-url=https://web.archive.org/web/20200615180428/http://visual.icse.us.edu.pl/methodology/why_Sage.html|url-status=dead}}</ref> [[OpenCV]] has Python bindings with a rich set of features for [[computer vision]] and [[image processing]].<ref>{{Cite web|title=OpenCV: OpenCV-Python Tutorials|url=https://docs.opencv.org/3.4.9/d6/d00/tutorial_py_root.html|access-date=2020-09-14|website=docs.opencv.org|archive-date=23 September 2020|archive-url=https://web.archive.org/web/20200923063145/https://docs.opencv.org/3.4.9/d6/d00/tutorial_py_root.html|url-status=live}}</ref>
 
Python is commonly used in artificial-intelligence and machine-learning projects, with support from libraries such as [[TensorFlow]], [[Keras]], [[Pytorch]], [[scikit-learn]] and [[ProbLog]] (a logic language).<ref name="whitepaper2015">{{cite web |last1=Dean |first1=Jeff |last2=Monga |first2=Rajat |first3=Sanjay |last3=Ghemawat |display-authors=2 |author-link1=Jeff Dean (computer scientist) |title=TensorFlow: Large-scale machine learning on heterogeneous systems |url=http://download.tensorflow.org/paper/whitepaper2015.pdf |website=TensorFlow.org |publisher=Google Research |access-date=10 November 2015 |date=9 November 2015 |archive-date=20 November 2015 |archive-url=https://web.archive.org/web/20151120004649/http://download.tensorflow.org/paper/whitepaper2015.pdf |url-status=live}}</ref><ref>{{cite web |last1=Piatetsky |first1=Gregory |title=Python eats away at R: Top Software for Analytics, Data Science, Machine Learning in 2018: Trends and Analysis |url=https://www.kdnuggets.com/2018/05/poll-tools-analytics-data-science-machine-learning-results.html/2 |website=KDnuggets |access-date=30 May 2018 |archive-date=15 November 2019 |archive-url=https://web.archive.org/web/20191115234216/https://www.kdnuggets.com/2018/05/poll-tools-analytics-data-science-machine-learning-results.html/2 |url-status=live}}</ref><ref>{{cite web|url=https://scikit-learn.org/stable/testimonials/testimonials.html|title=Who is using scikit-learn? – scikit-learn 0.20.1 documentation|website=scikit-learn.org|access-date=30 November 2018|archive-date=6 May 2020|archive-url=https://web.archive.org/web/20200506210716/https://scikit-learn.org/stable/testimonials/testimonials.html|url-status=live}}</ref><ref>{{cite web |author-link1=Norman Jouppi |last1=Jouppi |first1=Norm |title=Google supercharges machine learning tasks with TPU custom chip |url=https://cloudplatform.googleblog.com/2016/05/Google-supercharges-machine-learning-tasks-with-custom-chip.html |website=Google Cloud Platform Blog |access-date=19 May 2016 |archive-date=18 May 2016 |archive-url=https://web.archive.org/web/20160518201516/https://cloudplatform.googleblog.com/2016/05/Google-supercharges-machine-learning-tasks-with-custom-chip.html |url-status=live}}</ref><ref name="ProbLogConcepts">{{cite journal |last1=De Raedt |first1=Luc |last2=Kimmig|first2=Angelika |title=Probabilistic (logic) programming concepts |journal=Machine Learning |date=2015 |volume=100 |number=1 |pages=5–47 |doi=10.1007/s10994-015-5494-z |s2cid=3166992 |doi-access=free}}</ref> As a scripting language with a [[modular programming|modular architecture]], simple syntax, and rich text processing tools, Python is often used for [[natural language processing]].<ref name="AutoNT-47"/>
 
The combination of Python and [[Prolog]] has proven useful for AI applications, with Prolog providing knowledge representation and reasoning capabilities. The Janus system, in particular, exploits similarities between these two languages, in part because of their dynamic typing and their simple, recursive data structures. This combination is typically applied natural language processing, visual query answering, geospatial reasoning, and handling semantic web data.<ref>Andersen, C. and Swift, T., 2023. The Janus System: a bridge to new prolog applications. In Prolog: The Next 50 Years (pp. 93–104). Cham: Springer Nature Switzerland.</ref><ref>{{Cite web |title=SWI-Prolog Python interface |url=https://www.swi-prolog.org/pldoc/doc_for?object=section(%27packages/janus.html%27) |access-date=2024-03-15 |language=en-US |archive-date=15 March 2024 |archive-url=https://web.archive.org/web/20240315162046/https://www.swi-prolog.org/pldoc/doc_for?object=section%28%27packages%2Fjanus.html%27%29 |url-status=live}}</ref>
The Natlog system, implemented in Python, uses [[Definite clause grammar|Definite Clause Grammars]] (DCGs) to create prompts for two types of generators: text-to-text generators such as GPT3, and text-to-image generators such as DALL-E or Stable Diffusion.<ref>Tarau, P., 2023. Reflections on automation, learnability and expressiveness in logic-based programming languages. In Prolog: The Next 50 Years (pp. 359–371). Cham: Springer Nature Switzerland.</ref>
 
Python can be used for graphical user interfaces (GUIs), by using libraries such as [[Tkinter]].<ref>{{cite web |url=https://docs.python.org/3/library/tkinter.html |title=Tkinter — Python interface to TCL/Tk |access-date=9 June 2023 |archive-date=18 October 2012 |archive-url=https://web.archive.org/web/20121018043136/http://docs.python.org/library/tkinter.html |url-status=live}}</ref> Similarly, for the [[One Laptop per Child]] XO computer, most of the [[Sugar (software)|Sugar]] desktop environment is written in Python (as of 2008).<ref>{{cite web |url=https://www.geeksforgeeks.org/python-tkinter-tutorial/ |title=Python Tkinter Tutorial |date=3 June 2020 |access-date=9 June 2023 |archive-date=9 June 2023 |archive-url=https://web.archive.org/web/20230609031631/https://www.geeksforgeeks.org/python-tkinter-tutorial/ |url-status=live}}</ref>
 
Python is embedded in many software products (and some hardware products) as a scripting language. These products include the following:
 
* [[finite element method]] software such as [[Abaqus]],
* 3D parametric modelers such as [[FreeCAD]],
* 3D animation packages such as [[3ds Max]], [[Blender (software)|Blender]], [[Cinema 4D]], [[LightWave 3D|Lightwave]], [[Houdini (software)|Houdini]], [[Maya (software)|Maya]], [[modo (software)|modo]], [[MotionBuilder]], [[Autodesk Softimage|Softimage]],
* the visual effects compositor [[Nuke (software)|Nuke]],
* 2D imaging programs such as [[GIMP]],<ref>{{cite web |url=http://gimp-win.sourceforge.net/faq.html |title=Installers for GIMP for Windows – Frequently Asked Questions |author=<!-- Staff writer(s); no by-line. --> |date=26 July 2013 |access-date=26 July 2013 |url-status=dead |archive-url=https://web.archive.org/web/20130717070814/http://gimp-win.sourceforge.net/faq.html |archive-date=17 July 2013}}</ref> [[Inkscape]], [[Scribus]] and [[Paint Shop Pro]],<ref name="AutoNT-38" /> and
* [[musical notation]] programs such as [[scorewriter]] and [[Capella (notation program)|capella]].
 
Similarly, [[GNU Debugger]] uses Python as a [[pretty printer]] to show complex structures such as C++ containers. [[Esri]] promotes Python as the best choice for writing scripts in [[ArcGIS]].<ref name="AutoNT-39" /> Python has also been used in several video games,<ref name="AutoNT-40" /><ref name="AutoNT-41" /> and it has been adopted as first of the three [[programming language]]s available in [[Google App Engine]] (the other two being [[Java (software platform)|Java]] and [[Go (programming language)|Go]]).<ref name="AutoNT-42" /> [[LibreOffice]] includes Python, and its developers plan to replace Java with Python; LibreOffice's Python Scripting Provider is a core feature<ref>{{cite web |year=2013 |title=4.0 New Features and Fixes |url=http://www.libreoffice.org/download/4-0-new-features-and-fixes/ |url-status=live |archive-url=https://web.archive.org/web/20140209184807/http://www.libreoffice.org/download/4-0-new-features-and-fixes/ |archive-date=9 February 2014 |access-date=25 February 2013 |work=LibreOffice.org |publisher=[[The Document Foundation]]}}</ref> since version 4.0 (from 7 February 2013).
 
Among hardware products, the [[Raspberry Pi]] [[single-board computer]] project has adopted Python as its main user-programming language.
 
Many operating systems include Python as a standard component. Python ships with most [[Linux distribution]]s,<ref>{{Cite web|url=https://docs.python.org/3/using/unix.html|title=Python Setup and Usage|publisher=Python Software Foundation|access-date=10 January 2020|archive-date=17 June 2020|archive-url=https://web.archive.org/web/20200617143505/https://docs.python.org/3/using/unix.html|url-status=live}}</ref> [[AmigaOS 4]] (using Python&nbsp;2.7), [[FreeBSD]] (as a package), [[NetBSD]], and [[OpenBSD]] (as a package); it can be used from the command line (terminal). Many Linux distributions use installers written in Python: [[Ubuntu]] uses the [[Ubiquity (software)|Ubiquity]] installer, while [[Red Hat Linux]] and [[Fedora Linux]] use the [[Anaconda (installer)|Anaconda]] installer. [[Gentoo Linux]] uses Python in its [[package management system]], [[Portage (software)|Portage]].<ref name="AutoNT-51" />
 
Python is used extensively in the information security industry, including in exploit development.<ref name="AutoNT-49" /><ref name="AutoNT-50" />  


==Languages influenced by Python==
==Languages influenced by Python==
Python's design and philosophy have influenced many other programming languages:
* [[Cobra (programming language)|Cobra]] has an ''Acknowledgements'' document that lists Python first among influencing languages.<ref>{{cite web |url=http://cobra-language.com/docs/acknowledgements/ |title=Acknowledgements |last=Esterbrook |first=Charles |work=cobra-language.com |publisher=Cobra Language |access-date=7 April 2010 |archive-date=8 February 2008 |archive-url=https://web.archive.org/web/20080208141002/http://cobra-language.com/docs/acknowledgements/ |url-status=dead}}</ref>
* [[Boo (programming language)|Boo]] uses indentation, a similar syntax, and a similar object model.<ref name="AutoNT-90"/>
* [[ECMAScript]] and [[JavaScript]] borrowed iterators and [[generator (computer science)|generators]] from Python.<ref>{{cite web |url=http://wiki.ecmascript.org/doku.php?id=proposals:iterators_and_generators |archive-url=https://web.archive.org/web/20071020082650/http://wiki.ecmascript.org/doku.php?id=proposals:iterators_and_generators |url-status=dead |archive-date=20 October 2007 |title=Proposals: iterators and generators [ES4 Wiki&#93; |publisher=wiki.ecmascript.org |access-date=24 November 2008}}</ref>
* [[Cobra (programming language)|Cobra]] uses indentation and a similar syntax; its ''Acknowledgements'' document lists Python first among influencing languages.<ref name="AutoNT-91"/>
* [[Go (programming language)|Go]] is designed for "speed of working in a dynamic language like Python".<ref>{{cite news |url=https://techcrunch.com/2009/11/10/google-go-language/ |title=Google's Go: A New Programming Language That's Python Meets C++ |last=Kincaid |first=Jason |date=10 November 2009 |work=TechCrunch |access-date=29 January 2010 |archive-date=18 January 2010 |archive-url=https://web.archive.org/web/20100118014358/http://www.techcrunch.com/2009/11/10/google-go-language/ |url-status=live}}</ref>
* [[CoffeeScript]], a programming language that cross-compiles to JavaScript, has a Python-inspired syntax.
* [[Julia (programming language)|Julia]] was designed to be "as usable for general programming as Python".<ref>{{cite web |title= Why We Created Julia |date= February 2012 |website= Julia website |url= https://julialang.org/blog/2012/02/why-we-created-julia |access-date= 5 June 2014 |quote= We want something as usable for general programming as Python [...] |archive-date= 2 May 2020 |archive-url= https://web.archive.org/web/20200502144010/https://julialang.org/blog/2012/02/why-we-created-julia/ |url-status= live}}</ref>
* [[ECMAScript]][[JavaScript]] borrowed iterators and [[generator (computer science)|generators]] from Python.<ref name="AutoNT-93"/>
* [[Mojo (programming language)|Mojo]] is almost<ref name="Mojo"/><ref>{{Cite web |title=Modular Docs – Why Mojo |url=https://docs.modular.com/mojo/why-mojo.html |access-date=2023-05-05 |website=docs.modular.com |language=en |quote=Mojo as a member of the Python family [..] Embracing Python massively simplifies our design efforts, because most of the syntax is already specified.  [..] we decided that the right long-term goal for Mojo is to provide a superset of Python (i.e. be compatible with existing programs) and to embrace the CPython immediately for long-tail ecosystem enablement. To a Python programmer, we expect and hope that Mojo will be immediately familiar, while also providing new tools for developing systems-level code that enable you to do things that Python falls back to C and C++ for. |archive-date=5 May 2023 |archive-url=https://web.archive.org/web/20230505083518/https://docs.modular.com/mojo/why-mojo.html |url-status=live}}</ref> a superset of Python.<ref>{{Cite web |last=Spencer |first=Michael |title=What is Mojo Programming Language? |url=https://datasciencelearningcenter.substack.com/p/what-is-mojo-programming-language |access-date=2023-05-05 |website=datasciencelearningcenter.substack.com |date=4 May 2023 |language=en |archive-date=5 May 2023 |archive-url=https://web.archive.org/web/20230505090408/https://datasciencelearningcenter.substack.com/p/what-is-mojo-programming-language |url-status=live}}</ref>
* [[GDScript]], a Python-like scripting language that is built in to the [[Godot (game engine)|Godot]] game engine.<ref>{{Cite web|url=https://docs.godotengine.org/en/stable/about/faq.html|title=Frequently asked questions|website=Godot Engine documentation|access-date=10 May 2021|archive-date=28 April 2021|archive-url=https://web.archive.org/web/20210428053339/https://docs.godotengine.org/en/stable/about/faq.html|url-status=live}}</ref>
* [[GDScript]] is strongly influenced by Python. {{cn|date=November 2025}}
* [[Go (programming language)|Go]] is designed for "speed of working in a dynamic language like Python";<ref name="AutoNT-94"/> Go shares Python's syntax for slicing arrays.
* [[Apache Groovy| Groovy]], [[Boo (programming language)|Boo]], [[CoffeeScript]], [[F Sharp (programming language)|F#]], [[Nim (programming language)|Nim]], [[Ring (programming language)|Ring]],<ref name="The Ring programming language and other languages"></ref> [[Ruby (programming language)|Ruby]],<ref name="bini"></ref> [[Swift (programming language)|Swift]],<ref name="lattner2014"></ref> and [[V (programming language)|V]]<ref name="vpeople"></ref> have been influenced, as well.
* [[Groovy (programming language)|Groovy]] was motivated by a desire to incorporate the Python design philosophy into [[Java (programming language)|Java]].<ref name="AutoNT-95"/>
* [[Julia (programming language)|Julia]] was designed to be "as usable for general programming as Python".<ref name=Julia>{{cite web |title= Why We Created Julia |date= February 2012 |website= Julia website |url= https://julialang.org/blog/2012/02/why-we-created-julia |access-date= 5 June 2014 |quote= We want something as usable for general programming as Python [...] |archive-date= 2 May 2020 |archive-url= https://web.archive.org/web/20200502144010/https://julialang.org/blog/2012/02/why-we-created-julia/ |url-status= live}}</ref>
* [[Mojo (programming language)|Mojo]] is a non-strict<ref name="Mojo"/><ref>{{Cite web |title=Modular Docs – Why Mojo |url=https://docs.modular.com/mojo/why-mojo.html |access-date=2023-05-05 |website=docs.modular.com |language=en |quote=Mojo as a member of the Python family [..] Embracing Python massively simplifies our design efforts, because most of the syntax is already specified.  [..] we decided that the right long-term goal for Mojo is to provide a superset of Python (i.e. be compatible with existing programs) and to embrace the CPython immediately for long-tail ecosystem enablement. To a Python programmer, we expect and hope that Mojo will be immediately familiar, while also providing new tools for developing systems-level code that enable you to do things that Python falls back to C and C++ for. |archive-date=5 May 2023 |archive-url=https://web.archive.org/web/20230505083518/https://docs.modular.com/mojo/why-mojo.html |url-status=live}}</ref> superset of Python (e.g., omitting classes, and adding [[struct]]).<ref>{{Cite web |last=Spencer |first=Michael |title=What is Mojo Programming Language? |url=https://datasciencelearningcenter.substack.com/p/what-is-mojo-programming-language |access-date=2023-05-05 |website=datasciencelearningcenter.substack.com |date=4 May 2023 |language=en |archive-date=5 May 2023 |archive-url=https://web.archive.org/web/20230505090408/https://datasciencelearningcenter.substack.com/p/what-is-mojo-programming-language |url-status=live}}</ref>
* [[Nim (programming language)|Nim]] uses indentation and a similar syntax.<ref>{{cite web |url=https://www.infoworld.com/article/3157745/application-development/nim-language-draws-from-best-of-python-rust-go-and-lisp.html |title=Nim language draws from best of Python, Rust, Go, and Lisp |first=Serdar |last=Yegulalp |date=16 January 2017 |website=InfoWorld |quote=Nim's syntax is strongly reminiscent of Python's, as it uses indented code blocks and some of the same syntax (such as the way if/elif/then/else blocks are constructed). |access-date=7 June 2020 |archive-date=13 October 2018 |archive-url=https://web.archive.org/web/20181013211847/https://www.infoworld.com/article/3157745/application-development/nim-language-draws-from-best-of-python-rust-go-and-lisp.html |url-status=live}}</ref>
* [[Ruby (programming language)|Ruby]]'s creator, [[Yukihiro Matsumoto]], said that "I wanted a scripting language that was more powerful than Perl, and more object-oriented than Python. That's why I decided to design my own language."<ref name="linuxdevcenter"/>
* [[Swift (programming language)|Swift]], a programming language developed by Apple, has some Python-inspired syntax.<ref>{{cite web |url=http://nondot.org/sabre |title=Chris Lattner's Homepage |publisher=Chris Lattner |first=Chris |last=Lattner |author-link=Chris Lattner |date=3 June 2014 |access-date=3 June 2014 |quote=I started work on the Swift Programming Language in July of 2010. I implemented much of the basic language structure, with only a few people knowing of its existence. A few other (amazing) people started contributing in earnest late in 2011, and it became a major focus for the Apple Developer Tools group in July 2013 [...] drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list. |archive-date=22 December 2015 |archive-url=https://web.archive.org/web/20151222150510/http://nondot.org/sabre/ |url-status=live}}</ref>
* [[Kotlin (programming language)|Kotlin]] blends Python and Java features, which minimizes boilerplate code and enhances developer efficiency.<ref>{{Cite web |last=Jalan |first=Nishant Aanjaney |date=2022-11-10 |title=Programming in Kotlin |url=https://medium.com/codex/programming-in-kotlin-934bdb3659cf |access-date=2024-04-29 |website=CodeX |language=en}}</ref>
 
Python's development practices have also been emulated by other languages. For example, Python requires a document that describes the rationale and context for any language change; this document is known as a ''Python Enhancement Proposal'' or PEP. This practice is also used by the developers of [[Tcl]],<ref name="AutoNT-99"/> [[Erlang (programming language)|Erlang]],<ref name="AutoNT-100"/> and Swift.<ref>{{cite web |title=Swift Evolution Process |date=18 February 2020 |website=Swift Programming Language Evolution repository on GitHub |url=https://github.com/apple/swift-evolution/blob/master/process.md |access-date=27 April 2020 |archive-date=27 April 2020 |archive-url=https://web.archive.org/web/20200427182556/https://github.com/apple/swift-evolution/blob/master/process.md |url-status=live}}</ref>


==See also==
==See also==
{{Portal|Computer programming|Free and open-source software}}
{{Portal|Computer programming|Free and open-source software}}
* [[Python syntax and semantics]]
* [[List of computer books#Python|List of Python programming books]]
* [[pip (package manager)]]
* [[pip (package manager)]]
* [[List of programming languages]]
* [[Pydoc]]
* [[History of programming languages]]
* [[NumPy]]
* [[Comparison of programming languages]]
* [[SciPy]]
* [[Jupyter]]
* [[Pytorch]]
* [[Cython]]
* [[CPython]]
* [[Mojo (programming language)|Mojo]]
* [[Pygame]]
* [[PyQt]]
* [[PyGTK]]
* [[PyPy]]
* [[PyCon]]
* [[Google Colab]]{{snd}} zero setup [[Online integrated development environment|online IDE]] that runs Python


{{Clear}}
{{Clear}}
Line 624: Line 482:
<ref name="faq-created">{{cite web |url=https://docs.python.org/faq/general.html#why-was-python-created-in-the-first-place |title=Why was Python created in the first place? |work=General Python FAQ |publisher=Python Software Foundation |access-date=22 March 2007 |archive-date=24 October 2012 |archive-url=https://web.archive.org/web/20121024164224/http://docs.python.org/faq/general.html#why-was-python-created-in-the-first-place |url-status=live |quote=I had extensive experience with implementing an interpreted language in the ABC group at CWI, and from working with this group I had learned a lot about language design. This is the origin of many Python features, including the use of indentation for statement grouping and the inclusion of very high-level data types (although the details are all different in Python).}}</ref>
<ref name="faq-created">{{cite web |url=https://docs.python.org/faq/general.html#why-was-python-created-in-the-first-place |title=Why was Python created in the first place? |work=General Python FAQ |publisher=Python Software Foundation |access-date=22 March 2007 |archive-date=24 October 2012 |archive-url=https://web.archive.org/web/20121024164224/http://docs.python.org/faq/general.html#why-was-python-created-in-the-first-place |url-status=live |quote=I had extensive experience with implementing an interpreted language in the ABC group at CWI, and from working with this group I had learned a lot about language design. This is the origin of many Python features, including the use of indentation for statement grouping and the inclusion of very high-level data types (although the details are all different in Python).}}</ref>


<ref name="98-interview">{{cite web |url=http://www.amk.ca/python/writing/gvr-interview |title=Interview with Guido van Rossum (July 1998) |last=Kuchling |first=Andrew M. |work=amk.ca |date=22 December 2006 |access-date=12 March 2012 |url-status=dead |archive-url=https://web.archive.org/web/20070501105422/http://www.amk.ca/python/writing/gvr-interview |archive-date=1 May 2007 |quote=I'd spent a summer at DEC's Systems Research Center, which introduced me to Modula-2+; the Modula-3 final report was being written there at about the same time. What I learned there later showed up in Python's exception handling, modules, and the fact that methods explicitly contain 'self' in their parameter list. String slicing came from Algol-68 and Icon.}}</ref>
<ref name="98-interview">{{cite web |url=http://www.amk.ca/python/writing/gvr-interview |title=Interview with Guido van Rossum (July 1998) |last=Kuchling |first=Andrew M. |work=amk.ca |date=22 December 2006 |access-date=12 March 2012 |archive-url=https://web.archive.org/web/20070501105422/http://www.amk.ca/python/writing/gvr-interview |archive-date=1 May 2007 |quote=I'd spent a summer at DEC's Systems Research Center, which introduced me to Modula-2+; the Modula-3 final report was being written there at about the same time. What I learned there later showed up in Python's exception handling, modules, and the fact that methods explicitly contain 'self' in their parameter list. String slicing came from Algol-68 and Icon.}}</ref>


<ref name="AutoNT-1">{{cite journal |last=van Rossum |first=Guido |year=1993 |title=An Introduction to Python for UNIX/C Programmers |journal=Proceedings of the NLUUG Najaarsconferentie (Dutch UNIX Users Group) |quote=even though the design of C is far from ideal, its influence on Python is considerable. |citeseerx=10.1.1.38.2023}}</ref>
<ref name="AutoNT-1">{{cite journal |last=van Rossum |first=Guido |year=1993 |title=An Introduction to Python for UNIX/C Programmers |journal=Proceedings of the NLUUG Najaarsconferentie (Dutch UNIX Users Group) |quote=even though the design of C is far from ideal, its influence on Python is considerable. |citeseerx=10.1.1.38.2023}}</ref>
Line 644: Line 502:
<ref name="bini">{{cite book |last=Bini |first=Ola |title=Practical JRuby on Rails Web 2.0 Projects: bringing Ruby on Rails to the Java platform |year=2007 |publisher=APress |location=Berkeley |isbn=978-1-59059-881-8 |page=[https://archive.org/details/practicaljrubyon0000bini/page/3 3] |url-access=registration |url=https://archive.org/details/practicaljrubyon0000bini/page/3}}</ref>
<ref name="bini">{{cite book |last=Bini |first=Ola |title=Practical JRuby on Rails Web 2.0 Projects: bringing Ruby on Rails to the Java platform |year=2007 |publisher=APress |location=Berkeley |isbn=978-1-59059-881-8 |page=[https://archive.org/details/practicaljrubyon0000bini/page/3 3] |url-access=registration |url=https://archive.org/details/practicaljrubyon0000bini/page/3}}</ref>


<ref name="AutoNT-7">{{cite web |last=Kuhlman |first=Dave |url=https://www.davekuhlman.org/python_book_01.pdf|title=A Python Book: Beginning Python, Advanced Python, and Python Exercises |at=Section 1.1|url-status=dead |archive-url=https://web.archive.org/web/20120623165941/http://cutter.rexx.com/~dkuhlman/python_book_01.html |archive-date=23 June 2012}}</ref>
<ref name="AutoNT-7">{{cite web |last=Kuhlman |first=Dave |url=https://www.davekuhlman.org/python_book_01.pdf|title=A Python Book: Beginning Python, Advanced Python, and Python Exercises |at=Section 1.1|archive-url=https://web.archive.org/web/20120623165941/http://cutter.rexx.com/~dkuhlman/python_book_01.html |archive-date=23 June 2012}}</ref>
 
<ref name="About">{{cite web |url=https://www.python.org/about |title=About Python |publisher=Python Software Foundation |access-date=24 April 2012 |archive-date=20 April 2012 |archive-url=https://web.archive.org/web/20120420010049/http://www.python.org/about/ |url-status=live}}, second section "Fans of Python use the phrase "batteries included" to describe the standard library, which covers everything from asynchronous processing to zip files."</ref>


<ref name="venners-interview-pt-1">{{cite web |url=http://www.artima.com/intv/pythonP.html |title=The Making of Python |last=Venners |first=Bill |date=13 January 2003 |work=Artima Developer |publisher=Artima |access-date=22 March 2007 |archive-date=1 September 2016 |archive-url=https://web.archive.org/web/20160901183332/http://www.artima.com/intv/pythonP.html |url-status=live}}</ref>
<ref name="venners-interview-pt-1">{{cite web |url=http://www.artima.com/intv/pythonP.html |title=The Making of Python |last=Venners |first=Bill |date=13 January 2003 |work=Artima Developer |publisher=Artima |access-date=22 March 2007 |archive-date=1 September 2016 |archive-url=https://web.archive.org/web/20160901183332/http://www.artima.com/intv/pythonP.html |url-status=live}}</ref>
Line 656: Line 512:
<ref name="newin-2.0">{{cite web |url=https://docs.python.org/whatsnew/2.0.html |title=What's New in Python 2.0 |last1=Kuchling |first1=A. M. |last2=Zadka |first2=Moshe |date=16 October 2000 |publisher=Python Software Foundation |access-date=11 February 2012 |archive-date=23 October 2012 |archive-url=https://web.archive.org/web/20121023112045/http://docs.python.org/whatsnew/2.0.html |url-status=live}}</ref>
<ref name="newin-2.0">{{cite web |url=https://docs.python.org/whatsnew/2.0.html |title=What's New in Python 2.0 |last1=Kuchling |first1=A. M. |last2=Zadka |first2=Moshe |date=16 October 2000 |publisher=Python Software Foundation |access-date=11 February 2012 |archive-date=23 October 2012 |archive-url=https://web.archive.org/web/20121023112045/http://docs.python.org/whatsnew/2.0.html |url-status=live}}</ref>


<ref name="AutoNT-13">{{cite web |url=https://www.python.org/community/pycon/dc2004/papers/24/metaclasses-pycon.pdf |archive-url=https://web.archive.org/web/20090530030205/http://www.python.org/community/pycon/dc2004/papers/24/metaclasses-pycon.pdf |archive-date=30 May 2009 |title=Python Metaclasses: Who? Why? When? |last=The Cain Gang Ltd. |access-date=27 June 2009 |url-status=dead}}</ref>
<ref name="AutoNT-13">{{cite web |url=https://www.python.org/community/pycon/dc2004/papers/24/metaclasses-pycon.pdf |archive-url=https://web.archive.org/web/20090530030205/http://www.python.org/community/pycon/dc2004/papers/24/metaclasses-pycon.pdf |archive-date=30 May 2009 |title=Python Metaclasses: Who? Why? When? |last=The Cain Gang Ltd. |access-date=27 June 2009 }}</ref>


<ref name="AutoNT-14">{{cite web |url=https://docs.python.org/3.0/reference/datamodel.html#special-method-names |title=3.3. Special method names |work=The Python Language Reference |publisher=Python Software Foundation |access-date=27 June 2009 |archive-date=15 December 2018 |archive-url=https://web.archive.org/web/20181215123146/https://docs.python.org/3.0/reference/datamodel.html#special-method-names |url-status=live}}</ref>
<ref name="AutoNT-14">{{cite web |url=https://docs.python.org/3.0/reference/datamodel.html#special-method-names |title=3.3. Special method names |work=The Python Language Reference |publisher=Python Software Foundation |access-date=27 June 2009 |archive-date=15 December 2018 |archive-url=https://web.archive.org/web/20181215123146/https://docs.python.org/3.0/reference/datamodel.html#special-method-names |url-status=live}}</ref>
Line 672: Line 528:
<ref name="AutoNT-19">{{cite book |url=http://shop.oreilly.com/product/9780596007973.do |title=Python Cookbook, 2nd Edition |publisher=[[O'Reilly Media]] |last1=Martelli |first1=Alex |last2=Ravenscroft |first2=Anna |last3=Ascher |first3=David |year=2005 |page=230 |isbn=978-0-596-00797-3 |access-date=14 November 2015 |archive-date=23 February 2020 |archive-url=https://web.archive.org/web/20200223171254/http://shop.oreilly.com/product/9780596007973.do |url-status=live}}</ref>
<ref name="AutoNT-19">{{cite book |url=http://shop.oreilly.com/product/9780596007973.do |title=Python Cookbook, 2nd Edition |publisher=[[O'Reilly Media]] |last1=Martelli |first1=Alex |last2=Ravenscroft |first2=Anna |last3=Ascher |first3=David |year=2005 |page=230 |isbn=978-0-596-00797-3 |access-date=14 November 2015 |archive-date=23 February 2020 |archive-url=https://web.archive.org/web/20200223171254/http://shop.oreilly.com/product/9780596007973.do |url-status=live}}</ref>


<ref name="AutoNT-20">{{cite web |title=Python Culture |website=ebeab |date=January 21, 2014 |url=http://ebeab.com/2014/01/21/python-culture/ |archive-url=https://web.archive.org/web/20140130021902/http://ebeab.com/2014/01/21/python-culture/ |archive-date=January 30, 2014 |url-status=dead}}</ref>
<ref name="AutoNT-20">{{cite web |title=Python Culture |website=ebeab |date=January 21, 2014 |url=http://ebeab.com/2014/01/21/python-culture/ |archive-url=https://web.archive.org/web/20140130021902/http://ebeab.com/2014/01/21/python-culture/ |archive-date=January 30, 2014 }}</ref>


<ref name="PepCite000">{{cite web |url=https://www.python.org/dev/peps/pep-0001/ |title=PEP 1&nbsp;– PEP Purpose and Guidelines |last1=Warsaw |first1=Barry |last2=Hylton |first2=Jeremy |last3=Goodger |first3=David |date=13 June 2000 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=19 April 2011 |archive-date=6 June 2020 |archive-url=https://web.archive.org/web/20200606042011/https://www.python.org/dev/peps/pep-0001/ |url-status=live}}</ref>
<ref name="PepCite000">{{cite web |url=https://www.python.org/dev/peps/pep-0001/ |title=PEP 1&nbsp;– PEP Purpose and Guidelines |last1=Warsaw |first1=Barry |last2=Hylton |first2=Jeremy |last3=Goodger |first3=David |date=13 June 2000 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=19 April 2011 |archive-date=6 June 2020 |archive-url=https://web.archive.org/web/20200606042011/https://www.python.org/dev/peps/pep-0001/ |url-status=live}}</ref>


<ref name="AutoNT-21">{{cite web |url=https://www.python.org/dev/intro/ |title=Guido, Some Guys, and a Mailing List: How Python is Developed |last=Cannon |first=Brett |work=python.org |publisher=Python Software Foundation |access-date=27 June 2009 |url-status=dead |archive-url=https://web.archive.org/web/20090601134342/http://www.python.org/dev/intro/ |archive-date=1 June 2009}}</ref>
<ref name="AutoNT-21">{{cite web |url=https://www.python.org/dev/intro/ |title=Guido, Some Guys, and a Mailing List: How Python is Developed |last=Cannon |first=Brett |work=python.org |publisher=Python Software Foundation |access-date=27 June 2009 |archive-url=https://web.archive.org/web/20090601134342/http://www.python.org/dev/intro/ |archive-date=1 June 2009}}</ref>


<ref name="release-schedule">{{cite web |url=https://mail.python.org/pipermail/python-dev/2002-April/022739.html |title=&#91;Python-Dev&#93; Release Schedules (was Stability & change) |last=Norwitz |first=Neal |date=8 April 2002 |access-date=27 June 2009 |archive-date=15 December 2018 |archive-url=https://web.archive.org/web/20181215122750/https://mail.python.org/pipermail/python-dev/2002-April/022739.html |url-status=live}}</ref>
<ref name="release-schedule">{{cite web |url=https://mail.python.org/pipermail/python-dev/2002-April/022739.html |title=&#91;Python-Dev&#93; Release Schedules (was Stability & change) |last=Norwitz |first=Neal |date=8 April 2002 |access-date=27 June 2009 |archive-date=15 December 2018 |archive-url=https://web.archive.org/web/20181215122750/https://mail.python.org/pipermail/python-dev/2002-April/022739.html |url-status=live}}</ref>
Line 689: Line 545:


<ref name="AutoNT-26">{{cite web |url=https://stackoverflow.com/questions/5033906/in-python-should-i-use-else-after-a-return-in-an-if-block |title=In Python, should I use else after a return in an if block? |date=17 February 2011 |work=[[Stack Overflow]] |publisher=Stack Exchange |access-date=6 May 2011 |archive-date=20 June 2019 |archive-url=https://web.archive.org/web/20190620000050/https://stackoverflow.com/questions/5033906/in-python-should-i-use-else-after-a-return-in-an-if-block |url-status=live}}</ref>
<ref name="AutoNT-26">{{cite web |url=https://stackoverflow.com/questions/5033906/in-python-should-i-use-else-after-a-return-in-an-if-block |title=In Python, should I use else after a return in an if block? |date=17 February 2011 |work=[[Stack Overflow]] |publisher=Stack Exchange |access-date=6 May 2011 |archive-date=20 June 2019 |archive-url=https://web.archive.org/web/20190620000050/https://stackoverflow.com/questions/5033906/in-python-should-i-use-else-after-a-return-in-an-if-block |url-status=live}}</ref>
<ref name="quotes-about-python">{{cite web |url=https://www.python.org/about/quotes/ |title=Quotes about Python |publisher=Python Software Foundation |access-date=8 January 2012 |archive-date=3 June 2020 |archive-url=https://web.archive.org/web/20200603135201/https://www.python.org/about/quotes/ |url-status=live}}</ref>
<ref name="AutoNT-29">{{cite web |url=https://wiki.python.org/moin/OrganizationsUsingPython |title=Organizations Using Python |publisher=Python Software Foundation |access-date=15 January 2009 |archive-date=21 August 2018 |archive-url=https://web.archive.org/web/20180821075931/https://wiki.python.org/moin/OrganizationsUsingPython |url-status=live}}</ref>
<ref name="AutoNT-30">{{cite journal |title=Python : the holy grail of programming |journal=CERN Bulletin |issue=31/2006 |publisher=CERN Publications |date=31 July 2006 |url=http://cdsweb.cern.ch/journal/CERNBulletin/2006/31/News%20Articles/974627?ln=en |access-date=11 February 2012 |archive-date=15 January 2013 |archive-url=https://archive.today/20130115191843/http://cdsweb.cern.ch/journal/CERNBulletin/2006/31/News%20Articles/974627?ln=en |url-status=live}}</ref>
<ref name="AutoNT-31">{{cite web |url=https://www.python.org/about/success/usa/ |title=Python Streamlines Space Shuttle Mission Design |last=Shafer |first=Daniel G. |date=17 January 2003 |publisher=Python Software Foundation |access-date=24 November 2008 |archive-date=5 June 2020 |archive-url=https://web.archive.org/web/20200605093424/https://www.python.org/about/success/usa/ |url-status=live}}</ref>
<ref name="AutoNT-32">{{cite web |url=https://www.python.org/about/success/ilm/ |title=Industrial Light & Magic Runs on Python |last=Fortenberry |first=Tim |date=17 January 2003 |publisher=Python Software Foundation |access-date=11 February 2012 |archive-date=6 June 2020 |archive-url=https://web.archive.org/web/20200606042020/https://www.python.org/about/success/ilm/ |url-status=live}}</ref>
<ref name="AutoNT-33">{{cite web |url=http://www.eweek.com/c/a/Application-Development/Python-Slithers-into-Systems/ |title=Python Slithers into Systems |last=Taft |first=Darryl K. |date=5 March 2007 |work=eWeek.com |publisher=Ziff Davis Holdings |access-date=24 September 2011 |archive-date=13 August 2021 |archive-url=https://web.archive.org/web/20210813194304/https://www.eweek.com/development/python-slithers-into-systems/ |url-status=live}}</ref>
<ref name="AutoNT-35">{{cite web |title=Usage statistics and market share of Python for websites |year=2012 |url=http://w3techs.com/technologies/details/pl-python/all/all |access-date=18 December 2012 |archive-date=13 August 2021 |archive-url=https://web.archive.org/web/20210813194305/https://w3techs.com/technologies/details/pl-python |url-status=live}}</ref>
<ref name="AutoNT-38">{{cite web |url=http://www.jasc.com/support/customercare/articles/psp9components.asp |title=jasc psp9components |url-status=dead |archive-url=https://web.archive.org/web/20080319061519/http://www.jasc.com/support/customercare/articles/psp9components.asp |archive-date=19 March 2008}}</ref>
<ref name="AutoNT-39">{{cite web |url=http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=About_getting_started_with_writing_geoprocessing_scripts |title=About getting started with writing geoprocessing scripts |date=17 November 2006 |work=ArcGIS Desktop Help 9.2 |publisher=Environmental Systems Research Institute |access-date=11 February 2012 |archive-date=5 June 2020 |archive-url=https://web.archive.org/web/20200605144616/http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=About_getting_started_with_writing_geoprocessing_scripts |url-status=live}}</ref>
<ref name="AutoNT-40">{{cite web |url=http://community.eveonline.com/news/dev-blogs/stackless-python-2.7/ |title=Stackless Python 2.7 |publisher=[[CCP Games]] |date=24 August 2010 |author=CCP porkbelly |work=EVE Community Dev Blogs |quote=As you may know, EVE has at its core the programming language known as Stackless Python. |access-date=11 January 2014 |archive-date=11 January 2014 |archive-url=https://web.archive.org/web/20140111155537/http://community.eveonline.com/news/dev-blogs/stackless-python-2.7/ |url-status=live}}</ref>
<ref name="AutoNT-41">{{cite web |url=http://www.2kgames.com/civ4/blog_03.htm |title=Modding Sid Meier's Civilization IV |last=Caudill |first=Barry |date=20 September 2005 |publisher=[[Firaxis Games]] |archive-url=https://web.archive.org/web/20101202164144/http://www.2kgames.com/civ4/blog_03.htm |archive-date=2 December 2010 |work=Sid Meier's Civilization IV Developer Blog |quote=we created three levels of tools ... The next level offers Python and XML support, letting modders with more experience manipulate the game world and everything in it. |url-status=dead}}</ref>
<ref name="AutoNT-42">{{cite web |url=https://code.google.com/apis/documents/docs/1.0/developers_guide_python.html |title=Python Language Guide (v1.0) |work=Google Documents List Data API v1.0 |archive-url=https://web.archive.org/web/20100715145616/http://code.google.com/apis/documents/docs/1.0/developers_guide_python.html |archive-date=15 July 2010 |url-status=dead}}</ref>
<ref name="AutoNT-47">{{Cite web|url=http://www.nltk.org/|title=Natural Language Toolkit – NLTK 3.5b1 documentation|website=www.nltk.org|access-date=10 April 2020|archive-date=13 June 2020|archive-url=https://web.archive.org/web/20200613003911/http://www.nltk.org/|url-status=live}}</ref>
<ref name="AutoNT-49">{{cite web |url=http://www.immunitysec.com/products-immdbg.shtml |title=Immunity: Knowing You're Secure |url-status=usurped |archive-url=https://web.archive.org/web/20090216134332/http://immunitysec.com/products-immdbg.shtml |archive-date=16 February 2009}}</ref>
<ref name="AutoNT-50">{{Cite web|url=https://www.coresecurity.com/|title=Core Security|website=Core Security|access-date=10 April 2020|archive-date=9 June 2020|archive-url=https://web.archive.org/web/20200609165041/http://www.coresecurity.com/|url-status=live}}</ref>
<ref name="AutoNT-51">{{cite web |url=http://sugarlabs.org/go/Sugar |title=What is Sugar? |publisher=Sugar Labs |access-date=11 February 2012 |archive-date=9 January 2009 |archive-url=https://web.archive.org/web/20090109025944/http://sugarlabs.org/go/Sugar |url-status=live}}</ref>


<ref name="AutoNT-52">{{cite web |title=Is Python a good language for beginning programmers? |url=https://docs.python.org/faq/general.html#is-python-a-good-language-for-beginning-programmers |work=General Python FAQ |publisher=Python Software Foundation |access-date=21 March 2007 |archive-date=24 October 2012 |archive-url=https://web.archive.org/web/20121024164224/http://docs.python.org/faq/general.html#is-python-a-good-language-for-beginning-programmers |url-status=live}}</ref>
<ref name="AutoNT-52">{{cite web |title=Is Python a good language for beginning programmers? |url=https://docs.python.org/faq/general.html#is-python-a-good-language-for-beginning-programmers |work=General Python FAQ |publisher=Python Software Foundation |access-date=21 March 2007 |archive-date=24 October 2012 |archive-url=https://web.archive.org/web/20121024164224/http://docs.python.org/faq/general.html#is-python-a-good-language-for-beginning-programmers |url-status=live}}</ref>


<ref name="AutoNT-53">{{cite web |url=http://www.secnetix.de/~olli/Python/block_indentation.hawk |title=Myths about indentation in Python |publisher=Secnetix.de |access-date=19 April 2011 |archive-date=18 February 2018 |archive-url=https://web.archive.org/web/20180218162410/http://www.secnetix.de/~olli/Python/block_indentation.hawk |url-status=dead}}</ref>
<ref name="AutoNT-53">{{cite web |url=http://www.secnetix.de/~olli/Python/block_indentation.hawk |title=Myths about indentation in Python |publisher=Secnetix.de |access-date=19 April 2011 |archive-date=18 February 2018 |archive-url=https://web.archive.org/web/20180218162410/http://www.secnetix.de/~olli/Python/block_indentation.hawk }}</ref>
 
<!--ref name="AutoNT-54">{{cite web |url=http://c2.com/cgi/wiki?PythonWhiteSpaceDiscussion |title=White Space Discussion |access-date=1 January 2013}}</ref-->


<ref name="AutoNT-55">{{cite web |last=van Rossum |first=Guido |url=http://neopythonic.blogspot.be/2009/04/tail-recursion-elimination.html |title=Tail Recursion Elimination |publisher=Neopythonic.blogspot.be |date=22 April 2009 |access-date=3 December 2012 |archive-date=19 May 2018 |archive-url=https://web.archive.org/web/20180519225253/http://neopythonic.blogspot.be/2009/04/tail-recursion-elimination.html |url-status=live}}</ref>
<ref name="AutoNT-55">{{cite web |last=van Rossum |first=Guido |url=http://neopythonic.blogspot.be/2009/04/tail-recursion-elimination.html |title=Tail Recursion Elimination |publisher=Neopythonic.blogspot.be |date=22 April 2009 |access-date=3 December 2012 |archive-date=19 May 2018 |archive-url=https://web.archive.org/web/20180519225253/http://neopythonic.blogspot.be/2009/04/tail-recursion-elimination.html |url-status=live}}</ref>
Line 740: Line 562:
<ref name="AutoNT-60">{{cite web |url=https://www.python.org/dev/peps/pep-0308/ |title=PEP 308&nbsp;– Conditional Expressions |last1=van Rossum |first1=Guido |last2=Hettinger |first2=Raymond |date=7 February 2003 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=13 July 2011 |archive-date=13 March 2016 |archive-url=https://web.archive.org/web/20160313113147/https://www.python.org/dev/peps/pep-0308/ |url-status=live}}</ref>
<ref name="AutoNT-60">{{cite web |url=https://www.python.org/dev/peps/pep-0308/ |title=PEP 308&nbsp;– Conditional Expressions |last1=van Rossum |first1=Guido |last2=Hettinger |first2=Raymond |date=7 February 2003 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=13 July 2011 |archive-date=13 March 2016 |archive-url=https://web.archive.org/web/20160313113147/https://www.python.org/dev/peps/pep-0308/ |url-status=live}}</ref>


<ref name="AutoNT-61">{{cite web |url=https://docs.python.org/faq/design.html#why-must-self-be-used-explicitly-in-method-definitions-and-calls |title=Why must 'self' be used explicitly in method definitions and calls? |work=Design and History FAQ |publisher=Python Software Foundation |access-date=19 February 2012 |archive-date=24 October 2012 |archive-url=https://web.archive.org/web/20121024164243/http://docs.python.org/faq/design.html#why-must-self-be-used-explicitly-in-method-definitions-and-calls |url-status=live}}</ref>
<ref name="classy">{{cite web |title=The Python Language Reference, section 3.3. New-style and classic classes, for release 2.7.1 |access-date=12 January 2011 |url=https://docs.python.org/reference/datamodel.html#new-style-and-classic-classes |archive-date=26 October 2012 |archive-url=https://web.archive.org/web/20121026063834/http://docs.python.org/reference/datamodel.html#new-style-and-classic-classes }}</ref>
 
<ref name="classy">{{cite web |title=The Python Language Reference, section 3.3. New-style and classic classes, for release 2.7.1 |access-date=12 January 2011 |url=https://docs.python.org/reference/datamodel.html#new-style-and-classic-classes |archive-date=26 October 2012 |archive-url=https://web.archive.org/web/20121026063834/http://docs.python.org/reference/datamodel.html#new-style-and-classic-classes |url-status=dead}}</ref>


<ref name="pep0237">{{cite web |url=https://www.python.org/dev/peps/pep-0237/ |title=PEP 237&nbsp;– Unifying Long Integers and Integers |last1=Zadka |first1=Moshe |last2=van Rossum |first2=Guido |date=11 March 2001 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=24 September 2011 |archive-date=28 May 2020 |archive-url=https://web.archive.org/web/20200528063237/https://www.python.org/dev/peps/pep-0237/ |url-status=live}}</ref>
<ref name="pep0237">{{cite web |url=https://www.python.org/dev/peps/pep-0237/ |title=PEP 237&nbsp;– Unifying Long Integers and Integers |last1=Zadka |first1=Moshe |last2=van Rossum |first2=Guido |date=11 March 2001 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=24 September 2011 |archive-date=28 May 2020 |archive-url=https://web.archive.org/web/20200528063237/https://www.python.org/dev/peps/pep-0237/ |url-status=live}}</ref>
Line 752: Line 572:
<ref name="AutoNT-64">{{citation |url=https://docs.python.org/py3k/library/functions.html#round |access-date=14 August 2011 |title=round |work=The Python standard library, release 3.2, §2: Built-in functions |archive-date=25 October 2012 |archive-url=https://web.archive.org/web/20121025141808/http://docs.python.org/py3k/library/functions.html#round |url-status=live}}</ref>
<ref name="AutoNT-64">{{citation |url=https://docs.python.org/py3k/library/functions.html#round |access-date=14 August 2011 |title=round |work=The Python standard library, release 3.2, §2: Built-in functions |archive-date=25 October 2012 |archive-url=https://web.archive.org/web/20121025141808/http://docs.python.org/py3k/library/functions.html#round |url-status=live}}</ref>


<ref name="AutoNT-65">{{cite book |title=Python Essential Reference |url=https://archive.org/details/pythonessentialr00beaz_036 |url-access=limited |first1=David M. |last1=Beazley |edition=4th |year=2009 |page=[https://archive.org/details/pythonessentialr00beaz_036/page/n90 66] |publisher=Addison-Wesley Professional |isbn=9780672329784}}</ref>
<ref name="AutoNT-65">{{cite book |title=Python Essential Reference |url=https://archive.org/details/pythonessentialr00beaz_036 |url-access=limited |first1=David M. |last1=Beazley |edition=4th |year=2009 |page=[https://archive.org/details/pythonessentialr00beaz_036/page/n90 66] |publisher=Addison-Wesley Professional |isbn=978-0-672-32978-4}}</ref>


<ref name="CPL">{{cite book |title=The C Programming Language |first1=Brian W. |last1=Kernighan |first2=Dennis M. |last2=Ritchie |title-link=The C Programming Language |edition=2nd |year=1988 |page=[https://archive.org/details/cprogramminglang00bria/page/206 206]}}</ref>
<ref name="CPL">{{cite book |title=The C Programming Language |first1=Brian W. |last1=Kernighan |first2=Dennis M. |last2=Ritchie |title-link=The C Programming Language |edition=2nd |year=1988 |page=[https://archive.org/details/cprogramminglang00bria/page/206 206]}}</ref>
Line 777: Line 597:


<ref name="AutoNT-89">{{cite web |url=https://www.python.org/dev/peps/pep-0333/ |title=PEP 333&nbsp;– Python Web Server Gateway Interface v1.0 |last=Eby |first=Phillip J. |date=7 December 2003 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=19 February 2012 |archive-date=14 June 2020 |archive-url=https://web.archive.org/web/20200614170344/https://www.python.org/dev/peps/pep-0333/ |url-status=live}}</ref>
<ref name="AutoNT-89">{{cite web |url=https://www.python.org/dev/peps/pep-0333/ |title=PEP 333&nbsp;– Python Web Server Gateway Interface v1.0 |last=Eby |first=Phillip J. |date=7 December 2003 |work=Python Enhancement Proposals |publisher=Python Software Foundation |access-date=19 February 2012 |archive-date=14 June 2020 |archive-url=https://web.archive.org/web/20200614170344/https://www.python.org/dev/peps/pep-0333/ |url-status=live}}</ref>
<ref name="AutoNT-90">{{cite web |url=http://boo.codehaus.org/Gotchas+for+Python+Users |title=Gotchas for Python Users |work=boo.codehaus.org |publisher=Codehaus Foundation |access-date=24 November 2008 |url-status=dead |archive-url=https://web.archive.org/web/20081211062108/http://boo.codehaus.org/Gotchas+for+Python+Users |archive-date=11 December 2008}}</ref>
<ref name="AutoNT-91">{{cite web |url=http://cobra-language.com/docs/acknowledgements/ |title=Acknowledgements |last=Esterbrook |first=Charles |work=cobra-language.com |publisher=Cobra Language |access-date=7 April 2010 |archive-date=8 February 2008 |archive-url=https://web.archive.org/web/20080208141002/http://cobra-language.com/docs/acknowledgements/ |url-status=dead}}</ref>
<ref name="AutoNT-93">{{cite web |url=http://wiki.ecmascript.org/doku.php?id=proposals:iterators_and_generators |archive-url=https://web.archive.org/web/20071020082650/http://wiki.ecmascript.org/doku.php?id=proposals:iterators_and_generators |url-status=dead |archive-date=20 October 2007 |title=Proposals: iterators and generators [ES4 Wiki&#93; |publisher=wiki.ecmascript.org |access-date=24 November 2008}}</ref>
<ref name="AutoNT-94">{{cite news |url=https://techcrunch.com/2009/11/10/google-go-language/ |title=Google's Go: A New Programming Language That's Python Meets C++ |last=Kincaid |first=Jason |date=10 November 2009 |work=TechCrunch |access-date=29 January 2010 |archive-date=18 January 2010 |archive-url=https://web.archive.org/web/20100118014358/http://www.techcrunch.com/2009/11/10/google-go-language/ |url-status=live}}</ref>
<ref name="AutoNT-95">{{cite web |last=Strachan |first=James |date=29 August 2003 |title=Groovy&nbsp;– the birth of a new dynamic language for the Java platform |url=http://radio.weblogs.com/0112098/2003/08/29.html |access-date=11 June 2007 |archive-url=https://web.archive.org/web/20070405085722/http://radio.weblogs.com/0112098/2003/08/29.html |archive-date=5 April 2007 |url-status=dead}}</ref>
<ref name="linuxdevcenter">{{cite web |url=http://www.linuxdevcenter.com/pub/a/linux/2001/11/29/ruby.html |title=An Interview with the Creator of Ruby |publisher=Linuxdevcenter.com |access-date=3 December 2012 |archive-date=28 April 2018 |archive-url=https://web.archive.org/web/20180428150410/http://www.linuxdevcenter.com/pub/a/linux/2001/11/29/ruby.html |url-status=live}}</ref>
<ref name="AutoNT-99">{{cite web |url=http://www.tcl.tk/cgi-bin/tct/tip/3.html |title=TIP #3: TIP Format |last1=Kupries |first1=Andreas |last2=Fellows |first2=Donal K. |work=tcl.tk |publisher=Tcl Developer Xchange |date=14 September 2000 |access-date=24 November 2008 |archive-date=13 July 2017 |archive-url=https://web.archive.org/web/20170713233954/http://tcl.tk/cgi-bin/tct/tip/3.html |url-status=live}}</ref>
<ref name="AutoNT-100">{{cite web |url=http://www.erlang.org/eeps/eep-0001.html |title=EEP 1: EEP Purpose and Guidelines |last1=Gustafsson |first1=Per |last2=Niskanen |first2=Raimo |publisher=erlang.org |date=29 January 2007 |access-date=19 April 2011 |archive-date=15 June 2020 |archive-url=https://web.archive.org/web/20200615153206/http://erlang.org/eeps/eep-0001.html |url-status=live}}</ref>


<ref name="lj-bdfl-resignation">{{cite magazine |url=https://www.linuxjournal.com/content/guido-van-rossum-stepping-down-role-pythons-benevolent-dictator-life |title=Guido van Rossum Stepping Down from Role as Python's Benevolent Dictator For Life |last=Fairchild |first=Carlie |magazine=Linux Journal |date=12 July 2018 |access-date=13 July 2018 |archive-date=13 July 2018 |archive-url=https://web.archive.org/web/20180713192427/https://www.linuxjournal.com/content/guido-van-rossum-stepping-down-role-pythons-benevolent-dictator-life |url-status=live}}</ref>
<ref name="lj-bdfl-resignation">{{cite magazine |url=https://www.linuxjournal.com/content/guido-van-rossum-stepping-down-role-pythons-benevolent-dictator-life |title=Guido van Rossum Stepping Down from Role as Python's Benevolent Dictator For Life |last=Fairchild |first=Carlie |magazine=Linux Journal |date=12 July 2018 |access-date=13 July 2018 |archive-date=13 July 2018 |archive-url=https://web.archive.org/web/20180713192427/https://www.linuxjournal.com/content/guido-van-rossum-stepping-down-role-pythons-benevolent-dictator-life |url-status=live}}</ref>
Line 799: Line 603:


===Sources===
===Sources===
* {{cite web |url=https://wiki.python.org/moin/PythonForArtificialIntelligence |title=Python for Artificial Intelligence |publisher=Python Wiki |date=19 July 2012 |access-date=3 December 2012 |url-status=dead |archive-url=https://web.archive.org/web/20121101045354/http://wiki.python.org/moin/PythonForArtificialIntelligence |archive-date=1 November 2012}}
* {{cite web |url=https://wiki.python.org/moin/PythonForArtificialIntelligence |title=Python for Artificial Intelligence |publisher=Python Wiki |date=19 July 2012 |access-date=3 December 2012 |archive-url=https://web.archive.org/web/20121101045354/http://wiki.python.org/moin/PythonForArtificialIntelligence |archive-date=1 November 2012}}
* {{cite journal |editor-last=Paine |editor-first=Jocelyn |title=AI in Python |journal=AI Expert Newsletter |publisher=Amzi! |date=August 2005 |url=http://www.ainewsletter.com/newsletters/aix_0508.htm#python_ai_ai |access-date=11 February 2012 |archive-url=https://web.archive.org/web/20120326105810/http://www.ainewsletter.com/newsletters/aix_0508.htm#python_ai_ai |archive-date=26 March 2012 |url-status=dead}}
* {{cite journal |editor-last=Paine |editor-first=Jocelyn |title=AI in Python |journal=AI Expert Newsletter |publisher=Amzi! |date=August 2005 |url=http://www.ainewsletter.com/newsletters/aix_0508.htm#python_ai_ai |access-date=11 February 2012 |archive-url=https://web.archive.org/web/20120326105810/http://www.ainewsletter.com/newsletters/aix_0508.htm#python_ai_ai |archive-date=26 March 2012 }}
* {{cite web |url=https://pypi.python.org/pypi/PyAIML |title=PyAIML 0.8.5 : Python Package Index |publisher=Pypi.python.org |access-date=17 July 2013}}
* {{cite web |url=https://pypi.python.org/pypi/PyAIML |title=PyAIML 0.8.5: Python Package Index |publisher=Pypi.python.org |access-date=17 July 2013}}
* {{cite book |title=Artificial Intelligence: A Modern Approach |last1=Russell |first1=Stuart J. |author-link1=Stuart J. Russell |last2=Norvig |first2=Peter |author-link2=Peter Norvig |name-list-style=amp |edition=3rd |year=2009 |publisher=Prentice Hall |location=Upper Saddle River, NJ |isbn=978-0-13-604259-4}}
* {{cite book |title=Artificial Intelligence: A Modern Approach |last1=Russell |first1=Stuart J. |author-link1=Stuart J. Russell |last2=Norvig |first2=Peter |author-link2=Peter Norvig |name-list-style=amp |edition=3rd |year=2009 |publisher=Prentice Hall |location=Upper Saddle River, NJ |isbn=978-0-13-604259-4}}


Line 813: Line 617:
7. Neutrality on the part of editors is essential. In terms of major debates, items representing all major positions should be included, with annotations indicating the specific POV of each. We may have to work out rules where topic disputes are irreconcilable.
7. Neutrality on the part of editors is essential. In terms of major debates, items representing all major positions should be included, with annotations indicating the specific POV of each. We may have to work out rules where topic disputes are irreconcilable.
-->
-->
* {{cite book |last=Downey |first=Allen |title=Think Python: How to Think Like a Computer Scientist |edition=3rd |date=July 2024 |publisher=O'Reilly Media |isbn=978-1098155438 |url=https://allendowney.github.io/ThinkPython/}}
* {{cite book |last=Downey |first=Allen |title=Think Python: How to Think Like a Computer Scientist |edition=3rd |date=July 2024 |publisher=O'Reilly Media |isbn=978-1-0981-5543-8 |url=https://allendowney.github.io/ThinkPython/}}
* {{cite book |last=Lutz |first=Mark |title=Learning Python |publisher=O'Reilly Media |year=2013 |edition=5th |isbn=978-0-596-15806-4}}
* {{cite book |last=Lutz |first=Mark |title=Learning Python |publisher=O'Reilly Media |year=2013 |edition=5th |isbn=978-0-596-15806-4}}
* {{cite book |last=Summerfield |first=Mark |title=Programming in Python 3 |publisher=Addison-Wesley Professional|year=2009|edition=2nd|isbn=978-0-321-68056-3}}
* {{cite book |last=Summerfield |first=Mark |title=Programming in Python 3 |publisher=Addison-Wesley Professional|year=2009|edition=2nd|isbn=978-0-321-68056-3}}
Line 831: Line 635:
{{Sister project links |wikt=no |display=Python |commons=Category:Python (programming language) |b=Python Programming |n=no |s=no |voy=no |species=no |d=Q28865}}
{{Sister project links |wikt=no |display=Python |commons=Category:Python (programming language) |b=Python Programming |n=no |s=no |voy=no |species=no |d=Q28865}}
* {{Official website}}
* {{Official website}}
* [https://docs.python.org/3/ Python documentation]
* [https://docs.python.org/3/tutorial/ The Python Tutorial]
* [https://docs.python.org/3/tutorial/ The Python Tutorial]



Revision as of 06:14, 20 November 2025

Script error: No such module "Unsubst".Template:Short description Script error: No such module "Unsubst". Template:Use American English Script error: No such module "Infobox".Script error: No such module "Check for unknown parameters". Template:Python sidebar

Python is a high-level, general-purpose programming language. Its design philosophy emphasizes code readability with the use of significant indentation.[1] Python is dynamically type-checked and garbage-collected. It supports multiple programming paradigms, including structured (particularly procedural), object-oriented and functional programming.

Guido van Rossum began working on Python in the late 1980s as a successor to the ABC programming language. Python 3.0, released in 2008, was a major revision and not completely backward-compatible with earlier versions. Beginning with Python 3.5,[2] capabilities and keywords for typing were added to the language, allowing optional static typing.[3] Currently only versions in the 3.x series are supported.

Python has gained widespread use in the machine learning community.[4][5][6][7] It is widely taught as an introductory programming language.[8] Since 2003, Python has consistently ranked in the top ten of the most popular programming languages in the TIOBE Programming Community Index, which ranks based on searches in 24 platforms.[9]

History

Script error: No such module "Labelled list hatnote".

File:Guido van Rossum in PyConUS24.jpg
The designer of Python, Guido van Rossum, at PyCon US 2024

Python was conceived in the late 1980s[10] by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands.[11] It was designed as a successor to the ABC programming language, which was inspired by SETL,[12] capable of exception handling and interfacing with the Amoeba operating system.[13] Python implementation began in December 1989.[11] Van Rossum first released it in 1991 as Python 0.9.0.[11] Van Rossum assumed sole responsibility for the project, as the lead developer, until 12 July 2018, when he announced his "permanent vacation" from responsibilities as Python's "benevolent dictator for life" (BDFL); this title was bestowed on him by the Python community to reflect his long-term commitment as the project's chief decision-maker.[14] (He has since come out of retirement and is self-titled "BDFL-emeritus".) In January 2019, active Python core developers elected a five-member Steering Council to lead the project.[15][16]

The name Python derives from the British comedy series Monty Python's Flying Circus.[17] (See Template:Section link.)

Python 2.0 was released on 16 October 2000, featuring many new features such as list comprehensions, cycle-detecting garbage collection, reference counting, and Unicode support.[18] Python 2.7's end-of-life was initially set for 2015, and then postponed to 2020 out of concern that a large body of existing code could not easily be forward-ported to Python 3.[19][20] It no longer receives security patches or updates.[21][22] While Python 2.7 and older versions are officially unsupported, a different unofficial Python implementation, PyPy, continues to support Python 2, i.e., "2.7.18+" (plus 3.11), with the plus signifying (at least some) "backported security updates".[23]

Python 3.0 was released on 3 December 2008, and was a major revision and not completely backward-compatible with earlier versions, with some new semantics and changed syntax. Python 2.7.18, released in 2020, was the last release of Python 2.[24] Several releases in the Python 3.x series have added new syntax to the language, and made a few (considered very minor) backward-incompatible changes.

As of November 2025Script error: No such module "Check for unknown parameters"., Python 3.14.0 is the latest stable release, and Python 3.13.9 was released a week later, all older 3.x versions had a security update down to Python 3.9.24 then again with 3.9.25, the final version in 3.9 series. Python 3.10 is, since November 2025, the oldest supported branch.[25] Python 3.15 has an alpha released, and Android has a official downloadable executable available for Python 3.14. Releases receive two years of full support followed by three years of security support.

Design philosophy and features

Python is a multi-paradigm programming language. Object-oriented programming and structured programming are fully supported, and many of their features support functional programming and aspect-oriented programming – including metaprogramming[26] and metaobjects.[27] Many other paradigms are supported via extensions, including design by contract[28][29] and logic programming.[30] Python is often referred to as a 'glue language'[31] because it is purposely designed to be able to integrate components written in other languages.

Python uses dynamic typing and a combination of reference counting and a cycle-detecting garbage collector for memory management.[32] It uses dynamic name resolution (late binding), which binds method and variable names during program execution.

Python's design offers some support for functional programming in the "Lisp tradition". It has filter, map, and reduce functions; list comprehensions, dictionaries, sets, and generator expressions.[33] The standard library has two modules (Template:Codes and Template:Codes) that implement functional tools borrowed from Haskell and Standard ML.[34]

Python's core philosophy is summarized in the Zen of Python (PEP 20) written by Tim Peters, which includes aphorisms such as these:[35]

  • Explicit is better than implicit.
  • Simple is better than complex.
  • Readability counts.
  • Special cases aren't special enough to break the rules.
  • Although practicality beats purity.
  • Errors should never pass silently.
  • Unless explicitly silenced.
  • There should be one-- and preferably only one --obvious way to do it.

However, Python has received criticism for violating these principles and adding unnecessary language bloat.[36] Responses to these criticisms note that the Zen of Python is a guideline rather than a rule.[37] The addition of some new features had been controversial: Guido van Rossum resigned as Benevolent Dictator for Life after conflict about adding the assignment expression operator in Python 3.8 .[38][39]

Nevertheless, rather than building all functionality into its core, Python was designed to be highly extensible via modules. This compact modularity has made it particularly popular as a means of adding programmable interfaces to existing applications. Van Rossum's vision of a small core language with a large standard library and easily extensible interpreter stemmed from his frustrations with ABC, which represented the opposite approach.[10]

Python claims to strive for a simpler, less-cluttered syntax and grammar, while giving developers a choice in their coding methodology. Python lacks do while loops, which Rossum considered harmful.[40] In contrast to Perl's motto "there is more than one way to do it", Python advocates an approach where "there should be one – and preferably only one – obvious way to do it".[35] In practice, however, Python provides many ways to achieve a given goal. There are at least three ways to format a string literal, with no certainty as to which one a programmer should use.[41] Alex Martelli is a Fellow at the Python Software Foundation and Python book author; he wrote that "To describe something as 'clever' is not considered a compliment in the Python culture."[42]

Python's developers typically prioritise readability over performance. For example, they reject patches to non-critical parts of the CPython reference implementation that would offer increases in speed that do not justify the cost of clarity and readability.[43]Script error: No such module "Unsubst". Execution speed can be improved by moving speed-critical functions to extension modules written in languages such as C, or by using a just-in-time compiler like PyPy. Also, it is possible to transpile to other languages. However, this approach either fails to achieve the expected speed-up, since Python is a very dynamic language, or only a restricted subset of Python is compiled (with potential minor semantic changes).[44]

Python is meant to be a fun language to use. This goal is reflected in the name – a tribute to the British comedy group Monty Python[45] – and in playful approaches to some tutorials and reference materials. For instance, some code examples use the terms "spam" and "eggs" (in reference to a Monty Python sketch), rather than the typical terms "foo" and "bar".[46][47]

A common neologism in the Python community is pythonic, which has a broad range of meanings related to program style: Pythonic code may use Python idioms well; be natural or show fluency in the language; or conform with Python's minimalist philosophy and emphasis on readability.[48]

Syntax and semantics

Script error: No such module "Labelled list hatnote". Python is meant to be an easily readable language. Its formatting is visually uncluttered and often uses English keywords where other languages use punctuation. Unlike many other languages, it does not use curly brackets to delimit blocks, and semicolons after statements are allowed but rarely used. It has fewer syntactic exceptions and special cases than C or Pascal.[49]

Indentation

Script error: No such module "labelled list hatnote".

Python uses whitespace indentation, rather than curly brackets or keywords, to delimit blocks. An increase in indentation comes after certain statements; a decrease in indentation signifies the end of the current block.[50] Thus, the program's visual structure accurately represents its semantic structure.[51] This feature is sometimes termed the off-side rule. Some other languages use indentation this way; but in most, indentation has no semantic meaning. The recommended indent size is four spaces.[52]

Statements and control flow

Python's statements include the following:

  • The assignment statement, using a single equals sign =
  • The if statement, which conditionally executes a block of code, along with else and elif (a contraction of else if)
  • The for statement, which iterates over an iterable object, capturing each element to a variable for use by the attached block; the variable is not deleted when the loop finishes
  • The while statement, which executes a block of code as long as boolean condition is true
  • The try statement, which allows exceptions raised in its attached code block to be caught and handled by except clauses (or new syntax except* in Python 3.11 for exception groups);[53] the try statement also ensures that clean-up code in a finally block is always run regardless of how the block exits
  • The raise statement, used to raise a specified exception or re-raise a caught exception
  • The class statement, which executes a block of code and attaches its local namespace to a class, for use in object-oriented programming
  • The def statement, which defines a function or method
  • The with statement, which encloses a code block within a context manager, allowing resource-acquisition-is-initialization (RAII)-like behavior and replacing a common try/finally idiom[54] Examples of a context include acquiring a lock before some code is run, and then releasing the lock; or opening and then closing a file
  • The break statement, which exits a loop
  • The continue statement, which skips the rest of the current iteration and continues with the next
  • The del statement, which removes a variable—deleting the reference from the name to the value, and producing an error if the variable is referred to before it is redefined Template:Efn
  • The pass statement, serving as a NOP (i.e., no operation), which is syntactically needed to create an empty code block
  • The assert statement, used in debugging to check for conditions that should apply
  • The yield statement, which returns a value from a generator function (and also an operator); used to implement coroutines
  • The return statement, used to return a value from a function
  • The import and from statements, used to import modules whose functions or variables can be used in the current program
  • The match and case statements, analogous to a switch statement construct, which compares an expression against one or more cases as a control-flow measure

The assignment statement (=) binds a name as a reference to a separate, dynamically allocated object. Variables may subsequently be rebound at any time to any object. In Python, a variable name is a generic reference holder without a fixed data type; however, it always refers to some object with a type. This is called dynamic typing—in contrast to statically-typed languages, where each variable may contain only a value of a certain type.

Python does not support tail call optimization or first-class continuations; according to Van Rossum, the language never will.[55][56] However, better support for coroutine-like functionality is provided by extending Python's generators.[57] Before 2.5, generators were lazy iterators; data was passed unidirectionally out of the generator. From Python 2.5 on, it is possible to pass data back into a generator function; and from version 3.3, data can be passed through multiple stack levels.[58]

Expressions

Python's expressions include the following:

  • The +, -, and * operators for mathematical addition, subtraction, and multiplication are similar to other languages, but the behavior of division differs. There are two types of division in Python: floor division (or integer division) //, and floating-point division /.[59] Python uses the ** operator for exponentiation.
  • Python uses the + operator for string concatenation. The language uses the * operator for duplicating a string a specified number of times.
  • The @ infix operator is intended to be used by libraries such as NumPy for matrix multiplication.[60][61]
  • The syntax :=, called the "Template:Va", was introduced in Python 3.8. This operator assigns values to variables as part of a larger expression.[62]
  • In Python, == compares two objects by value. Python's is operator may be used to compare object identities (i.e., comparison by reference), and comparisons may be chained—for example, a <= b <= c.
  • Python uses and, or, and not as Boolean operators.
  • Python has a type of expression called a list comprehension, and a more general expression called a generator expression.[33]
  • Anonymous functions are implemented using lambda expressions; however, there may be only one expression in each body.
  • Conditional expressions are written as x if c else y.[63] (This is different in operand order from the c ? x : y operator common to many other languages.)
  • Python makes a distinction between lists and tuples. Lists are written as [1, 2, 3], are mutable, and cannot be used as the keys of dictionaries (since dictionary keys must be immutable in Python). Tuples, written as (1, 2, 3), are immutable and thus can be used as the keys of dictionaries, provided that all of the tuple's elements are immutable. The + operator can be used to concatenate two tuples, which does not directly modify their contents, but produces a new tuple containing the elements of both. For example, given the variable t initially equal to (1, 2, 3), executing t = t + (4, 5) first evaluates t + (4, 5), which yields (1, 2, 3, 4, 5); this result is then assigned back to t—thereby effectively "modifying the contents" of t while conforming to the immutable nature of tuple objects. Parentheses are optional for tuples in unambiguous contexts.[64]
  • Python features sequence unpacking where multiple expressions, each evaluating to something assignable (e.g., a variable or a writable property) are associated just as in forming tuple literal; as a whole, the results are then put on the left-hand side of the equal sign in an assignment statement. This statement expects an iterable object on the right-hand side of the equal sign to produce the same number of values as the writable expressions on the left-hand side; while iterating, the statement assigns each of the values produced on the right to the corresponding expression on the left.[65]
  • Python has a "string format" operator % that functions analogously to printf format strings in the C language—e.g. "spam=%s eggs=%d" % ("blah", 2) evaluates to "spam=blah eggs=2". In Python 2.6+ and 3+, this operator was supplemented by the format() method of the str class, e.g., "spam={0} eggs={1}".format("blah", 2). Python 3.6 added "f-strings": spam = "blah"; eggs = 2; f'spam={spam} eggs={eggs}'.[66]
  • Strings in Python can be concatenated by "adding" them (using the same operator as for adding integers and floats); e.g., "spam" + "eggs" returns "spameggs". If strings contain numbers, they are concatenated as strings rather than as integers, e.g. "2" + "2" returns "22".
  • Python supports string literals in several ways:
    • Delimited by single or double quotation marks; single and double quotation marks have equivalent functionality (unlike in Unix shells, Perl, and Perl-influenced languages). Both marks use the backslash (\) as an escape character. String interpolation became available in Python 3.6 as "formatted string literals".[66]
    • Triple-quoted, i.e., starting and ending with three single or double quotation marks; this may span multiple lines and function like here documents in shells, Perl, and Ruby.
    • Raw string varieties, denoted by prefixing the string literal with r. Escape sequences are not interpreted; hence raw strings are useful where literal backslashes are common, such as in regular expressions and Windows-style paths. (Compare "@-quoting" in C#.)
  • Python has array index and array slicing expressions in lists, which are written as a[key], a[start:stop] or a[start:stop:step]. Indexes are zero-based, and negative indexes are relative to the end. Slices take elements from the start index up to, but not including, the stop index. The (optional) third slice parameter, called step or stride, allows elements to be skipped or reversed. Slice indexes may be omitted—for example, a[:] returns a copy of the entire list. Each element of a slice is a shallow copy.

In Python, a distinction between expressions and statements is rigidly enforced, in contrast to languages such as Common Lisp, Scheme, or Ruby. This distinction leads to duplicating some functionality, for example:

  • List comprehensions vs. for-loops
  • Conditional expressions vs. if blocks
  • The eval() vs. exec() built-in functions (in Python 2, exec is a statement); the former function is for expressions, while the latter is for statements

A statement cannot be part of an expression; because of this restriction, expressions such as list and dict comprehensions (and lambda expressions) cannot contain statements. As a particular case, an assignment statement such as a = 1 cannot be part of the conditional expression of a conditional statement.

Typing

File:Python 3.13 Standrd Type Hierarchy-en.svg
The standard type hierarchy in Python 3

Python uses duck typing, and it has typed objects but untyped variable names. Type constraints are not checked at definition time; rather, operations on an object may fail at usage time, indicating that the object is not of an appropriate type. Despite being dynamically typed, Python is strongly typed, forbidding operations that are poorly defined (e.g., adding a number and a string) rather than quietly attempting to interpret them.

Python allows programmers to define their own types using classes, most often for object-oriented programming. New instances of classes are constructed by calling the class, for example, SpamClass() or EggsClass()); the classes are instances of the metaclass type (which is an instance of itself), thereby allowing metaprogramming and reflection.

Before version 3.0, Python had two kinds of classes, both using the same syntax: old-style and new-style.[67] Current Python versions support the semantics of only the new style.

Python supports optional type annotations.[68][69] These annotations are not enforced by the language, but may be used by external tools such as mypy to catch errors. Python includes a module typing including several type names for type annotations.[70][71] Also, Mypy supports a Python compiler called mypyc, which leverages type annotations for optimization.[72]

Summary of Python 3's built-in types
Type Mutability Description Syntax examples
bool immutable Boolean value True
False
bytearray mutable Sequence of bytes bytearray(b'Some ASCII')
bytearray(b"Some ASCII")
bytearray([119, 105, 107, 105])
bytes immutable Sequence of bytes b'Some ASCII'
b"Some ASCII"
bytes([119, 105, 107, 105])
complex immutable Complex number with real and imaginary parts 3+2.7j
3 + 2.7j
5j
dict mutable Associative array (or dictionary) of key and value pairs; can contain mixed types (keys and values); keys must be a hashable type {'key1': 1.0, 3: False}
{}
types.EllipsisType immutable An ellipsis placeholder to be used as an index in NumPy arrays ...
Ellipsis
float immutable Double-precision floating-point number. The precision is machine-dependent, but in practice it is generally implemented as a 64-bit IEEE 754 number with 53 bits of precision.[73]

1.33333

frozenset immutable Unordered set, contains no duplicates; can contain mixed types, if hashable frozenset({4.0, 'string', True})

frozenset()

int immutable Integer of unlimited magnitude[74] 42
list mutable List, can contain mixed types [4.0, 'string', True]
[]
types.NoneType immutable An object representing the absence of a value, often called null in other languages None
types.NotImplementedType immutable A placeholder that can be returned from overloaded operators to indicate unsupported operand types. NotImplemented
range immutable An immutable sequence of numbers, commonly used for iterating a specific number of times in for loops[75] range(1, 10)
range(10, 5, 2)
set mutable Unordered set, contains no duplicates; can contain mixed types, if hashable {4.0, 'string', True}
set()
str immutable A character string: sequence of Unicode codepoints 'Wikipedia'
"Wikipedia"
"""Spanning
multiple
lines"""
tuple immutable Tuple, can contain mixed types (4.0, 'string', True)
('single element',)
()

Arithmetic operations

Python includes conventional symbols for arithmetic operators (+, -, *, /), the floor-division operator //, and the modulo operator %. (With the modulo operator, a remainder can be negative, e.g., 4 % -3 == -2.) Also, Python offers the ** symbol for exponentiation, e.g. 5**3 == 125 and 9**0.5 == 3.0. Also, it offers the matrix‑multiplication operator @ .[76] These operators work as in traditional mathematics; with the same precedence rules, the infix operators + and - can also be unary, to represent positive and negative numbers respectively.

Division between integers produces floating-point results. The behavior of division has changed significantly over time:[77]

  • The current version of Python (i.e., since 3.0) changed the / operator to always represent floating-point division, e.g., 5/2 == 2.5.
  • The floor division // operator was introduced, meaning that 7//3 == 2, -7//3 == -3, 7.5//3 == 2.0, and -7.5//3 == -3.0. For Python 2.7, adding the from __future__ import division statement allows a module in Python 2.7 to use Python 3.x rules for division (see above).

In Python terms, the / operator represents true division (or simply division), while the // operator represents floor division. Before version 3.0, the / operator represents classic division.[77]

Rounding towards negative infinity, though a different method than in most languages, adds consistency to Python. For instance, this rounding implies that the equation (a + b)//b == a//b + 1 is always true. Also, the rounding implies that the equation b*(a//b) + a%b == a is valid for both positive and negative values of a. As expected, the result of a%b lies in the half-open interval [0, b), where b is a positive integer; however, maintaining the validity of the equation requires that the result must lie in the interval (b, 0] when b is negative.[78]

Python provides a round function for rounding a float to the nearest integer. For tie-breaking, Python 3 uses the round to even method: round(1.5) and round(2.5) both produce 2.[79] Python versions before 3 used the round-away-from-zero method: round(0.5) is 1.0, and round(-0.5) is −1.0.[80]

Python allows Boolean expressions that contain multiple equality relations to be consistent with general usage in mathematics. For example, the expression a < b < c tests whether a is less than b and b is less than c.[81] C-derived languages interpret this expression differently: in C, the expression would first evaluate a < b, resulting in 0 or 1, and that result would then be compared with c.[82]

Python uses arbitrary-precision arithmetic for all integer operations. The Decimal type/class in the decimal module provides decimal floating-point numbers to a pre-defined arbitrary precision with several rounding modes.[83] The Fraction class in the fractions module provides arbitrary precision for rational numbers.[84]

Due to Python's extensive mathematics library and the third-party library NumPy, the language is frequently used for scientific scripting in tasks such as numerical data processing and manipulation.[85][86]

Function syntax

Functions are created in Python by using the def keyword. A function is defined similarly to how it is called, by first providing the function name and then the required parameters. Here is an example of a function that prints its inputs:

def printer(input1, input2 = "already there"):
    print(input1)
    print(input2)
    
printer("hello")
    
# Example output:
# hello
# already there

To assign a default value to a function parameter in case no actual value is provided at run time, variable-definition syntax can be used inside the function header.

Code examples

"Hello, World!" program:

print('Hello, World!')

Program to calculate the factorial of a non-negative integer:

text = input('Type a number, and its factorial will be printed: ')
n = int(text)

if n < 0:
    raise ValueError('You must enter a non-negative integer')

factorial = 1
for i in range(2, n + 1):
    factorial *= i

print(factorial)

Libraries

Python's large standard library[87] is commonly cited as one of its greatest strengths. For Internet-facing applications, many standard formats and protocols such as MIME and HTTP are supported. The language includes modules for creating graphical user interfaces, connecting to relational databases, generating pseudorandom numbers, arithmetic with arbitrary-precision decimals,[83] manipulating regular expressions, and unit testing.

Some parts of the standard library are covered by specifications—for example, the Web Server Gateway Interface (WSGI) implementation wsgiref follows PEP 333[88]—but most parts are specified by their code, internal documentation, and test suites. However, because most of the standard library is cross-platform Python code, only a few modules must be altered or rewritten for variant implementations.

As of 13 March 2025,Script error: No such module "Check for unknown parameters". the Python Package Index (PyPI), the official repository for third-party Python software, contains over 614,339[89] packages.

Development environments

Script error: No such module "Labelled list hatnote".

MostTemplate:Which? Python implementations (including CPython) include a read–eval–print loop (REPL); this permits the environment to function as a command line interpreter, with which users enter statements sequentially and receive results immediately.[90]

Also, CPython is bundled with an integrated development environment (IDE) called IDLE,[91] which is oriented toward beginners.Script error: No such module "Unsubst".

Other shells, including IDLE and IPython, add additional capabilities such as improved auto-completion, session-state retention, and syntax highlighting.[91][92]

Standard desktop IDEs include PyCharm, Spyder, and Visual Studio Code;Script error: No such module "Unsubst". there are web browser-based IDEs, such as the following environments:

Implementations

Script error: No such module "Labelled list hatnote".

Reference implementation

CPython is the reference implementation of Python. This implementation is written in C, meeting the C11 standard[96] since version 3.11. Older versions use the C89 standard with several select C99 features, but third-party extensions are not limited to older C versions—e.g., they can be implemented using C11 or C++.[97][98] CPython compiles Python programs into an intermediate bytecode,[99] which is then executed by a virtual machine.[100] CPython is distributed with a large standard library written in a combination of C and native Python.

CPython is available for many platforms, including Windows and most modern Unix-like systems, including macOS (and Apple M1 Macs, since Python 3.9.1, using an experimental installer). Starting with Python 3.9, the Python installer intentionally fails to install on Windows 7 and 8;[101][102] Windows XP was supported until Python 3.5, with unofficial support for VMS.[103] Platform portability was one of Python's earliest priorities.[104] During development of Python 1 and 2, even OS/2 and Solaris were supported;[105] since that time, support has been dropped for many platforms.

All current Python versions (since 3.7) support only operating systems that feature multithreading, by now supporting not nearly as many operating systems (dropping many outdated) than in the past.

Limitations of the reference implementation

  • The energy usage of Python with CPython for typically written code is much worse than C by a factor of 75.88.[106]
  • The throughput of Python with CPython for typically written code is worse than C by a factor of 71.9.[106]
  • The average memory usage of CPython for typically written code is worse than C by a factor of 2.4.[106]

Other implementations

All alternative implementations have at least slightly different semantics. For example, an alternative may include unordered dictionaries, in contrast to other current Python versions. As another example in the larger Python ecosystem, PyPy does not support the full C Python API.

Creating an executable with Python often is done by bundling an entire Python interpreter into the executable, which causes binary sizes to be massive for small programs,[107] yet there exist implementations that are capable of truly compiling Python. Alternative implementations include the following:

  • PyPy is a faster, compliant interpreter of Python 2.7 and 3.10.[108][109] PyPy's just-in-time compiler often improves speed significantly relative to CPython, but PyPy does not support some libraries written in C.[110] PyPy offers support for the RISC-V instruction-set architecture.
  • Codon is an implementation with an ahead-of-time (AOT) compiler, which compiles a statically-typed Python-like language whose "syntax and semantics are nearly identical to Python's, there are some notable differences"[111] For example, Codon uses 64-bit machine integers for speed, not arbitrarily as with Python; Codon developers claim that speedups over CPython are usually on the order of ten to a hundred times. Codon compiles to machine code (via LLVM) and supports native multithreading.[112] Codon can also compile to Python extension modules that can be imported and used from Python.
  • MicroPython and CircuitPython are Python 3 variants that are optimized for microcontrollers, including the Lego Mindstorms EV3.[113]
  • Pyston is a variant of the Python runtime that uses just-in-time compilation to speed up execution of Python programs.[114]
  • Cinder is a performance-oriented fork of CPython 3.8 that features a number of optimizations, including bytecode inline caching, eager evaluation of coroutines, a method-at-a-time JIT, and an experimental bytecode compiler.[115]
  • The Snek[116][117][118] embedded computing language "is Python-inspired, but it is not Python. It is possible to write Snek programs that run under a full Python system, but most Python programs will not run under Snek."[119] Snek is compatible with 8-bit AVR microcontrollers such as ATmega 328P-based Arduino, as well as larger microcontrollers that are compatible with MicroPython. Snek is an imperative language that (unlike Python) omits object-oriented programming. Snek supports only one numeric data type, which features 32-bit single precision (resembling JavaScript numbers, though smaller).

Unsupported implementations

Stackless Python is a significant fork of CPython that implements microthreads. This implementation uses the call stack differently, thus allowing massively concurrent programs. PyPy also offers a stackless version.[120]

Just-in-time Python compilers have been developed, but are now unsupported:

  • Google began a project named Unladen Swallow in 2009: this project aimed to speed up the Python interpreter five-fold by using LLVM, and improve multithreading capability for scaling to thousands of cores,[121] while typical implementations are limited by the global interpreter lock.
  • Psyco is a discontinued just-in-time specializing compiler, which integrates with CPython and transforms bytecode to machine code at runtime. The emitted code is specialized for certain data types and is faster than standard Python code. Psyco does not support Python 2.7 or later.
  • PyS60 was a Python 2 interpreter for Series 60 mobile phones, which was released by Nokia in 2005. The interpreter implemented many modules from Python's standard library, as well as additional modules for integration with the Symbian operating system. The Nokia N900 also supports Python through the GTK widget library, allowing programs to be written and run on the target device.[122]

Transpilers to other languages

There are several compilers/transpilers to high-level object languages; the source language is unrestricted Python, a subset of Python, or a language similar to Python:

  • Brython[123] and Transcrypt[124][125] compile Python to JavaScript.
  • Cython compiles a superset of Python to C. The resulting code can be used with Python via direct C-level API calls into the Python interpreter.
  • PyJL compiles/transpiles a subset of Python to "human-readable, maintainable, and high-performance Julia source code".[44] Despite the developers' performance claims, this is not possible for arbitrary Python code; that is, compiling to a faster language or machine code is known to be impossible in the general case. The semantics of Python might potentially be changed, but in many cases speedup is possible with few or no changes in the Python code. The faster Julia source code can then be used from Python or compiled to machine code.
  • Nuitka compiles Python into C.[126] This compiler works with Python 3.4 to 3.13 (and 2.6 and 2.7) for Python's main supported platforms (and Windows 7 or even Windows XP) and for Android. The compiler developers claim full support for Python 3.10, partial support for Python 3.11 and 3.12, and experimental support for Python 3.13. Nuitka supports macOS including Apple Silicon-based versions. The compiler is free of cost, though it has commercial add-ons (e.g., for hiding source code).
  • Numba is a JIT compiler that is used from Python; the compiler translates a subset of Python and NumPy code into fast machine code. This tool is enabled by adding a decorator to the relevant Python code.
  • Pythran compiles a subset of Python 3 to C++ (C++11).[127]
  • RPython can be compiled to C, and it is used to build the PyPy interpreter for Python.
  • The Python → 11l → C++ transpiler[128] compiles a subset of Python 3 to C++ (C++17).

There are also specialized compilers:

Some older projects existed, as well as compilers not designed for use with Python 3.x and related syntax:

  • Google's Grumpy transpiles Python 2 to Go.[129][130][131] The latest release was in 2017.
  • IronPython allows running Python 2.7 programs with the .NET Common Language Runtime.[132] An alpha version (released in 2021), is available for "Python 3.4, although features and behaviors from later versions may be included."[133]
  • Jython compiles Python 2.7 to Java bytecode, allowing the use of Java libraries from a Python program.[134]
  • Pyrex (last released in 2010) and Shed Skin (last released in 2013) compile to C and C++ respectively.

Performance

A performance comparison among various Python implementations, using a non-numerical (combinatorial) workload, was presented at EuroSciPy '13.[135] In addition, Python's performance relative to other programming languages is benchmarked by The Computer Language Benchmarks Game.[136]

There are several approaches to optimizing Python performance, despite the inherent slowness of an interpreted language. These approaches include the following strategies or tools:

  • Just-in-time compilation: Dynamically compiling parts of a Python program during the execution of the program. This technique is used in libraries such as Numba and PyPy.
  • Static compilation: Sometimes, Python code can be compiled into machine code sometime before execution. An example of this approach is Cython, which compiles Python into C.
  • Concurrency and parallelism: Multiple tasks can be run simultaneously. Python contains modules such as `multiprocessing` to support this form of parallelism. Moreover, this approach helps to overcome limitations of the Global Interpreter Lock (GIL) in CPU tasks.
  • Efficient data structures: Performance can also be improved by using data types such as Set for membership tests, or deque from collections for queue operations.
  • Performance gains can be observed by utilizing libraries such as NumPy. Most high performance Python libraries use C or Fortran under the hood instead of the Python interpreter.[137]

Language Development

Python's development is conducted mostly through the Python Enhancement Proposal (PEP) process; this process is the primary mechanism for proposing major new features, collecting community input on issues, and documenting Python design decisions.[138] Python coding style is covered in PEP 8.[52] Outstanding PEPs are reviewed and commented on by the Python community and the steering council.[138]

Enhancement of the language corresponds with development of the CPython reference implementation. The mailing list python-dev is the primary forum for the language's development. Specific issues were originally discussed in the Roundup bug tracker hosted by the foundation.[139] In 2022, all issues and discussions were migrated to GitHub.[140] Development originally took place on a self-hosted source-code repository running Mercurial, until Python moved to GitHub in January 2017.[141]

CPython's public releases have three types, distinguished by which part of the version number is incremented:

  • Backward-incompatible versions, where code is expected to break and must be manually ported. The first part of the version number is incremented. These releases happen infrequently—version 3.0 was released 8 years after 2.0. According to Guido van Rossum, a version 4.0 will probably never exist.[142]
  • Major or "feature" releases are largely compatible with the previous version but introduce new features. The second part of the version number is incremented. Starting with Python 3.9, these releases are expected to occur annually.[143][144] Each major version is supported by bug fixes for several years after its release.[145]
  • Bug fix releases,[146] which introduce no new features, occur approximately every three months; these releases are made when a sufficient number of bugs have been fixed upstream since the last release. Security vulnerabilities are also patched in these releases. The third and final part of the version number is incremented.[146]

Many alpha, beta, and release-candidates are also released as previews and for testing before final releases. Although there is a rough schedule for releases, they are often delayed if the code is not ready yet. Python's development team monitors the state of the code by running a large unit test suite during development.[147]

The major academic conference on Python is PyCon. Also, there are special Python mentoring programs, such as PyLadies.

Naming

Python's name is inspired by the British comedy group Monty Python, whom Python creator Guido van Rossum enjoyed while developing the language. Monty Python references appear frequently in Python code and culture;[148] for example, the metasyntactic variables often used in Python literature are spam and eggs, rather than the traditional foo and bar.[148][149] Also, the official Python documentation contains various references to Monty Python routines.Script error: No such module "Footnotes".Script error: No such module "Check for unknown parameters".[150] Python users are sometimes referred to as "Pythonistas".[151]

Languages influenced by Python

See also

Script error: No such module "Portal".

Notes

Template:Notelist

References

<templatestyles src="Reflist/styles.css" />

  1. Script error: No such module "citation/CS1".
  2. Script error: No such module "citation/CS1".
  3. Script error: No such module "citation/CS1".
  4. Script error: No such module "citation/CS1".
  5. Script error: No such module "citation/CS1".
  6. Script error: No such module "citation/CS1". Updated as required.
  7. Script error: No such module "Citation/CS1".
  8. Script error: No such module "Citation/CS1".
  9. Script error: No such module "citation/CS1".
  10. a b Script error: No such module "citation/CS1".
  11. a b c Script error: No such module "citation/CS1".
  12. Script error: No such module "citation/CS1".
  13. Script error: No such module "citation/CS1".
  14. Script error: No such module "Citation/CS1".
  15. Script error: No such module "citation/CS1".
  16. Script error: No such module "citation/CS1".
  17. Script error: No such module "citation/CS1".
  18. Script error: No such module "citation/CS1".
  19. Script error: No such module "citation/CS1".
  20. Script error: No such module "citation/CS1".
  21. Script error: No such module "citation/CS1".
  22. Script error: No such module "citation/CS1".
  23. Script error: No such module "citation/CS1".
  24. Script error: No such module "citation/CS1".
  25. Script error: No such module "citation/CS1".
  26. Script error: No such module "citation/CS1".
  27. Script error: No such module "citation/CS1".
  28. Script error: No such module "citation/CS1".
  29. Script error: No such module "citation/CS1".
  30. Script error: No such module "citation/CS1".
  31. Script error: No such module "citation/CS1".
  32. Script error: No such module "citation/CS1".
  33. a b Script error: No such module "citation/CS1".
  34. Script error: No such module "citation/CS1".
  35. a b Script error: No such module "citation/CS1".
  36. Script error: No such module "citation/CS1".
  37. Script error: No such module "citation/CS1".
  38. Script error: No such module "citation/CS1".
  39. Script error: No such module "citation/CS1".
  40. Script error: No such module "citation/CS1".
  41. Script error: No such module "citation/CS1".
  42. Script error: No such module "citation/CS1".
  43. Script error: No such module "citation/CS1".
  44. a b Script error: No such module "citation/CS1".
  45. Script error: No such module "citation/CS1".
  46. Script error: No such module "citation/CS1".
  47. Script error: No such module "citation/CS1".
  48. Script error: No such module "citation/CS1".
  49. Script error: No such module "citation/CS1".
  50. Script error: No such module "citation/CS1".
  51. Script error: No such module "citation/CS1".
  52. a b Script error: No such module "citation/CS1".
  53. Script error: No such module "citation/CS1".
  54. Script error: No such module "citation/CS1".
  55. Script error: No such module "citation/CS1".
  56. Script error: No such module "citation/CS1".
  57. Script error: No such module "citation/CS1".
  58. Script error: No such module "citation/CS1".
  59. Script error: No such module "citation/CS1".
  60. Script error: No such module "citation/CS1".
  61. Script error: No such module "citation/CS1".
  62. Script error: No such module "citation/CS1".
  63. Script error: No such module "citation/CS1".
  64. Script error: No such module "citation/CS1".
  65. Script error: No such module "citation/CS1".
  66. a b Script error: No such module "citation/CS1".
  67. Script error: No such module "citation/CS1".
  68. Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
  69. Script error: No such module "citation/CS1".
  70. Script error: No such module "citation/CS1".
  71. Script error: No such module "citation/CS1".
  72. Script error: No such module "citation/CS1".
  73. Script error: No such module "citation/CS1".
  74. Script error: No such module "citation/CS1".
  75. Script error: No such module "citation/CS1".
  76. Script error: No such module "citation/CS1".
  77. a b Script error: No such module "citation/CS1".
  78. Script error: No such module "citation/CS1".
  79. Script error: No such module "citation/CS1".
  80. Script error: No such module "citation/CS1".
  81. Script error: No such module "citation/CS1".
  82. Script error: No such module "citation/CS1".
  83. a b Script error: No such module "citation/CS1".
  84. Script error: No such module "citation/CS1".
  85. Script error: No such module "citation/CS1".
  86. Script error: No such module "citation/CS1".
  87. Script error: No such module "citation/CS1".
  88. Script error: No such module "citation/CS1".
  89. Script error: No such module "citation/CS1".
  90. Script error: No such module "citation/CS1".
  91. a b Script error: No such module "citation/CS1".
  92. Script error: No such module "citation/CS1".
  93. Script error: No such module "citation/CS1".
  94. Script error: No such module "citation/CS1".
  95. Script error: No such module "citation/CS1".
  96. Script error: No such module "citation/CS1".
  97. Script error: No such module "citation/CS1".
  98. Script error: No such module "citation/CS1".
  99. Script error: No such module "citation/CS1".
  100. Script error: No such module "citation/CS1".
  101. Script error: No such module "citation/CS1".
  102. Script error: No such module "citation/CS1".
  103. Script error: No such module "citation/CS1".
  104. Script error: No such module "citation/CS1".
  105. Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
  106. a b c Script error: No such module "citation/CS1".
  107. Script error: No such module "citation/CS1".
  108. Script error: No such module "citation/CS1".
  109. Script error: No such module "citation/CS1".
  110. Script error: No such module "citation/CS1".
  111. Script error: No such module "citation/CS1".
  112. Script error: No such module "citation/CS1".
  113. Script error: No such module "citation/CS1".
  114. Script error: No such module "citation/CS1".
  115. Script error: No such module "citation/CS1".
  116. Script error: No such module "citation/CS1".
  117. Script error: No such module "citation/CS1".
  118. Script error: No such module "citation/CS1".
  119. Script error: No such module "citation/CS1".
  120. Script error: No such module "citation/CS1".
  121. Script error: No such module "citation/CS1".
  122. Script error: No such module "citation/CS1".
  123. Script error: No such module "citation/CS1".
  124. Script error: No such module "citation/CS1".
  125. Script error: No such module "citation/CS1".
  126. Script error: No such module "citation/CS1".
  127. Script error: No such module "Citation/CS1".
  128. Script error: No such module "citation/CS1".
  129. Script error: No such module "citation/CS1".
  130. Script error: No such module "citation/CS1".
  131. Script error: No such module "citation/CS1".
  132. Script error: No such module "citation/CS1".
  133. Script error: No such module "citation/CS1".
  134. Script error: No such module "citation/CS1".
  135. Script error: No such module "citation/CS1".
  136. Script error: No such module "citation/CS1".
  137. Script error: No such module "citation/CS1".
  138. a b Script error: No such module "citation/CS1".
  139. Script error: No such module "citation/CS1".
  140. Script error: No such module "citation/CS1".
  141. Script error: No such module "citation/CS1".
  142. Script error: No such module "citation/CS1".
  143. Script error: No such module "citation/CS1".
  144. Script error: No such module "citation/CS1".
  145. Script error: No such module "citation/CS1".
  146. a b Script error: No such module "citation/CS1".
  147. Script error: No such module "citation/CS1".
  148. a b Script error: No such module "citation/CS1".
  149. Script error: No such module "citation/CS1".
  150. Script error: No such module "citation/CS1".
  151. Script error: No such module "citation/CS1".
  152. Script error: No such module "citation/CS1".
  153. Script error: No such module "citation/CS1".
  154. Script error: No such module "citation/CS1".
  155. Script error: No such module "citation/CS1".
  156. Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
  157. Script error: No such module "citation/CS1".
  158. Script error: No such module "citation/CS1".
  159. Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
  160. Script error: No such module "citation/CS1".
  161. Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
  162. Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".

Cite error: <ref> tag with name "98-interview" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "AutoNT-1" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "classmix" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "effbot-call-by-object" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "AutoNT-2" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "AutoNT-3" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "AutoNT-4" defined in <references> is not used in prior text.

Cite error: <ref> tag with name "AutoNT-6" defined in <references> is not used in prior text.

Script error: No such module "Check for unknown parameters".

Sources

  • Script error: No such module "citation/CS1".
  • Script error: No such module "Citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".

Further reading

  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".

External links

Script error: No such module "Sister project links".Script error: No such module "Check for unknown parameters".

Script error: No such module "Navbox". Script error: No such module "Navbox". Script error: No such module "Navbox". Template:Differentiable computing Script error: No such module "Navbox". Script error: No such module "Navbox". Script error: No such module "Navbox". Script error: No such module "Authority control".