I've had the same trouble and I solved it out using a pyscripter's option in the 'Tools' menu called 'Edit Startup scripts' which's name says it all.
Everything you write there should be executed whenever pyscripter starts a python interpreter so it can be used among other things to do the same as 'kivy.bat' but inside pyscripter, I wrote the following startup script basing on info from here How to develop and run kivy apps on PyDev and it works fine for me.
# This startup script makes it possible to Pyscripter to work with the kivy package
import sys
import os
kivy_path = 'C:/kivy'
relative_modules_paths = ['/kivy',
'/Python/',
'/Python/Lib/',
'/Python/Lib/Site-packages/',]
# tells the interpreter to look for python modules in the kivy modules' paths
for relative_path in relative_modules_paths:
sys.path.append( kivy_path+relative_path )
# sets some environment variables needed by kivy. Not permanent.
os.environ['GST_PLUGIN_PATH'] = kivy_path+'/gstreamer/lib/gstreamer-0.10'
os.environ['GST_REGISTRY'] = kivy_path+'gstreamer/registry.bin'
kivy_environ_paths = '{kp};{kp}/Python;{kp}/gstreamer/bin;{kp}/MinGW/bin;'
kivy_environ_paths = kivy_environ_paths.format( kp=kivy_path )
os.environ['PATH'] = kivy_environ_paths
# theorecally your environment variables won't be affected outside the
# interpreter. You can still backup your environment variables if you
# don't feel confident
Just change the kivy_path variable in the script so it fixes with the kivy package's path (folder containing kivy.bat) on your computer and you should be able to run your kivy apps just like when you open them with kiby.bat
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…