PEP 638: Fix typos (#1634)
This commit is contained in:
parent
0c87b5a018
commit
0766114edf
12
pep-0638.rst
12
pep-0638.rst
|
@ -47,7 +47,7 @@ The use of Python in data science and machine learning has grown very rapidly
|
||||||
over the last few years.
|
over the last few years.
|
||||||
However, most of the core developers of Python do not have a background in
|
However, most of the core developers of Python do not have a background in
|
||||||
data science or machine learning.
|
data science or machine learning.
|
||||||
This makes it extemely difficult for the core developers to determine if a
|
This makes it extremely difficult for the core developers to determine if a
|
||||||
language extension for machine learning is worthwhile.
|
language extension for machine learning is worthwhile.
|
||||||
|
|
||||||
By allowing language extensions to be modular and distributable, like libraries,
|
By allowing language extensions to be modular and distributable, like libraries,
|
||||||
|
@ -55,7 +55,7 @@ domain specific extensions can be implemented without negatively impacting
|
||||||
users outside of that domain.
|
users outside of that domain.
|
||||||
A web developer is likely to want a very different set of extensions from
|
A web developer is likely to want a very different set of extensions from
|
||||||
a data scientist.
|
a data scientist.
|
||||||
We need to let the commmunity develop their own extensions.
|
We need to let the community develop their own extensions.
|
||||||
|
|
||||||
Without some form of user defined language extensions,
|
Without some form of user defined language extensions,
|
||||||
there will be a constant battle between those wanting to keep the
|
there will be a constant battle between those wanting to keep the
|
||||||
|
@ -65,8 +65,8 @@ that suits their domain or programming style.
|
||||||
__ https://www.linuxjournal.com/article/4731
|
__ https://www.linuxjournal.com/article/4731
|
||||||
|
|
||||||
|
|
||||||
Improving the expessiveness of libraries for specific domains
|
Improving the expressiveness of libraries for specific domains
|
||||||
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
|
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
|
||||||
|
|
||||||
Many domains see repeated patterns that are difficult or impossible
|
Many domains see repeated patterns that are difficult or impossible
|
||||||
to express as a library.
|
to express as a library.
|
||||||
|
@ -97,7 +97,7 @@ operations that that could, and should, have been done in the compiler.
|
||||||
|
|
||||||
For example,
|
For example,
|
||||||
until recently flow control within the ``try``-``finally`` and ``with``
|
until recently flow control within the ``try``-``finally`` and ``with``
|
||||||
statments was managed by complicated bytecodes with context dependent semantics.
|
statements was managed by complicated bytecodes with context dependent semantics.
|
||||||
The control flow within those statements is now implemented in the compiler, making
|
The control flow within those statements is now implemented in the compiler, making
|
||||||
the interpreter simpler and faster.
|
the interpreter simpler and faster.
|
||||||
|
|
||||||
|
@ -451,7 +451,7 @@ can be replaced with the zero cost macro:
|
||||||
def foo(...):
|
def foo(...):
|
||||||
...
|
...
|
||||||
|
|
||||||
Protyping langauge extensions
|
Protyping language extensions
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
Although macros would be most valuable for domain specific extensions, it is possible to
|
Although macros would be most valuable for domain specific extensions, it is possible to
|
||||||
|
|
Loading…
Reference in New Issue