Talk:Python (programming language)/Archive 11: Difference between revisions

Revision as of 12:13, 29 June 2024

Latest revision as of 12:13, 18 July 2025

(3 intermediate revisions by the same user not shown)

Line 94:

{{od}} no complaints from me: the areas highlighted are things that I've tried to tackle over the years, but any technical article on here tends to backslid towards trivia and pointless nitpicking if not strictly watched. In particular, all of the bulleted syntax stuff should be relegated to the syntax sub-article if not removed entirely. [[User:Thumperward|Chris Cunningham (user:thumperward)]] ([[User talk:Thumperward|talk]]) 06:46, 2 February 2023 (UTC)

== Semi-protected edit request on 6 August 2023 ==

{{edit semi-protected|Python (programming language)|answered=yes}}

Update latest beta release version - Python 3.12 0rc1 has been released (2023-08-06) [[Special:Contributions/86.130.253.139|86.130.253.139]] ([[User talk:86.130.253.139|talk]]) 14:51, 6 August 2023 (UTC)

:[[File:Pictogram voting wait.svg|20px|link=|alt=]] '''Already done'''<!-- Template:ESp --> via Wikidata —&#8288;'''[[User:PlanetJuice|PlanetJuice]]''' ([[User talk:PlanetJuice|talk]] • [[Special:Contribs/PlanetJuice|contribs]]) 20:19, 6 August 2023 (UTC)

== What platforms can run Python applications? ==

It would be good to know on what platforms and version Python can run on in a table, eg Windows, macOS, linux, iOS, Android, ... The table would probably need an explanation of any specific tools needed (frameworks, compilers). Also whether packaged packaged apps can be built that can be distributed (eg app store) to users without users requiring anything else to be installed.

An explanation of how features unique to each platform can be accessed would be useful. [[User:FreeFlow99|FreeFlow99]] ([[User talk:FreeFlow99|talk]]) 16:59, 6 March 2024 (UTC)

== Climate change ==

This page should mention that programming languages like Python that are not compiled into native executable code (e.g., they are interpreted or compiled into byte code that is run in a virtual machine) require more processor cycles for the same results compared to native executables. Therefore they use more power to execute, and they contribute more to climate change. Given the ubiquity of Python, a vast amount of power is wasted on interpretation or byte-code execution. [[Special:Contributions/209.145.84.194|209.145.84.194]] ([[User talk:209.145.84.194|talk]]) 20:08, 28 March 2024 (UTC)

:Do you have a source which describes this? The correlation between interpreted languages and climate change is not something I have seen described before. —<span style="font-family:Poppins, Helvetica, Sans-serif;">[[User:Panamitsu|Panamitsu]]</span> [[User_talk:Panamitsu|(talk)]] 23:59, 28 March 2024 (UTC)

::I've seen this mentioned before (don't have any immediate links) and it probably has some validity. But, I agree with Panamitsu that to actually include this we need good sources (I think more than one unless it's a really solid one) that discuss this and do a pretty complete analysis. Since this isn't unique to Python and there are other tradeoffs beyond just how the final applications are run. [[User:Skynxnex|Skynxnex]] ([[User talk:Skynxnex|talk]]) 13:21, 29 March 2024 (UTC)

::I can find a few reliable sources which suggest that Python does indeed use much more energy for the same tasks when compared with compiled languages like C.<ref>{{cite journal |last1=Abdulsalam |first1=Sarah |last2=Lakomski |first2=Donna |last3=Gu |first3=Qijun |last4=Jin |first4=Tongdan |last5=Zong |first5=Ziliang |title=Program energy efficiency: The impact of language, compiler and implementation choices |journal=International Green Computing Conference |date=November 2014 |pages=1–6 |doi=10.1109/IGCC.2014.7039169}}</ref><ref>{{cite journal |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 |title=Ranking programming languages by energy efficiency |journal=Science of Computer Programming |date=May 2021 |volume=205 |pages=102609 |doi=10.1016/j.scico.2021.102609}}</ref><ref>{{cite journal |last1=Koedijk |first1=Lukas |last2=Oprescu |first2=Ana |title=Finding Significant Differences in the Energy Consumption when Comparing Programming Languages and Programs |date=June 2022 |pages=1–12 |doi=10.1109/ICT4S55073.2022.00012 |journal=2022 International Conference on ICT for Sustainability (ICT4S)}}</ref> However, I find no studies examining a link with climate change. This could be because demonstrating such causality would, I imagine, be very difficult. I do wonder what the impact of language choice is, though, relative to e.g. the total power draw of all electronics in a country—it might be an interesting exercise to estimate how many GW (or perhaps only MW?) could be saved in your country by rewriting all Python programs in C. — [[User:Jumbo T|Jumbo T]] ([[User talk:Jumbo T|talk]]) 13:27, 29 March 2024 (UTC)

::Even if true that interpreted or VM run Bytecode compiled languages require more processor cycles, then the proper place for that discussion would be on the pages for those execution environments rather than on specific languages pages. I would also like to see the citations for that. But creating a link to climate change is an additional leap that again would require evidence. It's quite possible that despite requiring more processor cycles to run similar code there are other features that make it more efficient in practice, or even that python is a more amenable language for the creation of control systems for products that combat or mitigate against climate change - to be clear, that is a hypothesis without evidence but it does caution against a simplistic narrative: Python -> Byte code -> more cycles -> worse for environment. [[User:Crispyhull|Chris]] ([[User talk:Crispyhull|talk]]) 09:06, 2 April 2024 (UTC)

{{reftalk}}

== Naming ==

Python is named so, because the (long) code of the language looks like a snake/python. [[Special:Contributions/49.37.96.186|49.37.96.186]] ([[User talk:49.37.96.186|talk]]) 15:06, 28 June 2024 (UTC)

:{{Not done}} You have not provided [[WP:V|verification]] from a [[WP:RS|reliable source]] for this claim. This appears to be [[WP:OR|original research]]. [[User:Peaceray|Peaceray]] ([[User talk:Peaceray|talk]]) 18:36, 28 June 2024 (UTC)

== Disambiguation addition ==

So there are 2 articles. 1 is about a TLD and the 2nd one is a redirect to this article. I was wondering if I should redirect users to the [[PYC]] Disambiguation page. Please drop a opinion! [[User:Robloxguest3|Robloxguest3]] ([[User talk:Robloxguest3|talk]]) 00:45, 18 August 2024 (UTC)

:<small>I had reverted the addition of the hatnote since I didn't immediately think it was undue for the TLD ({{-r|.рус}}, which is actually made up of characters from {{slink|Cyrillic_script_in_Unicode#Basic_Cyrillic_alphabet}}).</small>

:I agree that it is/was difficult to get to the TLD articles since if a user types the latin ".pyc" you only see {{-r|.pyc}}, which is a redirect to this article. Just now the state was changed so that the latin .pyc has been retargeted to the TLD and the TLD has a hatnote added linking to the programming language. [[User:Skynxnex|Skynxnex]] ([[User talk:Skynxnex|talk]]) 14:57, 18 August 2024 (UTC)

::''Yeah I did that I think''. I kinda forgot if I did or not, but I'm pretty sure I did. '''Thanks for your reply!''' [[User:Robloxguest3|Robloxguest3]] ([[User talk:Robloxguest3|talk]]) 18:57, 18 August 2024 (UTC)

==Wiki Education assignment: Introduction to Technical Writing==

{{dashboard.wikiedu.org assignment | course = Wikipedia:Wiki_Ed/CSU_Los_Angeles/Introduction_to_Technical_Writing_(Fall_2024) | assignments = [[User:Christianjgarcia|Christianjgarcia]] | start_date = 2024-08-13 | end_date = 2024-12-17 }}

<span class="wikied-assignment" style="font-size:85%;">— Assignment last updated by [[User:Christianjgarcia|Christianjgarcia]] ([[User talk:Christianjgarcia|talk]]) 17:22, 2 October 2024 (UTC)</span>

== Ease of Learning ==

{{Inappropriate comment

|action=tag over

|reason=[[WP:TALK#PROPOSE]]

|comment=

Python is often considered one of the easiest programming languages to learn, making it accessible to people of all ages. Its simple, readable syntax emphasizes clarity, allowing beginners to quickly grasp fundamental programming concepts without being overwhelmed by complex rules. Even children can learn Python, thanks to its straightforward design and beginner-friendly resources. The language encourages an interactive learning experience, where users can immediately test and run code in a simple way, making it ideal for newcomers to programming.

Python's clean and consistent syntax reduces the learning curve, enabling new programmers to focus on solving problems rather than struggling with complicated syntax rules. This simplicity, combined with its powerful capabilities, makes Python an excellent choice for people who are just starting to learn coding. [[User:JadPythonWiki|JadPythonWiki]] ([[User talk:JadPythonWiki|talk]]) 15:44, 16 December 2024 (UTC)

}}

:{{Not done unclear}} Merely pasting text onto a talk page will not get anything done. Is this a change that you want to see incorporated into the article? Please be specific about the change(s) that you want. [[User:Peaceray|Peaceray]] ([[User talk:Peaceray|talk]]) 17:10, 16 December 2024 (UTC)

== Syntax for Beginners ==

{{Inappropriate comment

|action=tag over

|reason=[[WP:TALK#PROPOSE]]

|comment=

Python's syntax is designed to be simple and easy to read, contributing to its popularity as an introductory programming language. Some key features of Python's syntax include:

* '''Print Function''': Python uses the <code>print()</code> function to output data to the console. Unlike many languages, Python does not require semicolons at the end of statements, making it more readable.

* '''Variable Assignment''': Python is dynamically typed, meaning variables are assigned values directly without the need to declare their type. The type is inferred based on the assigned value. Example: <code>name = "JadPythonWiki"</code>

* '''Indentation''': Python uses indentation, rather than braces <code>{}</code>, to define blocks of code. Indentation must be consistent to avoid errors, making Python code clean and readable.

* '''Input''': Python uses the <code>input()</code> function to receive user input. By default, the input is returned as a string, which can be converted to other types if necessary.

* '''Comments''': Python supports single-line comments, which begin with the <code>#</code> symbol. Comments are ignored by the interpreter and are used to document the code.

* '''Function Definition''': Functions in Python are defined using the <code>def</code> keyword, followed by the function name and parameters in parentheses. Python functions can return values using the <code>return</code> statement.

[[User:JadPythonWiki|JadPythonWiki]] ([[User talk:JadPythonWiki|talk]]) 15:53, 16 December 2024 (UTC)

}}

:{{Not done unclear}} Merely pasting text onto a talk page will not get anything done. Is this a change that you want to see incorporated into the article? Please be specific about the change(s) that you want. [[User:Peaceray|Peaceray]] ([[User talk:Peaceray|talk]]) 17:10, 16 December 2024 (UTC)