These are chat archives for cherrypy/cherrypy

31st
Oct 2016
Sviatoslav Sydorenko
@webknjaz
Oct 31 2016 01:26
@dwich I am subscribed to http://stackoverflow.com/questions/tagged/cherrypy and I do answer questions when I have time. Go and do this as well :)
P.S. And there's just one person commitment left @ http://stackoverflow.com/documentation/cherrypy/commit to unlock SO documentation
@/all
blstdmi
@blstdmi
Oct 31 2016 09:49
ok. thx
Jason R. Coombs
@jaraco
Oct 31 2016 13:08
My primary reluctance to commiting to Stack Overflow docs is that it creates yet another forum for the documentation. Do we have the energy it will take to make sure that the current documentation is kept consistent and minimally duplicative of documentation on SO?
@webknjaz ^
Nicklas Börjesson
@nicklasb
Oct 31 2016 14:09
WRT documentation, I feel its good were it is. What are the added benefits of having docs att SO?
Sylvain Hellegouarch
@Lawouach
Oct 31 2016 14:41
I think we don't have the energy to run multiplaces but a community can also grow in various venues. If folks are fluent with SO, maybe that's worth we try it out.
Sviatoslav Sydorenko
@webknjaz
Oct 31 2016 14:47
The point is to add some representative usage examples to SO, since it's commonly much more googlable, than other places on the internet. Still the official framework/api documentation looks good at the current location.
SO docs could contain recipes on how to combine lots of stuff, which is usually not what you'd want to put into docs.
Sylvain Hellegouarch
@Lawouach
Oct 31 2016 14:58
That's definitely fine by me

/all this :)

P.S. And there's just one person commitment left @ http://stackoverflow.com/documentation/cherrypy/commit to unlock SO documentation

Nicklas Börjesson
@nicklasb
Oct 31 2016 14:58
By me as well, good idea.
Jason R. Coombs
@jaraco
Oct 31 2016 16:01
okay. let’s give it a go.
Sviatoslav Sydorenko
@webknjaz
Oct 31 2016 16:16
:tada: It's now available and open for contributions @ http://stackoverflow.com/documentation/cherrypy
Sylvain Hellegouarch
@Lawouach
Oct 31 2016 16:25
great :)
Sylvain Hellegouarch
@Lawouach
Oct 31 2016 16:43
I pushed a new tweet about it
blstdmi
@blstdmi
Oct 31 2016 20:48

help to understand,
here Flask study, written
"You can use the builtin server during development, but you should use a full deployment option for production applications. (Do not use the builtin development server in production.)"

but in CherryPy put it?
and then on top and the flask rolled..
don't understand.. what is different all so similar.

ps.. tried to ask questions on stackoverflow, all unsuccessfully

blstdmi
@blstdmi
Oct 31 2016 21:38
the answer is that flask is just an add-on to Werkzeug?
Nicklas Börjesson
@nicklasb
Oct 31 2016 21:40
@blstdmi I am sorry, really sorry, but I am not sure that I understand what you mean.
CherryPy has no relation to Flask. They are different frameworks.
blstdmi
@blstdmi
Oct 31 2016 21:41
trying to understand the differences of how it works