Jorge Vargas wrote: > for ones 2.5 is not consider production code yet so noone should be > running anything on it. same with 1.6.
that's completely ignoring how Python's developed, though. if you know what you're doing, using stable (*) betas or release candidates can be an excellent idea. </F> *) where "stable" means "works well in your test environment". -- http://mail.python.org/mailman/listinfo/python-list
