I thought it was silly at first, but then found it easier on the eyes and
quicker to confirm what's enabled. Still, requesting a change to the core
language/library through additional code (with the inevitable introduction
of more bugs) in order to support some syntactic sugar that really doesn't
:) I'd imagine we all do, but that brings up an interesting point. This
would obviously be most seen in .py files. One can just imagine projects
w/ various libraries from different third parties with different coding
standards with check marks in some modules or even in some functions in the
same
:) I'd imagine we all do, but that brings up an interesting point. This
would obviously be most seen in .py files. One can just imagine
projects w/ various libraries from different third parties with
different coding standards with check marks in some modules or even in
some functions in the
Hi John,
Your .ini file looks very cool :)
It may be worth bearing in mind that the check mark can have different
connotations in different cultures. When I grew up in Sweden it was used to
highlight exam questions that I answered incorrectly.
There is some more information about this on
Recently I was setting up configuration for a new project and was trying
to do the obvious thing in my .ini:
pyramid.reload_templates = ✔
pyramid.debug_authorization = ✖
pyramid.debug_notfound = ✖
pyramid.debug_routematch = ✖
pyramid.debug_templates = ✔
To my surprise, the checkmark did
