Comment # 7
on bug 8453
from Evan Huus
(In reply to comment #6)
> I suggested the same at the last Sharkfest. The opinion then was that
> somebody'd put a lot of effort into it so it would be a shame to throw it
> away. But maybe we should talk about it again.
>
> Meanwhile, I've seen seen 2 RPM .spec files from 2 Linux vendors which
> specifically enable Python (despite our having downgraded its status in
> "configure --help" output to BROKEN/UNSTABLE in 1.8). Maybe at the very
> least we should change the option to enable it to
> "--with-python-yes-I-really-mean-it-I-want-to-fix-it" or something like
> that. :-)
Perhaps send an email out to Sebastien (who wrote the original bindings), Eshed
(who wrote pyreshark) and both maintainers who've been enabling python? Ask for
either somebody to step up, or if everyone would be happy if we merged
pyreshark instead (with Eshed maintaining it), or some other concensus?
There may be a lot of interest from the community, but it seems like nobody in
-core is much interested in python anymore. Skimming the .py scripts in tools/,
it looks like they were written entirely by developers who are no longer very
active.
You are receiving this mail because:
- You are watching all bug changes.