> On 15 Apr 2019, at 22:07, Antoine Pitrou wrote:
>
> However, there are many contexts where implementation details would
> benefit from being hidden from tracebacks (the classical example being
> the internals of framework or middleware code, such as Django, Dask,
> etc.). We would therefore
On 4/15/2019 4:07 PM, Antoine Pitrou wrote:
Hello,
I apologize because I'm only going to throw a very vague idea and I
don't currently have time or motivation to explore it myself. But I
think it may prove interesting for other people and perhaps spur some
concrete actionable proposal.
With t
On Mon, Apr 15, 2019 at 5:07 PM Antoine Pitrou wrote:
>
> Hello,
>
> I apologize because I'm only going to throw a very vague idea and I
> don't currently have time or motivation to explore it myself. But I
> think it may prove interesting for other people and perhaps spur some
> concrete action
This is a really great idea. I’d also point to the awful hacks that jinja2
needs to go through to elide jinia2 frames from user tracebacks as an
indicator that this is a desired feature.
https://github.com/pallets/jinja/blob/master/jinja2/debug.py
On Mon, Apr 15, 2019 at 2:08 PM Antoine Pitrou w
On 15/04/2019 22.07, Antoine Pitrou wrote:
>
> Hello,
>
> I apologize because I'm only going to throw a very vague idea and I
> don't currently have time or motivation to explore it myself. But I
> think it may prove interesting for other people and perhaps spur some
> concrete actionable propos
Hello,
I apologize because I'm only going to throw a very vague idea and I
don't currently have time or motivation to explore it myself. But I
think it may prove interesting for other people and perhaps spur some
concrete actionable proposal.
With the growing complexity of Python software stac
