document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2024-12-26 21:30:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #20838 from lujun9972/add-MjAxOTEyMjggVGhlIFplbiBvZiBQeXRob24tIFdoeSB0aW1pbmcgaXMgZXZlcnl0aGluZy5tZAo=

Browse Source 
选题[tech]: 20191228 The Zen of Python: Why timing is everything
This commit is contained in:
Xingyu.Wang 2021-01-25 22:05:18 +08:00 committed by GitHub
commit 0c3eeb2b26
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 44 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
sources/tech/20191228 The Zen of Python- Why timing is everything.md Normal file
View File

@ -0,0 +1,44 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (The Zen of Python: Why timing is everything)
[#]: via: (https://opensource.com/article/19/12/zen-python-timeliness)
[#]: author: (Moshe Zadka https://opensource.com/users/moshez)
The Zen of Python: Why timing is everything
======
This is part of a special series about the Zen of Python focusing on the
15th and 16th principles: now vs. never.
![Clock, pen, and notepad on a desk][1]
Python is always evolving. The Python community has an unending appetite for feature requests but also an unending bias toward the status quo. As Python gets more popular, changes to the language affect more people.
The exact timing for when a change happens is often hard, but the [Zen of Python][2] offers guidance.
### Now is better than never.
There is always the temptation to delay things until they are perfect. They will never be perfect, though. When they look "ready" enough, that is when it is time to take the plunge and put them out there. Ultimately, a change always happens at _some_ now: the only thing that delaying does is move it to a future person's "now."
### Although never is often better than _right now_.
This, however, does not mean things should be rushed. Decide the criteria for release in terms of testing, documentation, user feedback, and so on. "Right now," as in before the change is ready, is not a good time.
This is a good lesson not just for popular languages like Python, but also for your personal little open source project.
--------------------------------------------------------------------------------
via: https://opensource.com/article/19/12/zen-python-timeliness
作者：[Moshe Zadka][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/moshez
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/desk_clock_job_work.jpg?itok=Nj4fuhl6 (Clock, pen, and notepad on a desk)
[2]: https://www.python.org/dev/peps/pep-0020/