#16 use the request path in the exception

[dannystaple]

Fixes #16.
Output looks like:

Traceback (most recent call last):
  File "code.py", line 1, in <module>
  File "counting.py", line 23, in <module>
  File "robot_wifi.py", line 52, in start_wifi_server
  File "adafruit_esp32spi/adafruit_esp32spi_wsgiserver.py", line 105, in update_poll
  File "/lib/adafruit_wsgi/wsgi_app.py", line 74, in __call__
RuntimeError: Proper HTTP response return not given for request handler '/count'

[tekktrik]

Good solution! Want to update the accompanying text to something more about the "path" than the "request handler"?
Actually I think "request handler for path" would be enough information to indicate that the issue is for the actual function while referencing it's path.

[tekktrik]

The feedback from above, but now in review format so I can hit the "Request changes" button 😄

[tekktrik]

Small change because the text seems to be broken up upon testing

[tekktrik]

I checked this out, and it seems this will be raised and catch the tabs as follows:

RuntimeError: Proper HTTP response return not given for request handler for path         'some/path/'

Try this out, I think this should both appease pylint and keep the words together:

    "Proper HTTP response return not given for request handler for path "
    f"'{request.path}'"

Note the space after path in the first line!

[dannystaple]

That should be better there. It didn't need to be f-stringed, as it is already typed as a string, so a simple concatenation should be good enough

[tekktrik]

Looks like the f is missing for the f-string

[dannystaple]

Facepalm. Fixed it.

[tekktrik]

Fantastic! Looks good to me!