[wingide-users] using scripts when installing python in non-standard locations

Wingware Support support at wingware.com
Thu Jul 11 09:35:48 EDT 2013


Marcin Krol wrote:
> C:\>C:\soft\Anaconda\python.exe  "C:\soft\Wing IDE
> 4.1\scripts\pep8panel.py" --repeat --statistics
> C:\tmp\tortoise_post_commit_hook.py
>
> Traceback (most recent call last):
>    File "C:\soft\Wing IDE 4.1\scripts\pep8panel.py", line 74, in<module>
>      import wingapi
>    File "C:\soft\Wing IDE 4.1\bin\wingapi.py", line 18, in<module>
>      import edit.editor
> ImportError: No module named edit.editor

The pep8checker is a script so you put it in the scripts directory in 
your User Settings Directory (listed 5th in Wing's About box) and then 
select Reload All Scripts from the Edit menu.  Then you should have the 
PEP8 panel appear in the Tools menu.

They have to be in the same process space as Wing so don't work in the 
Python Shell or debugger unless you have the Wing sources and run the 
entire IDE in the debugger.

-- 

Stephan Deibel
Wingware | Python IDE
Advancing Software Development

www.wingware.com


More information about the wingide-users mailing list