-On [20090128 00:57], Barry Warsaw (barry at python.org) wrote: >I stand by my opinion about the right way to do this. I also think >that a 3.1 release 6 months after 3.0 is perfectly fine and serves our >users just as well. When API fixes were mentioned, does that mean changes in the API which influence the C extension? If so, then I think a minor number update (3.1) is more warranted than a revision number update (3.0.1). -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Earth to earth, ashes to ashes, dust to dust...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4