From ee374553f2ba385157eec9a816cf9b023fbfb18a Mon Sep 17 00:00:00 2001 From: Zhiming Wang Date: Mon, 4 May 2015 15:03:55 -0700 Subject: process post metadata --- source/blog/2014-12-05-python-3-and-unicode.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'source/blog/2014-12-05-python-3-and-unicode.md') diff --git a/source/blog/2014-12-05-python-3-and-unicode.md b/source/blog/2014-12-05-python-3-and-unicode.md index d7d871d8..eb596956 100644 --- a/source/blog/2014-12-05-python-3-and-unicode.md +++ b/source/blog/2014-12-05-python-3-and-unicode.md @@ -1,8 +1,6 @@ --- -layout: post title: "Python 3 and Unicode" date: 2014-12-05 15:01:54 -0800 -comments: true -categories: +date-display: December 5, 2014 --- I never realized that in Python 3 Unicode is the default; in particular, `str` in Python 3 is practically equivalent to `unicode` in Python 2. This might be the *one thing* that convince me to migrate. `str.encode()`, `str.decode()`, `unicode.encode()`, `unicode.decode()`, etc. are so confusing that I'm never 100% sure what I'm doing (only-occasionally-used-but-unavoidable-and-worst-of-all-very-confusing "features" are nightmares). -- cgit v1.2.1