From the command line\/terminal run <\/p>\n
\r\npip install bottle\r\n<\/pre>\nBottle supports a style of defining routes to functions using decorators, for example<\/p>\n
\r\nfrom bottle import route, run\r\n\r\n@route('\/<name>')\r\ndef index(name):\r\n return f"Hello {name}"\r\n\r\nrun(host='localhost', port=8080)\r\n<\/pre>\nHTTP Method(s)<\/strong><\/p>\n
By default a @route<\/em> will respond to a GET HTTP method, but we can change to POST or be more explicit using the following<\/p>\n
\r\n@route('\/<name>', method='GET')\r\n# or\r\n@get('\/<name>')\r\n# or POST\r\n@route('\/<name>', method='POST')\r\n# or\r\n@post('\/<name>')\r\n<\/pre>\nWe can combine the methods using the following<\/p>\n
\r\n@route('\/<name>', method=['GET', 'POST'])\r\n<\/pre>\nand then within the actual function we can use the request<\/em> class like this<\/p>\n
\r\n@route('\/<name>', method=['GET', 'POST'])\r\ndef index(name):\r\n if request.method == 'POST':\r\n return f"POST {name}"\r\n elif request.method == 'GET':\r\n return f"GET {name}"\r\n\r\n return "Unexpected"\r\n<\/pre>\nWe can also declare multiple routes to a function like this<\/p>\n
\r\n@route('\/', method=['GET', 'POST'])\r\n@route('\/<name>', method=['GET', 'POST'])\r\ndef index(name = None):\r\n if request.method == 'POST':\r\n return f"POST {name}"\r\n else request.method == 'GET':\r\n return f"GET {name}"\r\n\r\n return "Unexpected"\r\n<\/pre>\nHow about some JSON<\/strong><\/p>\n
Obviously JSON is the current “in vogue” format for transferring data. To return JSON instead of a simple string we can use jsonpickle, start off by installing the library using<\/p>\n
\r\npip install jsonpickle\r\n<\/pre>\nWe’ll add an example class for our result<\/p>\n
\r\nclass Person:\r\n def __init__(self):\r\n self.firstName = "Eddie"\r\n self.lastName = "Van Halen"\r\n<\/pre>\nand our code (and additional imports) looks like this<\/p>\n
\r\nimport jsonpickle\r\n\r\n@get('\/<name>')\r\ndef index(name):\r\n person = Person()\r\n return jsonpickle.encode(person, unpicklable=False)\r\n<\/pre>\nThe unpicklable=False<\/em> turns off the pickle additional information to our JSON.<\/p>\n
Errors<\/strong><\/p>\n
We can also supply web pages, data etc. based upon HTTP errors, such as 404 errors. Assuming we changed out @get (above) to <\/p>\n
@get(‘\/name\/<name>’)<\/p>\n
now URL’s such as http:\/\/localhost:8080\/PutridParrot will fail to find a matching route and if we supply an error handler for a 404 then we can return some other data, i.e.<\/p>\n
\r\n@error(404)\r\ndef error404(error):\r\n return "Got a 404!"\r\n<\/pre>\n