Content deleted Content added
MiszaBot I (talk | contribs) m Archiving 1 thread(s) from Talk:Python (programming language). (ARCHIVE FULL) |
m Replaced deprecated <source> tags with <syntaxhighlight> (via WP:JWB) |
||
| (2 intermediate revisions by one other user not shown) | |||
Line 22:
This really doesn't belong in the "Implementations" section. Not sure if the new-ish user who reverted it there is the same as the IP who added it a couple days ago. In any case, Cython (and Pyrex) are ''different'' languages than Python and are ''not'' implementations. It's true that there is an intersection between the valid Cython programs and the valid Python programs, but there is a considerable disjunction on both sides too.
Probably equally important is that Cython is still a quite experimental language, not something in widespread use. We've seen lots of real Python implementations come and go over the years (Vyper, Prothon, etc). Some new effort, however well meaning and useful it might be, should find a notable audience and user base before being listed here. In truth, I think that Stackless is slightly borderline for where it is mentioned, but it was at least for a while pretty widely used, so inclusion is plausible.
== Guido's last name ==
Line 34:
: It is proper English style to capitalize the surname prefix if the name is used without the first name. Not only is this properly described in Van Rossum's webpage, but also the correct practice in his Wikipedia article. [[User:Kbrose|Kbrose]] ([[User talk:Kbrose|talk]]) 22:17, 20 October 2008 (UTC)
::Guido's homepage seems to confirm the cap-if-used alone "Van Rossum" spelling. However, of greater relevance is finding the right part of [[WP:STYLE]] for this issue. I don't know anything about Dutch orthography personally, but I presume this isn't the only Dutch name WP has ever wanted to describe. What's the rule?
::: Looking up Wikipedia [[Van_(Dutch)]], it seems that we should write "Van Rossum", and "Guido van Rossum". But I do not know if this rule applies to the english language. [[User:0x6adb015|0x6adb015]] ([[User talk:0x6adb015|talk]]) 13:00, 21 October 2008 (UTC)
::::IMHO to follow native style is proper form, unless of course the owner of the term wishes it otherwise. Thus a Dutch name would follow Dutch traditional style, etc. Only exception comes when we need to romanize a term, in which case it would be good form to parenthetically include the native script as well. <small>yamaplos 16:58, 31 October 2008 (UTC)</small>
Line 69:
Yes, I see the NoMoreLinks tag, but the wording there is 'consider carefully
:I don't care about the procedural stuff about who added or removed the link. However, I think the Python tutorial pushes us in the direction of linkspam, and is better omitted. There are many excellent pages at the official Python website; which is why it's good to give a single one for the home of that site, and let readers navigate to what they want. Linking to each "nice to have" page at Python.org is unnecessary... moreover, it's not even like the official tutorial is the only ''very good'' tutorial on Python. If that's what readers want, I'm sure Google could help them search for "Python tutorial" and give them many good choices.
::Fair enough. I agree with being careful of linkspam. In which case should the link to 'Official documentation and resources' also be removed? [[User:Peterl|peterl]] ([[User talk:Peterl|talk]]) 23:20, 20 November 2008 (UTC)
Line 81:
--[[Special:Contributions/190.161.73.209|190.161.73.209]] ([[User talk:190.161.73.209|talk]]) 21:21, 24 November 2008 (UTC)
: You have item three [http://www.askoxford.com/concise_oed/philosophy?view=uk here] that might fit. the use of the word. --[[User:Paddy3118|Paddy]] ([[User talk:Paddy3118|talk]]) 07:15, 25 November 2008 (UTC)
:: I managed to earn a doctorate in philosophy without actually learning anything that would suggest the usage of the word in this article is inappropriate. Just saying.
== Syntax box ==
It seems that the colored syntax box PNG-equivalent is wrongly rendered; the PNG is missing some variable that shows OK when looking at the SVG. Anybody knows how to fix that?
[[User:0x6adb015|0x6adb015]] ([[User talk:0x6adb015|talk]]) 14:24, 3 February 2009 (UTC)
:Works fine in every Firefox version I've looked at it in (which is quite a few, since I've watched the article for years, and provided the original syntax-highlight example... someone else converted my PNG to SVG). I think something is weird in your individual system setup.
:Scratch that, I lied! I just zoomed into the actual SVG in its image page, and I also get weird drop-outs in FF. Tried it in Safari, where it renders fine. I wonder if this is a glitch with ''new'' FF versions. I'm thinking that going back to the PNG might be reasonable for a while.
{{Talk:Python (programming language)/GA1}}
Line 134:
The point wasn't that it was awesome python code, rather that it mocks a code example from Ruby's website with their silly perl-esq sigils and magical behavior.
<
# Python knows what you mean, even if you want to do math on an entire set
cities = set(("""London
Line 146:
print ( "I still need to visit the following cities: "
+ ", ".join(cities - visited) )
</syntaxhighlight>
<
# Ruby knows what you
# mean, even if you
Line 163:
"following cities:",
cities - visited
</syntaxhighlight>
Granted the python example would look nicer with the set literal syntax a la 3.0.
Line 189:
Would it be possible for someone who knows a little more about such things to provide some sort of commentary about the changes between the 2.x and 3.x versions of Python? I came over here hoping for a neat summary of the kind Wikipedia is good at, and was unable to find one. [[User:Meand|me_and]] ([[User talk:Meand|talk]]) 20:54, 28 June 2009 (UTC)
:Sounds like the article you are looking for is [[History of the Python programming language]]. That one is linked at top of the relevant section in this article already.
== Python award ==
Line 218:
Python has changed ''throughout'' its life, not just at its inception. --[[User:Paddy3118|Paddy]] ([[User talk:Paddy3118|talk]]) 18:08, 23 November 2009 (UTC)
:There are features of Python (or of most languages) that were not present in the first release. In the Java case, I think the usual example given is the use of Python decorators, which borrow a syntax element from Java. I'm not really convinced that that is enough to merit mentioning Java in the infobox. However, it is sophistical to suppose that influence must only follow the release dates of version 1.0 of every language... many languages influence each other on an ongoing basis, across multiple versions.
::Personally, the best example I know of is the <code>logging</code> module, which is very much a clone of the equivalent Java library. --[[User:Cybercobra|<b
:::That's true. And actually, the unit test module is also based on Java's. And probably another thing or two. And Guido used Java as a the model for Unicode, especially in 3.x. So I guess I don't really object to the inclusion of Java as an influence in the infobox.
::::I'll concede all that, but it seems that we're setting the "Influenced by" bar pretty low, and it's a bit odd seeing Java alongside Modula-3 as a Python influence. It's a fundamental problem with infoboxes (and templates, and categories) - information is presented in a binary format, with no explanation. Anyway, I'll let it pass. [[User:Peter Ballard|Peter Ballard]] ([[User talk:Peter Ballard|talk]]) 23:55, 23 November 2009 (UTC)
:::::I don't feel that strongly in favour of including Java as an influence. I just don't want to remove it on the specious argument that Python 1.0 preceded Java 1.0, so no influence is possible. If you want to present a better focused argument for why the Java influence is insufficient to merit the infobox, I'm open minded.
::::::I would leave Java in, on the strength of it influencing the change in the handling of Unicode. --[[User:Paddy3118|Paddy]] ([[User talk:Paddy3118|talk]]) 05:22, 24 November 2009 (UTC)
Line 241:
Boolean operators and Boolean built-in types always return one of the Boolean values True and False ''except'' for the operators "<code>or</code>" and "<code>and</code>" which return one of their operands (from left to right, the first operand that determines the Boolean value of the expression).<ref>{{cite web| title=Boolean operations | url=http://docs.python.org/ref/Booleans.html}}</ref>
<
>>> class spam: pass # spam is assigned a class object.
...
Line 254:
<class __main__.spam at 0x01292660>
>>>
</syntaxhighlight>
----
----
| |||