Sunday, September 2, 2007

Winpdb 1.2.2, wxGlade0.6 & XRCed 0.1.8-5...

...all landed in subversion (rev255). wxGlade and XRCed are taken from their repositories, so they might be bleeding edge. Thanks to Diaa Sami some issues on Windows are fixed (eg running files with spaces). Check out the new SPE in the usual way:
svn checkout svn://


  1. Looks like plenty of very interesting improvements. Kudos! :)

    I haven't add the pleasure to test it yet though, as there seems to be still some Unicode issues under Windows. Here's the end of the debug log:

    Event>: Tab: «class 'sm.wxp.smdi.MdiSashTabsParentFrame'>.onFrameTab(1)
    Traceback (most recent call last):
    File "", line 227, in «module>
    style = style)
    File "C:\Python25\Lib\site-packages\_spe\sm\wxp\", line 1340, in __init__
    wx.App.__init__(self,redirect=not debug)
    File "C:\Python25\lib\site-packages\_spe\tabs\", line 51, in add
    File "C:\Python25\lib\site-packages\_spe\tabs\", line 56, in update
    self.files = [(os.path.basename(str(file)),file) for file in self.files]
    UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 54: ordinal not in range(128)


  2. Can you replace str with unicode in "C:\Python25\lib\site-packages\_spe\tabs\", line 56, in update
    self.files = [(os.path.basename(unicode(file)),file) for file in self.files]

    Let me know if works.

  3. Thank you very much for the reply. :)

    Using the latest build as of today:

    At first it didn't work, but I deleted the "Documents and settings\[profile]\.spe" folder with the history and it worked perfectly, even after reopening a few times SPE with a long path name.

    Interestingly, while the default ascii version throws the previously mentioned exception, it loads correctly.


  4. I updated to the most recent version but like a few others I've seen, I'm having keyboard mapping problems.

    Most of the keypad [.0-9] are drawing unicode characters (only when Numlock is off; with it on, numbers appear as normal).

    A number of the Function keys also produce similar effects (F1, F2, F4, F6, F7, F8, and F11).

    In the footer bar I am seeing "exceptions.UnicodeEncodeError instance at [address]" after having pushed any such key; after deleting the characters that appear the error goes away.

    My system is built with unicode support; the keyboard mapping is US English standard; your editor looks really great for working in Python but I just can't get used to not using the cursor and function keys. Any help you can provide would be appreciated!

  5. I suppose I should have added I'm using Linux as well, and Python 2.4. If there's any kind of log output I can give you to help debug, please let me know.

  6. Do you follow this pep 263 for declaring the encoding in your files?

  7. I don't declare file encodings as they're always ASCII (I don't put unescaped Unicode characters directly into my source files).

    I tried for the record, though -- No difference; the problem occurs from the very first keystroke in a new file, or in any other file loaded, whether the encoding is declared or not. I also changed the 'Preferences > General > Encoding' setting to "default", "ascii", "latin1/iso-8859-1" and "utf-8" but it made no difference.

  8. I just rebuild wxpython without Unicode support to see what would happen -- It definitely seems to be related to the problem.

    Now when I click keys that used to produce errors nothing happens; that is to say, I don't see any Unicode symbols appear in the document, but the keys don't do anything; they are effectively dead.

  9. Last comment, I promise. I corrected the issue and tried to submit a patch to your Berlios project, but the site is very slow and the upload timed out. You can find the patch:

    Thank you for your continuing hard work on this project, Stani!

  10. Thanks, I've accepted the patch and fixed two other smaller issues.

  11. Hello!

    First of all: Thank you! SPE is an amazing tool for my everyday work.

    I'm up to date (rev265) and from a few weeks ago I'm experimenting troubles with crashes.

    To reproduce the 'bug':
    - Select any piece of code and click once or twice over this selection.

    The pointer is blocked and the cursor change into a kind of angle. I can still write but only in the current tab. I can't change tabs neither change the window (control+tab doesn't work).

    Please tellme if it is a bug or is a 'local' problem, and how we can solve it.

    Thanks in advance

    PS: sorry about my poor english.

  12. @martin

    I can't reproduce the bug on Ubuntu Feisty. Please provide details about your os and versions.

    The code which is called is in _spe/sm/wxp/ (line 189):
    def OnLeftDown(self,event):
    if not event.ShiftDown():

    Maybe you can replace it by:
    def OnLeftDown(self,event):
    #if not event.ShiftDown():
    # self.SetSelectionEnd(0)

  13. Hey you!

    Your IDE looks really good! cant wait to do really hard work on it. hehe!

    but how can I change the background and font colours of the editor? white screens tire my eyes really quickly.


  14. There is no dialog to change the colours. You have to patch SPE yourself in _spe/sm/wxp/

    First, Many thanks for the great IDE, all the work and keeping it free and Open. I hope Pyxides brings together "something completely different".
    I can't get any .py or .pyw file to run in the debugger in Stani's SPE for windows. I run XP Pro, Python 2.5 and the newest SPE 0.8.4b. My python is in c:\Python25. I check change working directory to that of script in the debug pop up window but even unchecked i get the same error, "windows:Error [Error 13]The process cannot access the file because it is being used by another process.
    I am new to Python and SPE and Winpdb and so may be doing something noobie silly in my settings. Any help will be very much appreciated because i want to learn how to debug my programs and Winpdb has been rated very highly.
    Thank you for your assistance, Markandeya

  16. Thanks winpdb now works on ubuntu!

  17. Spe is not working with gutsy RC @_O. It
    conplains about wxpython's version.

  18. From svn, it works. The problem is with spe in the gutsy repository ^^

  19. If I use the SVN version, will it work with the latest wxPython? If not, can you point me to a place where I can download the correct old version of wxPython? The earliest version I can see on the wxPython site is 2.6.33.

  20. Ah, sorry, found the sourceforge link.

  21. @tony

    The only good version of SPE now is in svn: 0.8.4.b. It runs with the the latest wxPython. Running an older version is not recommended.

  22. Hey there!

    I just found this really nice IDE and I've got to say, I'm pretty impressed how well you did the job. It's a real joy to work with all the well-integrated tools. Keep up the good work!

  23. i am not able to checkout the source. the error i was getting is "the target system actively refuses the connection" but i am able to browse it through the websvn interface.

  24. I get the same error as above.

    Any tips would be helpful:

  25. Does it matter whether one uses ansi or unicode for wxpython?


Filter by topic: spe, python, ubuntu