> > Agreement on 5000? > > No, the __getattr__ example still dumps core for me. With 4000 it is > fine, but this indicates that this is totally the wrong approach: I > can change the available stack size with ulimit -s and cause a core > dump anyway. Or there could be a loger path through the C code where > more C stack is used per recursion. > > We could set the maximum to 1000 and assume a "reasonable" stack size, > but that doesn't make me feel comfortable either. > > It would be good if there was a way to sense the remaining available > stack, even if it wasn't portable. Any Linux experts out there? Gordon, how's that Stackless PEP coming along? Sorry, I couldn't resist ;-) Just
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