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

Correctly spell hierarchy.

This commit is contained in:
Guido van Rossum 2013-08-01 08:04:13 -07:00
parent fade322fd5
commit bbc946a16a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pep-0413.txt
View File

@ -627,7 +627,7 @@ release, one possible layout for such an approach might look like::
<news entries>
# Add maint.1, compat.1 etc as releases are made
Putting the version information in the directory heirarchy isn't strictly
Putting the version information in the directory hierarchy isn't strictly
necessary (since the NEWS file generator could figure out from the version
history), but does make it easier for *humans* to keep the different versions
in order.