Skip to main content

PyScripter

Oooo, shiny. PyScripter is awesome. From my spoilt python brat wishlist we have:
  1. Tabbed interface like Notepad++ and SciTE [CHECK]
  2. Remember session like Notepad++ [CHECK]
  3. Code context like IDLE editor [And More CHECK]
  4. Line numbers like SciTE [duh, CHECK]
  5. Adjustable tabbing and smart indent like SciTE (And not like IDLE; shudder) [OK, can't figure this out, but at least it does not mess up my existing indenting]
  6. Autocompletion like IDLE [And More CHECK]
  7. Debugger would be nice, but IPython happens to be all I need right now for that [CHECK]
  8. Folding [Ok, this seems to be missing]
In addition the little things I noticed were:
  1. Picture of bug before file name in tab, when file has a parsing error. Sweet touch

Labels:

Comments

  1. PyScripterMay 19, 2008 at 3:52 PM

    PyScripter does support debugging both using the internal and a remote Python engine.

    ReplyDelete
  2. AnonymousApril 17, 2010 at 9:34 AM

    don't forget you can ctrl-click any identifier or function and jump to its source. even for built-in library stuff. it makes Django coding so much less of a mystery :)

    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
Post a Comment
Read more

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
Post a Comment
Read more