CherryPy的VS瓶/ WERKZEUG [英] cherrypy vs flask/werkzeug

问题描述

我想写一个Python信息服务器：

I want to write a Python "information server":

• 在多种类型的信息将被显示：数据，文档等的表有些是动态的，一些静态。我想使用HTML模板，和我已经使用的Jinja2（带pygments）。
• 也可以有一些实时更新页面，所以我想使用AJAX也许jQuery的。
• 我想这个部署，而无需安装和配置HTTP服务器（例如Apache）。交通将是相当低的。但我想一个有效的Python服务器。

这两个解决方案，我在脑海中的CherryPy或瓶（和WERKZEUG）。 （这将与Jinja2的，jQuery的，SQLite的，SQL-炼金术？使用）的CherryPy已经存在了一段时间，显得相当成熟，并期待有一个高效的服务器实现和所有我想要的功能。瓶是新的，但看起来更加精致，而且我从Pocoo的其他工作pssed IM $ P $。

The two solutions I have in mind are Cherrypy or Flask (and Werkzeug). (These would be used with jinja2, jQuery, SQLite, SQL-Alchemy?) Cherrypy has been around for a while and seems quite mature and looks to have an efficient server implementation and all the features I'd want. Flask is newer, but looks more polished, and I'm impressed by the other work from Pocoo.

有没有人有两个系统工作过的经历吗？什么是要么限制？如何他们比较（功能，文档，支持，臭虫，速度）。

Does anyone have experience of having worked with both systems? What are limitations of either? How to they compare (features, documentation, support, bugs, speed).

时WERKZEUG一个高效的服务器？我读到的CherryPy大约是有效的一个，你可以用Python语言编写的服务器。是WERKZEUG快/ rebust足以让一个小网站？

Is Werkzeug an efficient server? I read that Cherrypy is about as efficient a server as you could write in Python. Is Werkzeug fast/rebust enough for a small site?

请不要用回复是男人，瓶凉，你应该使用它。这告诉我任何关于你的推理或经验，让我觉得你没有的真正的使用它。

Please don't reply with "yeah man, Flask is cool, you should use it." That tells me nothing about your reasoning or experience and makes me think you haven't really used it at all.

推荐答案

我一直在使用的两个的，在过去​​的几个月里，使用的CherryPy作为服务器和瓶为骨架 - 我有没有问题的。 （这是一个内部工具，所以非常低的流量，很喜欢你的事物所的声音。）

I have been working with both for the past few months, using CherryPy as the server and Flask as the framework -- and I have had no problems at all. (It is an internal tool, so very low traffic, very much like yours by the sound of things.)

我的经验总结：与开发服务器运行烧瓶并不稳定 - 与运行的CherryPy瓶作为服务器一直坚如磐石的

Summary of my experience: Running Flask with the development server was not stable -- running Flask with CherryPy as the server has been rock-solid.

我没有花很多时间与CherryPy的发展作为一个框架，所以我不能对此发表评论主场迎战瓶 - 但用他们两个在一起一直是绝对的胜利。

I have not spent a lot of time developing with CherryPy as a framework, so I cannot comment on it vs. Flask -- but using the two of them together has been an absolute win.

这篇关于CherryPy的VS瓶/ WERKZEUG的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！