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

Fix typos in PEP 423 

Closes #54
This commit is contained in:
Berker Peksag 2016-07-14 17:16:06 +03:00 committed by GitHub
parent 14c5ca31b6
commit 970e9c5346
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0423.txt
View File

@ -88,7 +88,7 @@ names:
* `register names with PyPI`_.
* make sure distributed packages and modules names are unique, unless
you explicitely want to distribute alternatives to existing packages
you explicitly want to distribute alternatives to existing packages
or modules. `Using the same value for package/module name and
project name <#use-a-single-name>`_ is the recommended way to
achieve this.
@ -165,7 +165,7 @@ Respect ownership
Understand the purpose of namespace before you use it.
Don't plug into a namespace you don't own, unless explicitely
Don't plug into a namespace you don't own, unless explicitly
authorized.
`If in doubt, ask`_.
@ -302,7 +302,7 @@ Distinct names should be rare
-----------------------------
A notable exception to the `Use a single name`_ rule is when you
explicitely need distinct names.
explicitly need distinct names.
As an example, the `Pillow`_ project provides an alternative to the
original `PIL`_ distribution. Both projects distribute a "PIL"
@ -579,7 +579,7 @@ About convention choices:
custom conventions. Then they can `Promote migrations`_.
It means that existing community conventions don't have to be
changed. But, at least, they should be explicitely documented.
changed. But, at least, they should be explicitly documented.
Example: "pyranha" is your project name and package name.
Tell contributors that: