Skip to main content

Installing Eric4

Eric4 is more involved to install than SPE.

Install SIT
ftp http://www.riverbankcomputing.co.uk/static/Downloads/sip4/sip-4.7.7.tar.gz
python configure.py
make
sudo make install

Install PyQT
ftp http://www.riverbankcomputing.co.uk/static/Downloads/PyQt4/PyQt-mac-gpl-4.4.3.tar.gz
python configure.py
make
sudo make install

Install QScintilla
ftp http://www.riverbankcomputing.co.uk/static/Downloads/QScintilla2/QScintilla-gpl-2.3.tar.gz
cd Qt4
qmake qscintilla.pro
make
sudo make install
Now make the Qsci module
cd ../python
python configure.py
make
sudo make install

Now install Eric
sudo python install.py

Comments

  1. Can you please explain in the manner you have done above on how to install Eric4 in Windows OS (Windows XP)

    ReplyDelete
  2. Hi Rupesh,

    sorry but I don't work on an XP machine anymore, so I can't help you there.
    Best

    ReplyDelete
  3. command qmake qcsintilla.pro

    creates qscintill2.xcodeproj file and does not creates Makefile. Hence I cannot run make. But I opened this project in XCode and built it with XCode. I got the build/Release/libqscintilla2.dylib

    how should I behave instead of install utility myself further? )

    Thank you for your reply in advance.
    Sergey

    ReplyDelete
  4. I've just installed eric4 and created an installation guide that worked for me. You may find it here:

    http://www.dmeisel.de/pub/python-windows-install.htm

    Best regards,
    David

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...