Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document workaround for "RuntimeError: maximum recursion depth exceeded" #2325

Closed
wants to merge 1 commit into from

Conversation

timgraham
Copy link
Contributor

As suggested in https://groups.google.com/d/topic/sphinx-dev/MtRf64eGtv4/discussion.

If there's a better spot in the docs to put this, let me know.

@birkenfeld
Copy link
Member

Why not emit this hint as a message when we catch the exception at runtime?

@timgraham
Copy link
Contributor Author

It could be done. I'm not sure it affects enough projects that it's a high priority given the complexity of that solution though.

@birkenfeld
Copy link
Member

I don't mind how many cases it actually affects (at least two) - interpreting the exception is easy and a good way to be more user friendly.

@timgraham
Copy link
Contributor Author

All right, I'll close this then. At least it can be found by search engines for now.

@timgraham timgraham closed this Feb 16, 2016
@birkenfeld
Copy link
Member

I was hoping you'd update the patch :)

@timgraham timgraham deleted the setrecursionlimit branch February 16, 2016 18:23
gmcharlt pushed a commit to Koha-Community/kohadocs that referenced this pull request Aug 14, 2017
To avoid 'RuntimeError: maximum recursion depth exceeded while calling a
Python object'

See sphinx-doc/sphinx#2325

1500 was not enough
gmcharlt pushed a commit to Koha-Community/kohadocs that referenced this pull request Oct 4, 2017
To avoid 'RuntimeError: maximum recursion depth exceeded while calling a
Python object'

See sphinx-doc/sphinx#2325

1500 was not enough

(cherry picked from commit 95d70ab)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants