I'm afraid not. This is a new feature not a bugfix. The 2.5 behaviour is not a bug, it is documented. Backporting the new behaviour would make it necessary to change the documentation, too. Because of Python release policy and 2.5.1 being a bugfix release, this cannot go in, I'm afraid. You must wait for the 2.6 release and work around this in the meantime. Sorry.