On Sep 14, 5:39 pm, "Edward K. Ream" <[email protected]> wrote:
> This ends the work on edb. Next, I'll turn my attention to winpdb. Installing winpdb on Blender is a bit of trick. You can't just copy the package to Blender's python/lib folder and do python setup.py install, because that would install into the *python's* (say Python 2.6) lib folder, not *Blender's* lib folder. (Within Blender, sys.executable is blender.exe!) So I installed winpdb in Python 3.2, and then just copied the installation into Blender's lib folder, then deleted the contents of all the __pycache__ folders just to make sure that things would be recompiled with Blender's internal Python. I also did the same thing with the distutils module, which is not part of Blender's Python(!!) After adding the path to lib/winpdb-1.4.8 to sys.path, I attempted to import winpdb or rpdb2 from Blender's Python console, but both imports failed trying to load the module wxVersion. It may be possible to use winpdb or rpdb2 on Blender, but it doesn't seem easy. I am going to abandon this part of the project for now. If anyone figures out how to use winpdb (or pudb) with Blender, please let me know. For me, using edb is plenty good enough. It's time to return to the original project, namely documenting autocompletion in such a way that anyone can understand how to use it... Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
