A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-October/082880.html below:

[Python-Dev] status of 2.5

[Python-Dev] status of 2.5 [Python-Dev] status of 2.5A.M. Kuchling amk at amk.ca
Mon Oct 6 23:28:50 CEST 2008
On Mon, Oct 06, 2008 at 12:53:01PM -0700, Raymond Hettinger wrote:
> The 2.6/3.0 development process was so disruptive that I doubt
> that 2.5 received adequate attention for bug fixes.  Why not wait
> two or three months for the dust to settle?

Can you please clarify your meaning? Do you mean that 

* we haven't been backporting fixes to 2.5?
* we should wait to see if any horrible problems are reported in 2.6?
* we need to look at the logs for commits that should be applied to 2.5?

--amk
More information about the Python-Dev mailing list

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