Leo 5.3 was working fine for me for quite some time.
Without any (known) changes Leo stopped working :-(
Here are the relevant tracebacks
<TB-01>
File "C:\Users\Viktor\Programs\leo53\leo\core\leoGlobals.py", line 5910, inos_path_finalize
path = os.path.abspath(path)
File "C:\Python35\lib\ntpath.py", line 535, in abspath
path = _getfullpathname(path)
ValueError: _getfullpathname: embedded null character
PS C:\Users\Viktor\worklogs>
--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+...@googlegroups.com.
To post to this group, send email to leo-e...@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
Hello Edward,Thanks for your quick feedback!
Here are the new tracebacks, when I call it with an explicit outline argument
!!! What irritates me is that something changed *without* any (known) update to Leo *or* Python !!!
--
Hello Edward,
I would accept that *somehow* one file(-name) changed - but - I'm sure you saw that I also started Leo w/o an explicit outline argument ...
Please let me know if there is anything else you want me to deliver. - Otherwise I plan to completely erase this environment ...
On Tue, Jun 28, 2016 at 1:21 PM, Viktor Ransmayr <viktor....@gmail.com> wrote:Hello Edward,I would accept that *somehow* one file(-name) changed - but - I'm sure you saw that I also started Leo w/o an explicit outline argument ...
--
Hello Edward,
I would accept that *somehow* one file(-name) changed - but - I'm sure you saw that I also started Leo w/o an explicit outline argument ...
Please let me know if there is anything else you want me to deliver. - Otherwise I plan to completely erase this environment ...
I can & will wait until the weekend - but - no longer.
Leo 5.3 was working fine for me for quite some time.
Without any (known) changes Leo stopped working :-(
Here are the relevant tracebacks
This is a bug in python, not matplotlib. The issue is that winreg.EnumValue
is not cutting string values at their length properly for some reason, and strings will include null characters which os.path.abspath
is not able to process.
QQQ
On Monday, June 27, 2016 at 1:40:35 PM UTC-5, Viktor Ransmayr wrote:Leo 5.3 was working fine for me for quite some time.
Without any (known) changes Leo stopped working :-(
Happily, I think we can say, the same thing just happened to me when I installed Python 3.5.2 on Anaconda 4.2.0 on my Win 10 laptop. This was a pretty clean install: I uninstalled lots of old pythons first.
Rev 2e1137 works around this problem in an inelegant, but probably completely safe way.Here are the relevant tracebacks
[Snip]File "C:\Users\Viktor\Programs\leo53\leo\core\leoGlobals.py", line 5910, in os_path_finalize
path = os.path.abspath(path)
File "C:\Python35\lib\ntpath.py", line 535, in abspath
path = _getfullpathname(path)
ValueError: _getfullpathname: embedded null character
Googling the exact error message (ValueError: _getfullpathname: embedded null character) yielded this page.
QQQThis is a bug in python, not matplotlib. The issue is that
winreg.EnumValue
is not cutting string values at their length properly for some reason, and strings will include null characters whichos.path.abspath
is not able to process.QQQ
The last post for this issue was in January. That's not good enough, as I say here.