Is CherryPy dead?

[irrgit]

Greetings,
I have this past year been using the CherryPy framework for a couple of
projects
and love everything about it. Alas everywhere I go online i dont find
anything
good or what i expect to find for what i consider such a great framework.
Have people moved to other frameworks? Are CherryPy users hermits?
Its discouraging to go online and search for benchmarks and comparisons
only to
find little to none when it comes to CherryPy.
Everywhere you go , all you see is info about Flask/Django etc. I look at
their
Hello World examples and scoff at how convoluted and messy they seem. What
is
CherryPy missing.
Recently I wanted to learn something new just not to stay rusty so I
researched
what to learn ( concerning python web frameworks) and couldnt decide.
CherryPy has about 1000 questions on StackOverflow , flask 18 times that,
and
Django about 8 times the amount of flask. Clearly less people are talking
about
CherryPy online which sometimes makes it harder to find a solution to
something
which is CherryPy specific, but I rarely encounter those issues.

I personally love CherryPy and everything about it, I especially love the
part
where I dont even know im using CherryPy because it never gets in my way, it
feels just like writing only python.

Considering future endeavors is it a good decision to keep using CherryPy
or
learn something which is more marketable/popular/hip?

[irrgit]

[Joseph S. Tate]

It's not dead. It does its job and stays out of the way. It's still widely used. It's mature, so it doesn't need large sweeping changes.

--
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-user...@googlegroups.com.
To post to this group, send email to cherryp...@googlegroups.com.
Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.

[Andrew Maizels]

It just works, so there's fewer changes and fewer questions.  I'm glad the devs haven't tried to turn it into a Djangoesque platform.

It's worth also learning Django, but keep CherryPy in your toolbox.

To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe@googlegroups.com.
To post to this group, send email to cherrypy-users@googlegroups.com.

Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "cherrypy-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe@googlegroups.com.
To post to this group, send email to cherrypy-users@googlegroups.com.

Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.

--

Ahh... We are all heroes; you and Boo and I.
Hamsters and rangers everywhere, rejoice!
Read Peopleware! http://www.amazon.com/Peopleware-Productive-Projects-Teams-Second/dp/0932633439

[irrgit]

Apologies for the double post.  I like the part where it just works and doesn't get in your way. I will also try to learn Django and/or Flask.
Another question came to mind.

Is there a need to use uWSGI with CherryPy? Usually i just put nginx in front and be done. But Ive seen  setups with uWSGI as well.

[Joseph S. Tate]

I've mostly done the NGINX thing, though I have used uwsgi for some small apps, I think for small sites, nginx is fine, but when you start to need more than one GIL, uWSGI steps in nicely. Beats having multiple config files and supervisor for managing all those processes, the orchestration of which has caused a number of problems in trying to build a zero downtime deployment system.

--
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-user...@googlegroups.com.
To post to this group, send email to cherryp...@googlegroups.com.

[David Allouche]

Here, we use cherrypy for our main product, with some decent traffic. It's not "web scale" and it does not involve tons of virtualized servers, but it's definitely at the scale where bottlenecks are visible and brittle code breaks. And cherrypy is not one of those.

It's simple and extensible, and does everything we need it to. And when I have a question, I just look at the source code.

If you need to convince investors, or potential recruits, with the latest trendy stuff, it might be a good idea to use something else. But if you need a simple, reliable, mature, and battle-hardened micro framework for Python, I would definitely recommend cherrypy.

--

[Michiel Overtoom]

Hi Irrgit,

Our main web site is served for years now by CherryPy, and we have no reasons to migrate to other systems. It is fronted with nginx.

I do have to add some extra insight to the conversation tho, and that is why I chose CherryPy over other Python web frameworks almost a decade ago, when I had to make choices about which web framework to choose. That is because I had to build a website that could accomodate 1800 different domains. After some questing I found a good candidate: CherryPy's 'VirtualDispatch' was the most adjusted to my wishes, much more so than Django or Flask (which didn't even exist at that time).

Since then, CherryPy has stuck and has never let us down. We use it for simple webservice endpoints also.

Greetings,

[Andrea Esuli]

I just joined to support this message. 

Cherrypy is well alive.

It works, it is simple, clear, effective.

Minimal, but not missing any relevant feature. 

Yet, not clogged with tons of feats that are unrelated with its core goal.

It is very pythonic.

I'm using it in a project involving many other packages (sqlalchemy, mako templates, sklearn,...) and it fits perfectly with all the other components. Love it.

To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-user...@googlegroups.com.
To post to this group, send email to cherryp...@googlegroups.com.

Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-user...@googlegroups.com.
To post to this group, send email to cherryp...@googlegroups.com.

Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.

[matt Gerwen van]

I try for a year to make an app/webab with cherrypy and shortly I like to make it an SPA(Single Page App) with React. React version 0.13 - 0.14 is supported. When I try to use React Native or Fibre (version 16) then nothing seem to work. I only looked at Flask documentation and saw they support version 15 of React. That is much better. By the way Netflix is using Flask as python webframe work and no more Cherrypy as I understand there explaination. So I go for a closer look at Flask.

With kind regards.