====== Python 俱乐部 ======

===== Python2 =====

  * [[python-basic:introduction]]
  * [[python-basic:start|Python基本语法]]
  * [[python-class:start|Python的类]]
  * [[python-files:start|Python文件处理]]
  * [[python-network-application:start|Python网络编程]]
  * [[modules:start|Python 模块]]
  * [[algorithm:start|常见算法的Python实现]]
  * [[python-hacks:start|Python Hacks]]
  * [[python-books:start]]
  * [[database:start|Python数据库相关]]
  * [[dataminer:start]]
  * [[download:start]]
  * [[news:start]]
  * [[application:start]]
  * [[challenge:start]]

====== Python3 ======
  * [[p3:start]]


===== Python 应用 =====
  * [[google:start]]
    * [[google:gae:start]]
  * [[heroku:start]]
  * [[framework:django:start]]

===== 我的工作 =====
  * [[vlsi:start]]

===== 我的爱好 =====
  * 系统
    * [[linux:start]]

  * 编程 
    * [[html:javascript:start]]
    * [[php:start]]
    * [[tcl:start]]
    * [[perl:start]]
    * [[code:start]]

  * 软件
    *  [[mysql:start]]
    * [[linux:vim:start]]

  * 建站
    * [[dokuwiki:start]]

  * 求职
    * [[interview:start]]
  * [[itfun:start]]
  * [[host:start]]
===== 最近更新 =====
<latestupdate> 
  * [[http://www.pythonclub.org/feed.php|RSS 订阅更新]]
====== Zen of Python ======

<code>
Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
>>>
</code>