| Name |
Last commit
|
Last update |
|---|---|---|
| docs | ||
| rest_framework | ||
| tests | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| MANIFEST.in | ||
| README.md | ||
| mkdocs.py | ||
| requirements-test.txt | ||
| requirements.txt | ||
| runtests.py | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini |
I ran into an issue today where I was not seeing the rest_framework.views.exception_handler do what I thought it should be doing. It turned out that I had imported View from rest_framework.views rather than importing APIView from rest_framework.views. The phrase "raised inside REST framework" was confusing as I was debugging this issue. I was unsure if that meant that I could raise those exceptions in my code or if it had to originate from within framework code. I'm not sure if the proposed wording is ideal, I just wanted to point out what I found to be confusing.
| Name |
Last commit
|
Last update |
|---|---|---|
| docs | Loading commit data... | |
| rest_framework | Loading commit data... | |
| tests | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| MANIFEST.in | Loading commit data... | |
| README.md | Loading commit data... | |
| mkdocs.py | Loading commit data... | |
| requirements-test.txt | Loading commit data... | |
| requirements.txt | Loading commit data... | |
| runtests.py | Loading commit data... | |
| setup.cfg | Loading commit data... | |
| setup.py | Loading commit data... | |
| tox.ini | Loading commit data... |