iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix a couple of typos

This commit is contained in:
Eli Bendersky 2012-02-11 05:04:13 +02:00
parent bf85d6e7bc
commit 8acc68809b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0411.txt
View File

@ -26,7 +26,7 @@ On the other hand, the core development team explicitly states that no promises
are made with regards to the the stability of the package's API, which may
change for the next release. While it is considered an unlikely outcome,
such packages may even be removed from the standard library without a
deprecation period if the concerns regarding their API or maintenante prove
deprecation period if the concerns regarding their API or maintenance prove
well-founded.
@ -90,7 +90,7 @@ stable standard library. Some reasons for not graduating are:
* A much better alternative package may be found during the preview release.
Essentially, the decision will be made by the core developers on a per-case
basis. The point to emphasize here is that a packages's inclusion in the
basis. The point to emphasize here is that a package's inclusion in the
standard library as "provisional" in some release does not guarantee it will
continue being part of Python in the next release.