Home
Hello PageHTTP and WSGI variablesUpload exampleCGI examplesFavicon - Text ModeFavicon - Image
Session variablesCookies
Factorial of 42The origin of everything: Python!Python per noi...WSGI (Web Server Gateway Interface, the tech behind Bicchiere) Wikipedia pageWSGI Python secret web weapon (Part I)WSGI Python secret web weapon (Part II)
Show '/static' directory
Echo Server Example
About

WSGI, Bicchiere Flavor

Bicchiere Logo

Yet another Python web (WSGI) micro-framework

Following Flask and Bottle footsteps, adding a bit of italian flavor :-)

Install

pip install bicchiere

Project Demo App

GitHub tag (latest by date)

A drop from Bicchiere

from bicchiere import Bicchiere

app = Bicchiere()
or
app = Bicchiere("La mia bella App")

@app.get("/")
def home():
    return "Bon giorno, cosa bevete oggi?"
    
if __name__ == "__main__":
    #This will run default server on http://localhost:8086
    app.run()

... and this is just about the classical WSGI Hello, World, for everything else please refer to Bicchiere Wiki

Well... not really. A bit of rationale is in order here.

So, why Bicchiere?

  • For one thing, reinventing the wheel is not only fun but highly educational, so, by all means, do it!

  • I like Flask and Bottle. A lot. Both have things that I highly appreciate, simplicity in the first place. But it doesn't end there.

  • There's also the single file/no dependencies approach (Bottle), which I intend to mimic with Bicchiere. Although not a mandatory thing, I like it that way.

  • Built-in sessions (Flask). Although the user of the library must be free to choose whatever he likes regarding sessions or any other component of the application for that matter, I think session-handling is one of those must-have things in any web app these days. So, I provided basic session handling mechanism, in 3 flavors: memory, filesystem, and sqlite. This was the most that could be done without falling out of the boundaries of the Python Standard Library. Details on this at the wiki (under construction)

  • Built-in templating mechanism (Bottle). Similar considerations apply. In my opinion, this is also a must have, regardless how micro is the framework/library. Then again, end-user must be free to choose. As a good WSGI compliant middleware, Bicchiere doesn't come in the way of the user if he prefers to use Mako, Jinja2, Genshi or whatever he likes. Details at the wiki (under construction)

  • WebSockets handling: to me, this is the fruit on the cake, for various reasons:

    1. It's been said that it can't be done under WSGI, reason the more to do it.
    2. Real time communication looks like another must have in the current landscape of web app development
    3. Then again, its a lot of fun. A lot of pain, too... In any case, Bicchiere comes bundled with native WebSocket support - just taken out from the oven :-)) Details at the wiki (under construction) . Regretably, the original Demo App won't work with websockets, because Pythonanywhere hasn't yet implemented the feature. As of now, there's a mirror at bicchiere.sytes.net which works fine, test at the home page and all. In any case, these issues are related to reverse proxy configuration and have nothing to see with the app/library itself.

  • And still, there's a lot of stuff to be mentioned. More to come...