[issue37985] WFERR_UNMARSHALLABLE breaks recursion limit

2020-04-12 Thread Dong-hee Na
Change by Dong-hee Na : -- versions: -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue37985] WFERR_UNMARSHALLABLE breaks recursion limit

2020-04-12 Thread hai shi
hai shi added the comment: If I understand correctly, `p->depth--` associated with `p->error` could be removed? -- ___ Python tracker ___

[issue37985] WFERR_UNMARSHALLABLE breaks recursion limit

2020-04-12 Thread hai shi
Change by hai shi : -- keywords: +patch nosy: +shihai1991 nosy_count: 2.0 -> 3.0 pull_requests: +18836 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19482 ___ Python tracker ___

[issue37985] WFERR_UNMARSHALLABLE breaks recursion limit

2019-08-30 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: It should be against master or the the newest version in which the problem exists. After merging this pull request the changes will be backported to older versions. 3.6 and 3.5 are open for security fixes only. -- nosy: +serhiy.storchaka

[issue37985] WFERR_UNMARSHALLABLE breaks recursion limit

2019-08-29 Thread Davis Herring
Davis Herring added the comment: I can easily make a patch or pull request, but against which version(s) should I do so? (Will such a trivial change require a CLA?) -- ___ Python tracker __

[issue37985] WFERR_UNMARSHALLABLE breaks recursion limit

2019-08-29 Thread Davis Herring
New submission from Davis Herring : Most of the "p->depth--;" lines associated with "p->error = WFERR_UNMARSHALLABLE;" are spurious, and can crash the interpreter if enough of them prevent reaching MAX_MARSHAL_STACK_DEPTH. (The only exceptions are in 2.7, where some of them are followed by a