These are chat archives for cherrypy/cherrypy

16th
Jun 2016
David Allouche
@ddaanet
Jun 16 2016 16:33
O hai guys!
So, I'm a firm believer of "If it's not broken don't fix it"
And I have this 10 years old code base running Cherrypy 3.1.2
But I just found out that the session tool there does not provide httponly cookies
So it's broken
So I need to upgrade
But, for the life of me, I was not able to find Cherrypy release notes anywhere.
Any clue where I could find something like that, so get a clue as to which version I want to upgrade to, and what I need to change
Joseph S. Tate
@josephtate
Jun 16 2016 16:35
They're broken up into WhatsNewIn## pages, like https://bitbucket.org/cherrypy/cherrypy/wiki/WhatsNewIn33
(I'm sure they've been moved to github too)
David Allouche
@ddaanet
Jun 16 2016 16:36
Cool
Maybe a stupid question, but if there would be any known unexpected regression bug in any release, would they be mentioned there?
"We do not have unexpected regressions" is an acceptable answer, of course :-)
Joseph S. Tate
@josephtate
Jun 16 2016 16:38
No, I don't think so. You can survey the issue tracker. There aren't that many.
David Allouche
@ddaanet
Jun 16 2016 16:38
okay
David Allouche
@ddaanet
Jun 16 2016 16:43
It does not look like there's any wiki on github: https://github.com/cherrypy/cherrypy/wiki
Nor am I able to find any release note beyond 3.3… :worried:
I think I'll just clone the repo and look at the code. Not ideal, but hey… Use the force...
Joseph S. Tate
@josephtate
Jun 16 2016 16:49
4.0 happened in December, 5.0 in Feb, and that's where we are now.
Semver....
David Allouche
@ddaanet
Jun 16 2016 16:49
Yeah, I heard it's the fashionable thing. Personally I do not care either way. A number is just a number.
I'd be happier with release notes, but you get what you pay for.
Joseph S. Tate
@josephtate
Jun 16 2016 16:50
I actually like bitbucket's commits view better than Githubs: https://bitbucket.org/cherrypy/cherrypy/commits/all
There are only 3 pages of commit messages to look at to get back to 3.3
David Allouche
@ddaanet
Jun 16 2016 16:51
Yeah, cool, this one is actually usable.
Joseph S. Tate
@josephtate
Jun 16 2016 17:31
@ddaanet If you start a WhatsNewIn page for 4.0 and 5.0, that'd be much appreciated
Paulo Vital
@pvital
Jun 16 2016 18:35
@josephtate, howdy. back to the engine.block() case, do you know any other case where cpu consumption is high when server is in idle mode?
Joseph S. Tate
@josephtate
Jun 16 2016 19:21
@pvital the engine is a classic pub/sub system. There is a timer on the main thread that creates new events to publish, but there are no default listeners on that event. The timer runs every 10s by default IIRC.
but cpu consumption should be near 0 between events
if no network traffic occurs, that is.
Have you checked to see if the cpu consumption happens on a hello-world sample app? or only when your app is mounted?
Paulo Vital
@pvital
Jun 16 2016 20:04
@josephtate, no cpu consumption when running the hello-world sample.
but my app is not using quickstart() - we do, tree.mount(pllugin), engine.start() and engine.block()
Joseph S. Tate
@josephtate
Jun 16 2016 20:05
Any subscribes?
Paulo Vital
@pvital
Jun 16 2016 20:07
cherrypy.engine.timeout_monitor.unsubscribe(); cherrypy.engine.subscribe('exit', terminate_proxy); if hasattr(cherrypy.engine, 'signal_handler'): cherrypy.engine.signal_handler.subscribe()
Joseph S. Tate
@josephtate
Jun 16 2016 20:21
So it would be interesting to see which of those handlers the quickstart uses
Maybe this is a red herring, but as far as I know, the only thing that the main thread runs is the engine and its plugins.