On Nov 10, 2007, at 1:43 PM, Philip Jenvey wrote:
Awesome. Like I mentioned to you on AIM, I sort of miss some of the color of the original Pylons skin, but that's not a big deal.
We can add back in color, or other CSS tweaks. The itraceback.css file in pylons/media is inserted at the top of the traceback if anyone wants to fiddle with it.
The Extra data section currently spits out 3 sections (they all have an 'Extra Data' header which is kinda superfluous), though one of them is blank. I see there's a hook to get the config dictionary displayed like it was before via environ['weberror.config']. When I manually added that to environ it showed up fine (so Pylons needs to do this somewhere), but there were now 4 sections, one of them still blank). Also, the Registry restorer stuff looks for EvalException under the key 'paste.evalexception' under environ, to know whether or not it should enable itself when there's an exception. The registry continues to work work in Pylons apps because RegistryManager is outside of EvalException, but restoration breaks if its inside of it (there's tests for this in Paste).
I'll make those appear in the variable list as well.
We can probably get away with renaming the keys if we also maintain the old ones, but get_debug_count might be a little odd to deal with. Keeping the old key names would be easiest fix, unfortunately
Hmmm, yea, I'll have to think about another way to handle that. For right now, we'll just have to hope ppl don't move the Registry around. But generally the Registry should *always* be as near the top of the call stack as possible anyways.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
