On 6/1/2013 12:10 AM, Matt Wilkie wrote:
Hi Jake, thanks for the offer to help out.
TODO (elaborated on in further messages, which may take a while to
write):
- fix py3.x installer bug
Do you have an error log on this? I suspect it's related to one of 2
things:
Not a full traceback, just one line "ImportError: No module named
__builtin__", reported on the last step of the install, after compilng
.pyc/.pyo files. There's something that zips by just prior but I
haven't been able to catch it.
That import statement doesn't exist in leo-install.py.
The last few lines of PYTHONHOME\leo-wininst.log are:
{{{
200 File Copy: C:\Python32\Lib\site-packages\leo\core\bzr_version.pyo
200 File Copy: C:\Python32\Lib\site-packages\leo\__init__.pyo
300 Run Script: [python32.dll]C:\Python32\Scripts\leo-install.py
*** Installation finished 2013/05/31 21:03 ***
}}}
-matt
That may be a bug with distutils/setuptools or your environment...
perhaps your python3 is using the python2 copy of that library?
In either case, I found only a few (properly guarded) uses of 'import
__builtin__' in the Leo core and plugins, and none in the setup, so I
think it's an environment issue. Perhaps a 2to3 step is being skipped
somewhere?
If it helps, the module has been renamed to 'builtins' (no underscores,
and added an s) in python 3.
-->Jake
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
