Hi Dennis,
It's been a while since I've used this code, but in the early days it was
indispensible. I think you have the right ideas on making it more useful
now that we're hacking on the bytecode again. Since lltrace is most useful
when the bytecode interpreter is somehow faulty, it doesn't make
Whoops, you’re right. I suppose I should have no opinion on whether to
deprecate it; I haven’t thought about it for over two decades…
On Thu, Apr 14, 2022 at 16:33 Jelle Zijlstra
wrote:
>
>
> El jue, 14 abr 2022 a las 12:21, Damian Shaw ()
> escribió:
>
>> > I searched grep.app and found no
El jue, 14 abr 2022 a las 12:21, Damian Shaw ()
escribió:
> > I searched grep.app and found no significant usage.
>
> Maybe someone wants to inform mitmproxy?
>
> It's a very popular tool and it comes up using that tool when searching
> for "import mailcap" using grep.app:
>
Hi everyone,
I'm looking to improve the output of the interpreter's LLTRACE feature to make
it more understandable. This "feature" is undocumented, but it prints out the
opcode and oparg of every bytecode instruction executed, along with some info
about stack operations, whenever you've built
+1 add it to the 3.11 deprecations and proactively reach out to the
mitmproxy owners.
(internal code search: aside from mitmproxy I only see a _single_ use of
this in our codebase and it was simply convenient but has a clear simpler
alternative assuming that ~2008 era code is even still in use)
On Thu, Apr 14, 2022 at 12:04 Jelle Zijlstra
wrote:
>
>
> El jue, 14 abr 2022 a las 11:47, Brett Cannon ()
> escribió:
>
>> Do you know why this module wasn't included in PEP 594?
>
Probably because it’s not a top level module — it’s inside the email
package.
Should we do another audit of old
> I searched grep.app and found no significant usage.
Maybe someone wants to inform mitmproxy?
It's a very popular tool and it comes up using that tool when searching for
"import mailcap" using grep.app:
https://grep.app/search?q=import%20mailcap
El jue, 14 abr 2022 a las 11:47, Brett Cannon () escribió:
> A CVE has been opened against mailcap (see
> https://github.com/python/cpython/issues/68966 for details). I'm not
> aware of anyone trying to maintain the module and Victor did a search
> online and didn't find any use of the module in
A CVE has been opened against mailcap (see
https://github.com/python/cpython/issues/68966 for details). I'm not aware
of anyone trying to maintain the module and Victor did a search online and
didn't find any use of the module in the top 5000 projects on PyPI (see the
issue). The module is also
