> I know, and I'm not. But the thing is, there are plenty of users of > CPython which do rely on this feature -- so you're going to break > people's code. Not nice. No - we will simply be pointing out their already broken code. We arent breaking anything! I have no problem with this at all. The sooner we point out the broken code the better. The last thing we want is for obviously and documented broken code to suddenly be considered non-broken simply by the volume of poor code out there... Either way, I think you are overstating the problem. The main scenario is closing resources, and for most users these are unlikely to be so scarce that delaying their finalization will cause problems. If someone is writing a web-server, for example, and assumes that files or sockets are automatically closed, and they open them at such a rate that true GC causes them a problem, then IMO they have got what they deserve ;-) Mark.
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