[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2021-10-19 Thread Irit Katriel
Irit Katriel added the comment: There has been work done on recursion handling in more recent python versions, so you should get clean RecursionErrors now rather than the fatal error. Please create a new issue if you have such problems on current versions (3.9+). -- nosy:

[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2019-09-05 Thread hongweipeng
hongweipeng added the comment: According to the provided text.py file. `__exit__` will always execute due to the `with` syntax. It looks like this: ``` def rec(): try: rec() except RecursionError: rec() rec() ``` -- nosy: +hongweipeng

[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2019-06-26 Thread konstantin danilov
konstantin danilov added the comment: Same error, python3.7. I have attached minifyed code version. It runs into infinite recursion due to __setattr__ call inside 'with' statement on top of same object. As result: > python /tmp/text.py Fatal Python error: Cannot recover from stack

[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2019-06-26 Thread Andrew Svetlov
Andrew Svetlov added the comment: Is it ok to have File "/home/ajung/sandboxes/ugent-portaal-plone-4x/eggs/Products.CMFDynamicViewFTI-6.0.1-py3.7.egg/Products/CMFDynamicViewFTI/browserdefault.py", line 76 in __call__ so many times? Looks very suspicious --

[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2019-06-25 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- components: +asyncio -Interpreter Core nosy: +asvetlov, yselivanov versions: +Python 3.8, Python 3.9 -Python 3.6 ___ Python tracker ___

[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2019-06-25 Thread Andreas Jung
Andreas Jung added the comment: Typical traceback: WARNING:plone.app.contenttypes.indexers:Lookup of PrimaryField failed for http://nohost/plone_portal/microscopycentre/img/fotos-specialist-course2018.htm/demo10-jpg If renaming or importing please reindex!

[issue37402] Fatal Python error: Cannot recover from stack overflow issues on Python 3.6 and 3.7

2019-06-25 Thread Andreas Jung
New submission from Andreas Jung : I am using Python 3.6 and 3.7 (always latest minor releases) with Plone 5.2 and I various issues with Fatal Python error: Cannot recover from stack overflow. and do not make much sense to me. Some related tracebacks are documented here