|
|
|
|
|
|
by bonkabonka
5399 days ago
|
|
|
You're right, I indulged in too much purple prose there. Sorry. Would you expand on what you meant by: > The context of the comment makes it seem like it's subpar on these things. What I intended to get across was that Bottle, being a single file at ~2700 lines, makes it convenient to scan the code to see exactly what it is doing (or not). It also doesn't require a lot of typing to wire a function to a URL and offers some nice syntactic sugar while doing so: you don't have to @route things you can @get them or @post them (it's probably my Java background that makes me think in terms of separate code paths for the different HTTP verbs). My take on a more detailed (and hopefully hyperbole-free) summation of my original post is: "Because this was a short timeframe prototype, they had no Linux VM available in the lab so I had to use Windows. I found a recipe that let me run Python stuff as a service which I was able to wrap around Bottle more quickly than I was able to with the other frameworks I tried. Because I was working on a machine that had no access out to the internet, I had no virtualenv and had to instead bundle all my stuff up by hand." |
|
|