Wikipedia:Peer review/Python (programming language)/archive1: Difference between revisions

Content deleted Content added
No edit summary
Legobot (talk | contribs)
m Bot: Fixing lint errors, replacing obsolete HTML tags: <tt> (1x)
 
(One intermediate revision by one other user not shown)
Line 6:
* A script has been used to generate a semi-[[User:AndyZ/peerreviewer|automated]] review of the article for issues relating to grammar and [[WP:MOS|house]] style; it can be found on the [[Wikipedia:Peer review/Automated/February 2009#Python (programming language)|automated peer review page]] for February 2009. [[Category:Peer review pages with semiautomated peer reviews]]
**[[Image:Yes check.svg|20px]] Issues from automated review now fixed. --[[User:Cybercobra|Cybercobra]] ([[User talk:Cybercobra|talk]]) 09:05, 19 February 2009 (UTC)
'''This peer review discussion has been closed.'''<br/> <noinclude>[[Category:March 2009 peer reviews]]</noinclude>
{{Peer review page|topic=engtech}}
I've listed this article for peer review because I think the article is of high quality and hope to see it progress to a Featured Article eventually. And since peer review is one of the steps on the way to a FA, I'm requesting it.
 
Line 24:
There are a lot of statements of intent and goals: Python is intended to be flexible, easy to learn, easily extensible, simple, etc. It seems to me that someone somewhere has to have studied whether these are actually ''accomplished''. Have there been any studies on (say) students learning Python, on whether it is actually easier to learn? It's nice to talk about design goals, but they're ''all over'' this article.
 
Some statements are made which sound like Python advocacy, and which are sourced to documents at <ttcode>python.org</ttcode>. Example:
 
:Python requires less boilerplate than traditional statically-typed structured languages such as C or Pascal, and has a smaller number of syntactic exceptions and special cases than either of these.