#93 regression in _trim_arity

[user]

In a nutshell, _trim_arity fails if the source code for the program in unavailable, e.g. when compiling executables with PyInstaller. This is due to traceback.extract_tb returning None for exc_source_line and pyparsing calling exc_source_line.endswith()..

File "site-packages/pyparsing.py", line 803, in wrapper
AttributeError: 'NoneType' object has no attribute 'endswith'

https://github.com/mitmproxy/mitmproxy/issues/1087
https://docs.python.org/2/library/traceback.html#traceback.extract_tb

[Paul McGuire]

A candidate fix has been checked into SVN - please download and verify in your PyInstaller environment.

[Paul McGuire]

Fixed version checked into SVN, no longer relies on presence of source code
- please download and test in your PyInstaller environment.

Thanks,

-- Paul

From: user [mailto:maluwa@users.sf.net]
Sent: Thursday, April 21, 2016 7:08 PM
To: Ticket 93 93@bugs.pyparsing.p.re.sf.net
Subject: [pyparsing:bugs] #93 regression in _trim_arity

---

[bugs:#93] https://sourceforge.net/p/pyparsing/bugs/93/ regression in
_trim_arity

Status: open
Group: v1.0 (example)
Created: Fri Apr 22, 2016 12:08 AM UTC by user
Last Updated: Fri Apr 22, 2016 12:08 AM UTC
Owner: nobody

In a nutshell, _trim_arity fails if the source code for the program in
unavailable, e.g. when compiling executables with PyInstaller. This is due
to traceback.extract_tb returning None for exc_source_line and pyparsing
calling exc_source_line.endswith()..

File "site-packages/pyparsing.py", line 803, in wrapper
AttributeError: 'NoneType' object has no attribute 'endswith'

https://github.com/mitmproxy/mitmproxy/issues/1087
https://docs.python.org/2/library/traceback.html#traceback.extract_tb

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/pyparsing/bugs/93/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

---

This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[Paul McGuire]

Was fixed in 2.1.2, then fixed better in 2.1.3, just released.