There seems to be an issue on mac, depending how the original Wireshark binary has been called. It seems to be, that by clicking on the icon, the system python interpreter get's loaded, which most certainly will let your script fail. If you call Wireshark from a console context (by either executing directly or with "open Wireshark.app", it seems to work fine.
Try executing through a login shell and it might work as intended. cheers Roland Am Fr., 12. Apr. 2019 um 22:21 Uhr schrieb Dario Lombardo <lom...@gmail.com >: > > On Fri, Apr 12, 2019 at 10:14 PM Dario Lombardo <lom...@gmail.com> wrote: > >> >> https://travis-ci.org/crondaemon/wireshark/jobs/519284280 >> >> >> This build actually comes from a tentative patch. A failing build on > master is at the following link. > > https://travis-ci.org/crondaemon/wireshark/jobs/519168819 > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe