Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Tree [fb1c79] default / qt / ScintillaEditPy /

File Date Author Commit
README 2012-05-29 nyamatongwe nyamatongwe [cdf405] Information about running on Fedora.
ScintillaConstants.py.template 2012-05-17 nyamatongwe nyamatongwe [3f4a45] Qt platform layer added. Based on an implementa...
ScintillaEditPy.pro 2013-05-06 Neil Hodgson Neil Hodgson [fb1c79] Bug: [#1448]. Detect QT 5.x and add widgets to ...
global.h 2012-05-17 nyamatongwe nyamatongwe [3f4a45] Qt platform layer added. Based on an implementa...
sepbuild.py 2012-07-16 Neil Hodgson<nyamatongwe@scintilla.org> Neil Hodgson<nyamatongwe@scintilla.org> [0b0228] Clean up more generated files when run with --c...
testsepq.py 2012-09-20 Neil Hodgson<nyamatongwe@scintilla.org> Neil Hodgson<nyamatongwe@scintilla.org> [180792] Fix example PySide code to match current API.
typesystem_ScintillaEdit.xml.template 2012-05-17 nyamatongwe nyamatongwe [3f4a45] Qt platform layer added. Based on an implementa...

Read Me

README for building of ScintillaEditPy on Qt with PySide

This directory is for building a Python encapsulation of Scintilla for use
with PySide. For C++ libraries see the README in the parent directory.

PySide and ScintillaEditPy currently only support Python 2.x.

CMake may be used to rebuild PySide and is required on Windows.
It can be downloaded from

On Windows, PySide only supports Visual C++ 2008. The "Visual Studio 2008
Command Prompt" should be used to run all build commands.
Visual C++ 2008 Express Edition can be downloaded from

Download and install PySide. Instructions are on the PySide web site

For Linux, there may be both PySide library packages and PySide development
files. Both should be installed as ScintillaEditPy needs the headers and
libraries from the development package and runs with the normal library package.
On apt-based systems, the packages are libshiboken-dev, shiboken, libpyside-dev,
and python-pyside. python-dev is also needed for Python language headers.
On yum-based systems the packages are shiboken-devel, python-pyside-devel,
and python-devel.
The qmake program may not be in the path and can be found with
"find /usr -name qmake".

On Windows, the PySide library packages can be downloaded from 
The PySide development files must be built from source using CMake as 
described on the PySide site. This will create a Unix-style set of [bin, include,
lib, and share] directories in packaging\setuptools\install-py<ver>-qt<qver>. 
There is no standard place for the PySide development files so copy them
to "\usr", creating it if needed.

On OS X, a combined package with PySide libraries and PySide development
files can be downloaded from 
This package works best in combination with the Qt libraries for Mac from

The path should be modified so that a Python 2.x interpreter and Qt's "qmake"
program can be run by typing "python" or "qmake".


There are several steps to building and they are encapsulated in the sepbuild.py
script which is run:

python sepbuild.py

This script first runs the WidgetGen.py script to fill out the ScintillaEdit.h, 
ScintillaEdit.cpp and ScintillaConstants.py files.

A short file "sepbuild.pri" is written out which contains a series of version and 
path properties discovered by sepbuild.py which are used by qmake.

Then it runs PySide's "shiboken" program to create C++ code that will act as a
bridge between Python and the C++ libraries. This code goes into the 
ScintillaEditPy/ScintillaEditPy directory. Several log files are produced which can
help uncover problems in the bridge if it fails to build.

The qmake program is run to produce make files from ScintillaEditPy.pro.

The system make program is then run to build the library. The library is located in
the scintilla/bin directory as ScintillaEditPy.so for Unix systems and 
ScintillaEditPy.pyd for Windows.

A demonstration program can be run:

python testsepq.py

The individual steps in the script can be run manually if wanted although the
shiboken program has complex arguments and differs between systems so run 
sepbuild.py and copy the section starting with a line containing "generatorrunner"
and continuing to "typesystem_ScintillaEdit.xml".

On Windows, it is more difficult to set up an environment to debug ScintillaEditPy
since all the libraries have to be debug or all have to be release. The easy path 
is to always build for release with "nmake release".

To remove generated code, run "python sepbuild.py --clean".