Talk:Python (programming language)/Archive 5

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Archive 4 Archive 5 Archive 6

POV issues

There's a whole bunch of statements in this article that are dubious from a POV perspective, and some which are probably unverifiable. Most of them are vague peacock praise for Python that doesn't provide any actual evidence. I'm grouping the whole lot under POV because it comes down to people not being sufficiently careful about writing in a neutral style. It needs careful triage and editing, and would probably benefit from attention by editors who are not programmers at all and knows nothing about python (most of this is not specialist stuff, just statements that don't even pretend to be factual information, and it's easier to spot those if you aren't involved).

Things I spotted offhand, without really looking hard (intended as examples, not an exhaustive list of stuff to fix):

  1. The philosophy behind Python is noteworthy among high-level programming languages

    Peacock phrase. "noteworthy" is an opinion, not a fact
  2. The majority of Python's major features were present in this initial release

    Groan-worthy phrasing, and "major features" is at best unsourced, but sounds like an opinion to me - what makes those features major?
  3. The Python programming language is actively used in industry and academia for a wide variety of purposes.

    Another peacock statement. Used by whom? For what purposes? There's a short list, but that doesn't substantiate "wide variety" and this statement adds no useful information to the article.
  4. It aims toward an uncluttered visual layout, uses English keywords frequently where other languages use punctuation, and has notably fewer syntactic constructions than many structured languages such as C, Perl, or Pascal.

    Unsourced, and probably unverifiable - the decision of how to count "syntactic constructions" is essentially arbitrary. The reader can't learn anything much from this sentence.
  5. This is a boon for those learning the language and experienced developers alike

    Poetic, grandiose... peacock.
  6. As well, the Python shell is often used to interactively perform system tasks, such as modifying files.

    Unverifiable and mostly meaningless statement.
  7. The codebase is written in compliant C89[26], and is thus easily portable to most operating systems, especially POSIX-compliant or Unix-like operating systems.

    The second part of this statement is unsourced, largely because it's wrong - merely writing something in compliant C89 does not make it "easily portable to most operating systems", even if you can agree on what qualifies as "most operating systems".
  8. Several other experimental implementations have been created, but have not yet been widely adopted.

    Vague, unsourced, no useful information content.

I don't have the energy to fix this thing right now, so tagging POV-check. There's almost certainly more than I've listed here. Careful review is needed to find all the ones I didn't. Asuffield 09:54, 18 February 2007 (UTC)

Rewritten 1 and 2, removed 3, tagged 4 (this is a stated goal in the philosophy which needs linked), removed 5, rewritten 6 and 7, removed 8. Thanks. Chris Cunningham 16:02, 18 February 2007 (UTC)

avoiding naming collisions

This is not about the article itself, so to keep in line with wikipedia policy, I posted the question here instead. If anyone is watching this, pls help if you can. pls don't bite the noob. Thanks. NoClutter 17:39, 28 February 2007 (UTC)


At the moment, the article uses a hodge-podge if -ise and -ize spellings. This should be made consistent. The question is, which way? Python's style guides don't specify, and it's used on both sides of the Atlantic. So it seems to depend on which editor actually does the task. If I do it, I will move towards -ise spellings, but I will not complain if someone goes ahead and makes it all use -ize before I do this. I'll do it tomorrow, providing no-one beats me to the punch or provides a strong argument otherwise. 21:07, 16 March 2007 (UTC)

Also, it's Random Useless Statistic Time: there are 3 genuine -ize/ization/izing words, versus 7 genuine -ise/isation/ising words in the current version. Make of that what you will. 21:21, 16 March 2007 (UTC)
Yes, but four of those are variants of "optimise" in a single paragraph, and there are two -ized/izes words you may have missed :p. FWIW, the Python documentation heavily prefers American spellings, except for a few modules in the standard library. But I don't feel strongly about it. — Miles (Talk) 02:13, 17 March 2007 (UTC)

<references /> columns

Unfortunately, it is not only low screen resolutions affected by this. If I were to try to print this article with two columns of references with full-size text (hey, reading a too-small printout is awful!), with some only marginally longer than average URLs, they bleed into the next column too. (On Firefox at least, this can be simulated by clicking the 'Printable version' link in the toolbox, and selecting File -> Print preview. At 100% text size, it happens on several URLs, and even at 70% (which, IMHO, is about the minimum size that's actually usable for me), there's one link that spills over.)

Seeing as this has been changed twice in the past few days, I'm taking this to talk to solicit feedback and rationales. Ideally, there'd be some magical template that can detect the screen width being used, and automatically compute the width needed for its reference list, but as far as I know there's no such thing. Abednigo 16:02, 29 March 2007 (UTC)


I think the two should be cross referenced (each link the other) and have the main page perhaps mention other language implementations. ...or perhaps have translations in various languages. But if there be too much content, the folks won't read. The article is already long and mentioning every possible fact has to be balanced against the possibility of loosing readers. Mention, cross link, but do not merge. opinion. Larry 08:48, 15 April 2007 (UTC)

DO NOT MERGE I have same opinion as Larry. Also note that ChinesePython page is using non roman scripts, it's another drawback.Vivek 10:30, 1 May 2007 (UTC)

Thoughts on reference

Someone added:

  • Computing in Science & Engineering, a peer-reviewed technical magazine, recently devoted a special issue to Python.

It seems fairly relevant, but the link is a to a collection of "give us money" links to read the actual content. I'm inclined to think such a list of commercial content falls under "advertising", and we should leave it out. LotLE×talk 15:31, 8 May 2007 (UTC)

Even worse, the link is now dead. I've removed it. --AdamGomaa 11:41, 6 July 2007 (UTC)

List of IDEs (where?)

An anonymous editor added the below list of IDEs. Such a list feels like a worthwhile resource, but it equally feels out of place here (especially tacked on after all the footnotes and external references. Anyone have an idea where this list might better live? LotLE×talk 15:09, 29 May 2007 (UTC)

Python IDEs and GUI Builders

Some more:

When we are at it, if we add the list to the article (and I hope we will), we should definitely mention that a lot of Python developers (me at least) use a normal text editor (maybe with some extra features like auto-indentation and syntax highlighting), run their code and other tools (version control, for example) via command line and use the interactive python shell (or, IPython, the enhanced frontend) for discovering (Code completion!) and testing (interactive, right?) commands. -- (talk) 17:26, 30 December 2007 (UTC)


Can we add Groovy to the list? —Preceding unsigned comment added by (talk)

Certainly (and done): the article already mentions it. --Piet Delport 20:25, 11 June 2007 (UTC)

Python is an imperative programmin language?

Like Perl and PHP. Python is an aimperative programming languge. So we should add it to the imperative languages Category ? --- Fırat KÜÇÜK 11:44, 8 July 2007 (UTC)

Shed Skin

I'm concerned about the mention of Shed Skin in the derived languages/implementations section. My main concern is that this project is early-alpha, and I have real doubts it yet merits inclusion in the Python article. Lots of folks have tried interesting things, but I'm not convinced this one will have legs (more power to it if it does; I said the same thing of Vyper back in 2000 though, magic bullets come and go).

But in particular, the claim about being much, much faster than Psyco seems contentious to me. Someone added a citation, but that citation was to the project creator's site, with no obvious benchmarks or methodology given there, just a general claim. Lies, damned lies, and benchmarks... as they say. Except there aren't even any specific benchmarks to point to. LotLE×talk 05:18, 9 July 2007 (UTC)

Here was the version I made more neutral:

Shed Skin is an experimental compiler that can translate smallish, statically typed programs into C++. When it works the obtained speedup is typically much larger than when using Psyco. [1]

"Limited functional"

The addition about Python lacking anonymous closures is rather odd. In any common sense, of course Python has anonymous closures, e.g.:

>>> (lambda x: lambda y: x*y)   # A function that returns a closure   
<function <lambda> at 0x12b00f0>
>>> (lambda x: lambda y: x*y)(3)  # A closure on x=3
<function <lambda> at 0x1318170>
>>> (lambda x: lambda y: x*y)(3)(5)

Actually, I'm thinking of taking out the tail-call elimination thing too. There's a decorator at the online Python cookbook to do exactly that ( Yes it's external code, but the fact it's so relatively simple to do makes the point correct in only the most contorted and pedantic sense. LotLE×talk 18:09, 20 July 2007 (UTC)

Please note that the previous version called it "multi-expression anonymous closures", which Python does not support. lambdas are only a single statement (which is how the article probably should read). There is no way to encode, eg:
def foo():
    if bar:
        while baz:
using a single lambda (or if there is, it's too hacky to even contemplate). —Preceding unsigned comment added by (talk) 2007-07-20 19:13:27
But of course that block statement can be replaced with an equivalent single expression by using boolean shortcutting. I won't argue that it is non-hacky... however, given I've published some widely read articles on "FP in Python" that show the details, it clearly has been contemplated. Actually, using the new ternary if in Python 2.5, it's not even unnatural: e.g., qux() if bar else spam().
Moreover, in Lisp (which is used as the "baseline") every program is a single expression (or close enough for these purposes). Making a statement so convoluted as to actually be true is nearly impractical for what you are trying to put in this article: e.g. "Multi-expression anonymous closures that don't use hackish boolean shortcutting and that work in Python versions <2.5". Claims that are kinda-sorta true, in principle, with sufficient caveats and exceptions, aren't good stuff for a WP article. LotLE×talk 20:55, 20 July 2007 (UTC)
Agreed; the details are finicky and particular, and don't improve the paragraph. I think "offers limited support for functional programming [...]" is a sufficient summarization for the context. —Piet Delport 02:07, 21 July 2007 (UTC)
I disagree with the assertion that "the fact it's so relatively simple to do makes the point correct in only the most contorted and pedantic sense." At least in the sense that recursion is, IMO, a major part of functional programming. I'm sure the example you noted could be used to write primitives for higher order functions, but it isn't very elegant. I may be misunderstaning your point, but I could just as easily argue that Scheme has support for objects, because 1% of the users wrote object systems. (actually I think this argument is more convincing because object systems don't require any major implementation/compiler changes). I use functional programming in a perl proejct, though with great tedium, and I don't see how it would be substantially different in python.
I was not the person who wrote the subject statement though, keep in mind. —Preceding unsigned comment added by (talk) 23:34, 21 May 2008 (UTC)

No Strengths vs Weaknesses or Criticisim Topic

Some programming language articles have a Strengths vs Weaknesses or Criticisim Topic which I think many readers find helpful in comparing different languages and understanding why one language is better than another for a particular application or program implementation. I realize this might be a sensitive issue but think the added content would be helpful. Wam067 07:30, 25 July 2007 (UTC)

Criticism sections are generally disfavored per WP style guidelines and neutrality policy. (See e.g., WP:NPOV#Article_structure). Despite this, sometimes sections dealing with general review and critique are considered acceptable, at least by some (See e.g., Xml#Critique_of_XML).
The problem with putting these sections into a programming language article is it invites partisanship, because few people universally agree on what makes one language "better than another". Indeed, most programming languages in popular use today evolved because someone considered the closest alternative language to be unacceptable, so they designed something new. Consequently, the definition of "better" is subject to dispute.
You might also want to consult Comparison of programming languages. See also [1], [2]. dr.ef.tymac 08:17, 25 July 2007 (UTC)

Criticism is fine, as long as it is balanced, not original research, and attributable to a reliable source: you can't go and write down your own opinions. —Piet Delport 13:53, 25 July 2007 (UTC)

Readability vs. Speed and Expressiveness

Nowhere in the executive summary is Python said to value readability at the expense of speed or expressiveness. I assume the original author of that sentence considered the summary to have inferred such a philosophy, which is not factually supported. Changing this about a bit. Reb42 05:53, 28 July 2007 (UTC)

Python 3 article merge

Any interested editors, please see Talk:Python 3: i'm looking for consensus on what to do with that article. —Piet Delport 05:00, 29 July 2007 (UTC)

Better code example?

I think we should update the sidebar image labeled "Syntax-highlighted Python code" with something a little more Pythonic. The example reads more like Java or C# ported to Python than like something written in Python. For example, it uses isinstance() rather than duck-typing; and uses a getter. I don't have the means of generating this, or else I'd volunteer. Terry Carroll 21:45, 17 August 2007 (UTC)

For the sake of posterity, I'm referring to this image: Python add5 syntax.svg Terry Carroll 21:50, 17 August 2007 (UTC)

I can assure you that I wrote that code in Python (and moreover, isinstance() really is the way to do what it does). And as someone who's never written a line of C#, only a moderate number in Java, and wrote a book about Python. Duck typing is nice enough... but when you are examining a multi-typed value returned from a specific standard-library module, there's no sense of asking if the value "quacks like a duck". LotLE×talk 00:50, 18 August 2007 (UTC)
Oh yeah, and what the heck would you use in place of .get()? You could wrap an ugly try/except, but that would be verbose and hard to read:
  label = symbol.sym_name[int(ast[0])]
except KeyError:
  label = ast[0]
Do you really want to avoid a perfectly good method, .get()? (There is a bit clever way to do this in Python 2.5 and DefaultDict, but that's sneaky, and newer than my code sample.LotLE×talk 01:01, 18 August 2007 (UTC)
I would also vote for providing more "pythonic" code, the current one (add5) even does not follow python coding standards. Mykhal 20:40, 13 September 2007 (UTC)
.. maybe the code could use the default ID(L)E highlighting. What about something like this ?
.. I know I could use the with statement, but that could be somewhat confusing
Mykhal 11:46, 8 November 2007 (UTC)
What is the copyright status on that image? And why isn't it uploaded to WP? Also, can you create an image that doesn't have such an ugly and thin looking font? LotLE×talk 20:03, 8 November 2007 (UTC)
The copyright is for now all rights reserved :) - it's just a proposal. here is the updated version (note that in there was a bug) with the larger font. Mykhal 22:32, 8 November 2007 (UTC)
Looks better, what about an SVG version like the old code? LotLE×talk 04:27, 9 November 2007 (UTC)
That's a much better, clearer code example than what we've got. rspeer / ɹəədsɹ 05:49, 9 November 2007 (UTC)
I think there should be some more discussion, my code is not absolutely OK, because I do not close the file explicitly. I think the final code should be short, using good programming practices, and exposing several nice python features/syntax. The final image/svg then may would look nicer using some light on dark scheme, like this.. Here it is in text format:
import sys

def list_file(fname):
    """Prints the file content,
    with the line numbers prepended"""
        f = open(fname)
        sys.exit("Error opening file %s" % fname)
    # the numbering may be done
    # better with enumerate()
    lineno = 1
    for line in f:
        print str(lineno)+':', line.rstrip('\n')
        lineno += 1

if len(sys.argv) != 2:
    sys.exit('Incorrect number of arguments')
filename = sys.argv[1]
Mykhal 11:51, 9 November 2007 (UTC)

Bare references

These look really ugly. I like that the article uses the footnote references, but each one should have a meaningful name (probably the actual title of the linked document) rather than just a URL. Readers looking at the footnotes shouldn't need to jump back and forth or guess why a certain URL is used.

I know you're all thinking that I should therefore clean it up. True enough, but I invite any help that might be offered in the project :-). LotLE×talk 02:50, 19 August 2007 (UTC)

Too much bibliography

There are too many, and too quickly growing, books listed in the external references. Moreover, even at too many, only about 1/4 of the available titles are listed. There's no particular logic to what is there or not there, other than "some editor liked that particular book".

What I would very strongly prefer is leaving in those titles that are freely available electronically, and removing all of those that are not. There is absolutely nothing wrong with buying a commercial title on nicely bound paper... but WP ain't a book review or recommendation site either. Book buyers can browse their local or online stores. What sayeth others? LotLE×talk 07:32, 3 September 2007 (UTC)

I concur. We cannot list all, so those complete books that are available freely seems reasonable.
What, however, happens after Py3K is released; when it could be argued that those free books based on pre-Py3k are inappropriate? --Paddy 08:16, 3 September 2007 (UTC)
There will be parallel maintenance and (minor) updates of the 2.x series for at least two years after the release of 3.0. So we have a while to worry about that issue. LotLE×talk 19:14, 3 September 2007 (UTC)

Afd on Python philosophy

Readers of the general Python article might be interested to notice that the child article Python philosophy was nominated on AfD at Wikipedia:Articles for deletion/Python philosophy. Please opine there if you have something to contribute. Thanks. LotLE×talk 05:39, 16 October 2007 (UTC)

Criticism, redux

I just removed the very recently added Criticism section from the article. I'm putting it here, in the hope that we can distil some useful additions to the article.


  • Python OO is often considered non-native to the language by OO purists as class member functions force the user to have self as its first parameter, in a similar way to Perl. Also, instance variables within a member function also need to be accessed always through self, leading to much more verbose (and often hard to read) code. Other OO languages such as C++, D, Ruby, etc. consider self implicit, force the use of accessors or use sigils for this.


A discussion of Python's treatment of 'self' is already in the article, in more NPOV terms. Redundant.


  • Python was originally born as an OO language where its built-in classes could not be modified. While much of this problem was addressed in 2.2, most of the standard library has not been updated to try to take advantage of this. Modification of built-in classes within the Python community is still perceived as dangerous.


Discussed in the History section, though not in as much depth (of opinion as well as of detail). Perhaps could be worked in there.


  • Lack of native regular expressions syntax like Perl or Ruby forces code involving them to be more verbose than in those languages.


A criticism of the standard library, not of the language itself. If there is a solid reference for this, it should be but in the 'Philosophy' section, after the part about Python's core-language minimalism.


  • Use of indentation is often a problem when sharing code through Internet forms or other methods that do not respect indentation. Even cutting and pasting code from other python sources where the tabulation level is different can often require careful editing to avoid syntax or subtle logic errors.


Covered in depth both in this article and in Python syntax. Redundant.


  • Use of indentation and the need to use modules for several basic operations makes Python often not that well suited for one-liners as sed, awk, Ruby or Perl are for system administrators.


See above, though I don't think this is mentioned explicitly. This is a fair point, so perhaps should be added to Python syntax. Actually, isn't there something about Python golf, and how it specifically doesn't work, already?


  • Tuples are often considered an unneeded addition to the language as lists provide a similar functionality. Alternatively, the immutability of tuples not being available to other primitives is also perceived as an inconsistency in the language.


Infested with weasel words. Stripped of these, the argument is: "Tuples are just immutable lists and thus not needed. Their immutability is inconsistant with other built-in types." The first part is sometimes brought up on, and is sometimes dispatched by Pythonistas using arguments such as tuples not being lists, but being records (a la Pascal); and lists being unsuitable for use as dictionary keys. A mention (again in Python syntax) of this could be good. The latter part is simply wrong (cf str, frozenset).

But, without cites, all this is moot. I don't have the time right now to cite any of the potentially valid addendums I've just rooted out, so I'm leaving them here for an interested editor to quest for. 17:02, 9 November 2007 (UTC)

These sort of rambling WP:OR violations definitely have no place in a PL article. In fact, "Criticism" sections almost never have any place in any article. It is a foolish and false sense of "balance" that seems to encourage some readers to put in random insults of a topic, as if that presented "both sides" of an already neutral article. I am definitely strongly opposed to any criticism section, even one that were written far better than this thankfully deleted one. LotLE×talk 17:45, 9 November 2007 (UTC)


  • Methods on objects are functions attached to the object's class; the syntax instance.method(argument) is, for normal methods and functions, syntactic sugar for Class.method(instance, argument). Python methods have an explicit self parameter to access instance data, in contrast to the implicit self in some other object-oriented programming languages (for example, Java, C++ or Ruby).


This is not really true of Ruby. Instance attributes in Ruby must be accessed with a special scoping sigil and can not be accessed with a self. Instance methods may be accessed without an explicit self but only those that are already defined and not the ones that will be defined at some future point in time (and meta programming is often used in Ruby so the explicit self become necessary).

None of this is relevant to a discussion about Python so keeping Ruby as an example only leads to missinformation. I'll be removing it unless someone can see a reason it has to stay. —Preceding unsigned comment added by Het (talkcontribs) 05:43, 30 January 2008 (UTC)

Typical Tunnel Vision Problem

A long article. The work that went it to it is evident. Commendable! So please take my criticism to heart without losing heart.

As with many expert type articles, this articles suffers from an overly narrow view of its customers. One almost gets the idea it is written exclusively for the same group of enthusiasts as are doing the writing! The article would certainly benefit by a step back from this notion of the readership. For instance, the target readership should be expanded to include (at least) people with experience programming in any other language, but explicitly lacking Python background.

A simple example to show what I mean: Right at the start, I'd like to see an answer to the question "Why Python?", i.e., what types of applications Python is especially designed to handle, and why it is better at these problems than other languages. (This information would be much more relevant to the stranger to Python than, for instance, cute anecdotes about a founder nominating himself as dictator for life.) In the same context, I'd also expect guidance as to what type of problems Python is not well adapted to dealing with (that is, less well adapted than other languages). Together, these define the relevant user group.

Philopedia (talk) 17:05, 16 November 2007 (UTC)

Any simple story about what Python is/is not good at very quickly strays into improper advocacy. I suppose a small number of well cited details would be OK. But this article does a much better job than many PL articles of avoiding that advocacy... I don't want to make it worse for what seems to me to be an ill-defined purpose.
It seems OK to observe "Python has construct X (while PL Foo does not)", but not to further claim X is better/worse than other languages' approximations. However, that has the problem that there are thousands of languages in which construct X does or does not exist. A comparison with a particular PL might seem "obvious" to users of that particular other language (e.g. Perl vs. Python), but not to the users of all the other PLs. What the article does now is much better: just list features of Python w/o trying to compare to every other option, nor to heap praise or blame on each feature. LotLE×talk 19:25, 16 November 2007 (UTC)