These are chat archives for cherrypy/cherrypy
CherryPy is a pythonic, object-oriented HTTP framework. | post your issues to: github.com/cherrypy/cherrypy/issues | FAQ: https://stackoverflow.com/questions/tagged/cheroot+or+cherrypy
For example, I talked to @jaraco privately about why requiring a test here: cherrypy/cherrypy#1432
Yes, there are cases were it is good to keep tabs on more subtle bugs that way.
However in that case, it felt like we were testing ntob and that it might do more to lock down the code and raise the bar for contribution than any actual good.
That ended up not turning out to be a problem, but as I have become more BDD:ish lately(however not purely, as I feel that they sort of both have their place), I have become a little bit more selective about testing.
Anyway, it would be good if we all knew where it’s at and why.
The module have pretty good module level descriptions in the code, but where they are in the system in general is, while obviously possible to understand, not easy to understand.
(I get push notification on my OSX app, you haven’t denied some gitter e-mail somewhere, I remember vaguely that I had some problems with that)