Closed philipstarkey closed 6 years ago
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Doing .encode('utf8')
on the filepath makes sense, and the other problem I would say is a zprocess bug, which I've fixed in zprocess 2.1.1 (released on PyPI so pip install --upgrade zprocess
will get it).
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Fix issue #28, handle unicode in analysis routine filenames
→ \<\<cset a4135b74151d9b8bdb82a74ebf197cadc1d16ce4>>
Original comment by Philip Starkey (Bitbucket: pstarkey, GitHub: philipstarkey).
This is not actually fixed as the changeset in the pullrequest was backed-out before merging
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Resolved by pull request #22
Original report (archived issue) by Jan Werkmann (Bitbucket: PhyNerd, GitHub: PhyNerd).
If you import scripts into lyse that include non ascii characters in their name (such as german Umlauts) the script will not run.
If you modify analysis_subprocess.py in line 288 in the following way scripts will run:
However if that script then crashed lyse will crash along with it and give you this traceback: