Closed gregglind closed 11 years ago
Seems like this is covered on the main site at: http://bottlepy.org/docs/dev/tutorial.html#tutorial-templates but not mentioned consistently.
Downloading bottle.py directly is not recommended, because you won't get any bug-fixes that way. The download link (see here http://bottlepy.org/docs/dev/tutorial.html#installation ) only gets you the development snapshot for quick testing. That is intentional, stable releases should be installed via pip or a package manager.
I think we are discussing different use cases.
For the use case where I want to do a demo, using bottle as a small, minimal server, I want transportable. The suggestion ask for a 'release' tag is to make it easier to always get the latest 'stable' release. If I want to update under that scenario, it's exactly the same curl
command, and I would get the bug fixes :)
This micro-usage of Bottle is one of the few reasons I have not to simple use a JavaScript client-side framework for these sorts of projects.
(Obviously, pip / venv / package manager is clearly the 'right way' for longer lived installs / promoting to a Real Project).
That sounds like a great set of links, and worth putting in the README, for the super super lazy!
GL
On Fri, Feb 15, 2013 at 6:07 PM, Marcel Hellkamp notifications@github.comwrote:
How about:
- http://bottlepy.org/docs/dev/bottle.py
- http://bottlepy.org/docs/stable/bottle.py
- http://bottlepy.org/docs/0.11/bottle.py
(updated daily)
— Reply to this email directly or view it on GitHubhttps://github.com/defnull/bottle/issues/442#issuecomment-13635601.
In README and other docs, it would be nice to see a stable one-line installer for the truly lazy:
For that to happen, there needs to be a tag/branch for 'release'.