Raymond Hettinger wrote: > [Reinhold Birkenfeld] >> This last patch includes a new exception, are you sure that this can > be >> safely backported? > > Not too worried about it. Better to have the exception reported than > the silent failure that confused the heck out of everyone who tried to > figure-out what caused the OP's problem. > > > >> If so, the documentation changes must be backported, too. > > Maybe. My thought is the new message is akin to an improved error > message. However, adding it to the Py2.4 docs suggests that you could > catch and handle the exception, but that cannot be done portably across > Py2.4 versions. If you really feel the need, go ahead and add to the > docs with \versionadded{2.4.2}. My preference is to leave it be. Makes sense. It'll be best to leave it be. Reinhold -- Mail address is perfectly valid!
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