Fix two "space not found" warnings in PEP-404.
This commit is contained in:
parent
6230377206
commit
c2bcb46cf6
|
@ -93,7 +93,7 @@ sequences. While Python 2 also has a unicode string type, the
|
|||
fundamental ambiguity of the core string type, coupled with Python 2's
|
||||
default behavior of supporting automatic coercion from 8-bit strings
|
||||
to unicode objects when the two are combined, often leads to
|
||||
`UnicodeError`s. Python 3's standard string type is Unicode based, and
|
||||
`UnicodeError`\ s. Python 3's standard string type is Unicode based, and
|
||||
Python 3 adds a dedicated bytes type, but critically, no automatic coercion
|
||||
between bytes and unicode strings is provided. The closest the language gets
|
||||
to implicit coercion are a few text-based APIs that assume a default
|
||||
|
@ -106,7 +106,7 @@ natively supported.
|
|||
This string/bytes clarity is often a source of difficulty in
|
||||
transitioning existing code to Python 3, because many third party
|
||||
libraries and applications are themselves ambiguous in this
|
||||
distinction. Once migrated though, most `UnicodeError`s can be
|
||||
distinction. Once migrated though, most `UnicodeError`\ s can be
|
||||
eliminated.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue