Hello, maybe you have noticed a bunch of commits I made the last couple of days. They were all related to resource leaks and other issues that were detected by Coverity. Maybe you have seen the CID in some checkin messages. Most memory and reference leaks were found in the error branch of functions and predates even Python 2.7. The leaks are usually in highly unlikely branches and cause no serious problem. Coverity is really great in following up all possible code branches. A few issues are 3.3 regressions, for example #15900, #15895 and 85cb90f79cbf are IMHO serious issues that should be fixed in the next rc. AFAIK Georg wants to create another rc. I didn't create NEWS entries for my commits yet and just a few tickets for modification I wasn't sure about. Is it sufficient to write just one news entry that lists all fixed functions for 2.7 and 3.2? Georg: Shall I create a list of commits with just regressions so you can cherry pick them? Or do you want to pull all memory leak fixes? Christian