From c2bcb46cf6d079ec00031c64ae9cbb7df105ed8e Mon Sep 17 00:00:00 2001 From: Ezio Melotti Date: Thu, 17 Nov 2011 18:45:29 +0200 Subject: [PATCH] Fix two "space not found" warnings in PEP-404. --- pep-0404.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pep-0404.txt b/pep-0404.txt index 6918b0cd0..f11cb78cd 100644 --- a/pep-0404.txt +++ b/pep-0404.txt @@ -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.