Python 3移植

The 3 in 2013 is for Python 3

2013年的3是针对Python 3的

I tend to like projects that everyone else hates, e.g.:

我倾向于项目一样，其他人都恨 ，如：

• Removing persistent Python objects associated with missing classes in ZODB.
• Making new releases for old software that is still useful but unmaintained.
• Running flake8 on 10s or 100s of source files and hand-fixing the results.

• 删除与ZODB中缺少类相关联的持久化Python对象。
• 为旧软件制作新版本仍然有用，但无需维护。
• 在10s或100s的源文件上运行flake8并手动修复结果。

Part of this has to do with repetition. I know how to do these things, and I like doing them. Over and over. If someone says, “my Data.fs file is broken” I get excited. Anyway, I hope you get the idea.

这部分与重复有关 。 我知道如何做这些事情，而且我喜欢这样做。 一遍又一遍。 如果有人说“我的Data.fs文件已损坏”，我会很兴奋。 无论如何，我希望你能明白。

我是你的男人 (I am your man)

Which brings me to the subject of this post: Python 3 Porting. I’ve been helping out porting the Python Imaging Library to Python 3 (via the Pillow fork, where I am the release manager). And it strikes me as the type of thing I’d be very interested in doing professionally. So, if you or your company are in need of a “workhorse” to plow through old code and update it, I am your man. Please do get in touch.

这使我想到了本文的主题： Python 3 Porting 。 我一直在帮助将Python Imaging Imaging Library移植到Python 3（通过Pillow fork，我是版本管理器）。 这让我印象深刻，因为我对专业做事非常感兴趣。 因此，如果您或您的公司需要“主力军”研究旧代码并进行更新，那么我就是您的人 。 请保持联系 。

给你的东西是什么 (What’s in it for you)

Now I know what you are thinking: porting Python 2 software to Python 3 is a lot of work for little gain. Maybe. Maybe not. I’m not going to try to convince you otherwise, however I will tell you this:

现在，我知道您在想什么： 将Python 2软件移植到Python 3上的工作量很大，但收效甚微 。 也许。 也许不会。 我不会试图说服您，但是我会告诉您的是：

• For me, 2013 is “the year of Python 3”. I’ve now promised to deliver and maintain a Python 3 compatible PIL by PyCon 2013. I now care about Python 3 (this was not true before).
• The Python 3 Wall of Shame is now the Python 3 Wall of Superpowers. We are over the hump.
• Many popular Python web frameworks support or are about to support Python 3 e.g. CherryPy, Django, Pyramid.

• 对我来说，2013年是“ Python 3之年”。 我现在已承诺在PyCon 2013之前交付并维护与Python 3兼容的PIL 。 我现在关心的是Python 3（以前不是这样）。
• Python 3耻辱墙现在是Superpower的Python 3墙 。 我们已经驼峰了。
• 许多流行的Python Web框架都支持或即将支持Python 3，例如CherryPy，Django，Pyramid。

So, there is no time like the present to take a serious look at Python 3.

因此，没有像现在这样的时间认真考虑Python 3了 。

翻译自: https://www.pybloggers.com/2013/01/python-3-porting/