Python标准化：维基百科条目 [英] Python Standardization: Wikipedia entry
问题描述
我会重视那些同样为维基百科贡献的Pythoneers的观点，关于是否是Python标准化的问题。
特别是在上下文中此表：
http://en.wikipedia.org/wiki /Compari...ral_comparison
（编程语言比较）
和谈话页面中的这个条目
http://en.wikipedia.org/wiki/Talk:Co...ized_Python.3F
（对话：编程语言比较＃标准化Python？）
- 谢谢。
文章
< be *************************** *******@y5g2000hsf.g ooglegroups.com>，
ajaksu< aj **** @ gmail.comwrote：
1月27日晚上10点32分，Paddy< paddy3 ... @ googlemail.comwrote：
我会重视那些已经向维基百科贡献的Pythoneers的观点，关于是否是Python标准化的问题。
特别是在此表的上下文中：
http：//en.wikipedia.org/wiki/Compari ...语言#Gene ...
（编程语言比较）
这个条目在谈话页面中
http://en.wikipedia.org/wiki/Talk:Co...ming_languages .. 。
（对话：编程语言比较＃标准化Python？）
- 谢谢。
嗯。在我看来，是X标准化吗？在给定的上下文中意味着
具有由某些标准
组织发布的正式公布标准。
这就是它的意思。例如，如果我正在购买C ++编译器，我可以在合同中指定必须符合ISO 14882，并且每个人
都会知道什么我正在谈论。
在栅栏的另一边，如果我是自由职业的C ++开发人员，我可以
指定我的客户认为我编写的代码在使用符合ISO 14882的编译器编译时是正常工作的。无论这样的编译器实际上是否存在b / b $ b $，还有一点:-)
Python没有这样的标准。当然，docs.python.org上有一些东西，
但写一份合同很难说必须遵守
$ b在docs.python.org上有$ b的东西，并且在法律意义上它是有意义的。
所以，我认为不。在标准化？中python的列恰好是
吧。那并不是说你不可能有一些不好的东西，而不是标准化的b $ b。有时，标准委员会甚至会在标准化过程中进入左侧领域和b
。有些东西有很多不同的标准（即unix标准的完整标准），它的价值几乎毫无价值。但是，就目前而言，
维基百科文章是正确的。
Roy Smith < ro*@panix.com写在留言中
news：ro *********************** @ 70-1-84 -166.area1.spcsdns.net ...
|但是，Python肯定有很多实现定义。方面。
|特别是在图书馆。
我个人不认为图书馆是语言的一部分（因为
与发行版相对）并没有提及它们。句法语法
的语法定义非常严格。主要的例外是浮动
点，这是一个令人讨厌的问题。这就是为什么其中一个实现方面
正在标准化的下一个版本。
|特别是图书馆的那些部分
|在操作系统服务之上是薄层（操作系统和插座来了
到
|介意两个高度可变的区域）。
我确信套接字不是C89标准的一部分。因此，高b / b $ b变异性很高。 （我不知道更新的C标准）。我期望
，socket.py使变化不会更糟，并假设它掩盖了
至少一点点。同样适用于某些操作系统服务。
tjr
文章< ma *** **********************************@python.or g> ;,
"特里·里迪 < tj ***** @ udel.eduwrote：
" Roy Smith" < ro*@panix.com写在留言中
news：ro *********************** @ 70-1-84 -166.area1.spcsdns.net ...
|但是，Python肯定有很多实现定义。方面。
|特别是在图书馆。
我个人不认为图书馆是语言的一部分（因为
与发行版相对）并没有提及它们。
我意识到核心语言和
库之间存在差异，但Python依赖于库而不是很多其他
语言。它们是包括电池。部分。
的确，Python库参考中有很多内容。在
中，大多数语言都被认为是核心的一部分。例如，
布尔运算（和，或者不是）的描述。字符串，序列和
字典方法。你在哪里画线并说：核心语言
在这里结束;其余的只是图书馆？
I would value the opinion of fellow Pythoneers who have also
contributed to Wikipedia, on the issue of "Is Python Standardized".
Specifically in the context of this table:
http://en.wikipedia.org/wiki/Compari...ral_comparison
(Comparison of programming languages)
And this entry in the talk page
http://en.wikipedia.org/wiki/Talk:Co...ized_Python.3F
(Talk:Comparison of programming languages#Standardized Python?)
- Thanks.
In article
<be**********************************@y5g2000hsf.g ooglegroups.com>,
ajaksu <aj****@gmail.comwrote:
On Jan 27, 10:32 pm, Paddy <paddy3...@googlemail.comwrote:I would value the opinion of fellow Pythoneers who have also
contributed to Wikipedia, on the issue of "Is Python Standardized".
Specifically in the context of this table:
http://en.wikipedia.org/wiki/Compari...languages#Gene...
(Comparison of programming languages)
And this entry in the talk page
http://en.wikipedia.org/wiki/Talk:Co...ming_languages...
(Talk:Comparison of programming languages#Standardized Python?)
- Thanks.
Hmmm. Seems to me that "Is X Standardized" in the given context means
having a formal, published standard issued by some Standards
organization.That''s exactly what it means. For example, if I''m buying a C++ compiler, I
can specify in the contract, "Must comply with ISO 14882", and everybody
will know what I''m talking about.
On the other side of the fence, if I''m a free-lance C++ developer, I can
specify to my customers that the code I write will work properly when
compiled with a compiler that meets ISO 14882. Whether such a compiler
actually exists, is besides the point :-)
Python has no such standard. Sure, there''s the stuff on docs.python.org,
but it''s kind of hard to write a contract which says, "Must comply with the
stuff on docs.python.org", and have it be meaningful in a legal sense.
So, I think the "No" in the "Standardized?" column for python is exactly
right. That''s not to say you can''t have something good which isn''t
standardized. Sometimes standards committees even go off into left field
and field break stuff in the process of standardizing it. Some things have
so many different standards (i.e. the pletora of unix standards), it''s
almost worthless to say it''s standardized. But, as it stands, the
Wikipedia article is correct.
"Roy Smith" <ro*@panix.comwrote in message
news:ro***********************@70-1-84-166.area1.spcsdns.net...
| But, surely Python has plenty of "implementation defined" aspects.
| Especially in the libraries.
I personally do not consider the libraries as part of the language (as
opposed to the distribution) and was not referring to them. The semantics
of the syntax is pretty tightly defined. The main exception is floating
point, which is a nuisance. Which is why one implementation aspect thereof
is being standardized in the next version.
| Especially those parts of the libraries which
| are thin layers on top of operating system services (os and socket come
to
| mind as two highly variable areas).
I am sure that sockets are not part of the C89 standard. Hence the high
variability. (I don''t know about the newer C standard). I would expect
that socket.py makes the variability no worse and presume that it masks at
least a bit of it. Ditto for some os services.
tjr
In article <ma*************************************@python.or g>,
"Terry Reedy" <tj*****@udel.eduwrote:
"Roy Smith" <ro*@panix.comwrote in message
news:ro***********************@70-1-84-166.area1.spcsdns.net...
| But, surely Python has plenty of "implementation defined" aspects.
| Especially in the libraries.
I personally do not consider the libraries as part of the language (as
opposed to the distribution) and was not referring to them.I realize that there is a difference between the core language and the
libraries, but Python depends on the libraries more than a lot of other
languages do. They are the "batteries included" part.
Indeed, there is a lot of stuff in the "Python Library Reference" which in
most languages would be considered part of the core. The description of
boolean operations (and, or, not), for example. String, sequence, and
dictionary methods. Where do you draw the line and say, "The core language
ends here; the rest is just libraries"?
这篇关于Python标准化：维基百科条目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
