Re: [Pythonmac-SIG] ANN: ScrIDE 0.4

On Aug 4, 2006, at 4:01 PM, Christopher Barker wrote: > Bob Ippolito wrote: >> Also, you really shouldn't mix tabs and spaces in your source >> code. Ick. > > I haven't looked at ScrIDE yet, but it shouldn't allow mixed tabs and > spaces at all. In fact, it really should ONLY allow spaces. That

Re: [Pythonmac-SIG] ANN: ScrIDE 0.4

On Aug 4, 2006, at 3:12 PM, Bob Ippolito wrote: > > On Aug 4, 2006, at 11:32 AM, [EMAIL PROTECTED] wrote: > >> Version 0.4, the "PyOXIDE replacement" IDE is now available - it >> fixed several problems with 0.3, adds "context sensitive object >> info details" (to both the rich shells as well

[Pythonmac-SIG] ANN: ScrIDE 0.4

Version 0.4, the "PyOXIDE replacement" IDE is now available - it fixed several problems with 0.3, adds "context sensitive object info details" (to both the rich shells as well as debugger), and the ability to browse the variables in a rich shell (using a variable display like the debugger).ScrIDE i

Re: [Pythonmac-SIG] Adding Apps - Pycrust too?

> >> -bob > > Just tried, and neither the IDLE nor PyCrust > interactive shells supports wx (or any other gui > framework) out of the box. IDLE complains about > needing to use Pythonw, and PyCrust just hangs > (probably due to the issue Bob mentioned). > > If the interactive shell in IDLE can be

Re: [Pythonmac-SIG] indentation problem

On Mar 10, 2006, at 4:31 AM, altern wrote: > hi all > > i have been developing some tutorials with PyOxide and now i find that > when i open them on Smultron the indentation is wrong. Students are > vey > likely to be using Smultron (no need to insatall pyObjC). > I would strongly recommend s

[Pythonmac-SIG] ANN: ScrIDE 0.3

So in an attempt to finally get rid of the potential morass that further work on PyOXIDE could be, I'm release a very early version of ScrIDE, a generic, extensible, scripting IDE. There are several major differences between the two - first, ScrIDE is designed to support multiple scripting

[Pythonmac-SIG] ANN: ScrIDE 0.2

So in an attempt to finally get rid of the potential morass that further work on PyOXIDE could be, I'm release a very early version of ScrIDE, a generic, extensible, scripting IDE. There are several major differences between the two - first, ScrIDE is designed to support multiple scripting

Re: [Pythonmac-SIG] My stab at a new page

On Feb 10, 2006, at 11:27 AM, Bob Ippolito wrote: > > On Feb 10, 2006, at 7:24 AM, [EMAIL PROTECTED] wrote: > >> >> On Feb 9, 2006, at 1:32 PM, Kevin Walzer wrote: >>> If I'm a newbie, I'm going to go, "Huh?", then "shrug," and move >>> on to >>> Realbasic. There needs to be something double-cl

Re: [Pythonmac-SIG] My stab at a new page

On Feb 9, 2006, at 1:32 PM, Kevin Walzer wrote: > If I'm a newbie, I'm going to go, "Huh?", then "shrug," and move on to > Realbasic. There needs to be something double-clickable there for a > newbie to use. PythonIDE, though it had many flaws, was useful this > way. > BTW, what happened to PyO

Re: [Pythonmac-SIG] Build PyOxide

On Jun 9, 2005, at 9:27 AM, Brice Thurin wrote:Hello,  I have been trying to install PyOxide but without success. First I tried the installation package but how I installed macpython2.4, it can't install it apparentely the installation package is looking for the 2.3 version. So I decided to build i

Re: [Pythonmac-SIG] PyObjC vs "old school" embedding

On May 31, 2005, at 4:54 PM, Bob Ippolito wrote: >> >>> Somewhere in PyOXIDE you're not managing interpreter state >>> correctly, probably not in the code you've pasted, I don't have >>> time to look into it... >>> >>> >> >> Obviously you've got next week's session to get prepared for, but

Re: [Pythonmac-SIG] PyObjC vs "old school" embedding

On May 31, 2005, at 3:51 PM, Bob Ippolito wrote: > > On May 31, 2005, at 1:17 PM, [EMAIL PROTECTED] wrote: > > >> So PyOXIDE is based on the traditional way to embed python in an >> application (explicitly calling the python APIs to access and call >> stuff), and this worked reasonably well.

[Pythonmac-SIG] PyObjC vs "old school" embedding

So PyOXIDE is based on the traditional way to embed python in an application (explicitly calling the python APIs to access and call stuff), and this worked reasonably well.  For example, it runs various scripts at startup, which register various callbacks to handle things like new documents, new in

Re: [Pythonmac-SIG] PyOXIDE wishes?

On May 29, 2005, at 7:38 PM, Lance Boyle wrote: > This sounds like a good idea to me. The Mathematica editor does this > and I can't remember any problems caused by it. > > Jerry > > > On May 28, 2005, at 5:03 AM, altern wrote: > > >> hi >> >> maybe a bit late but there it goes. >> I have been do

Re: [Pythonmac-SIG] making a C extension compatible across OS versions?

On May 26, 2005, at 1:56 PM, has wrote: > Nicholas Riley wrote: > > >>> Obviously the extension needs to be built on Tiger to provide sdef >>> support, but what should I do to ensure that, say, applications >>> containing that binary extension will still work OK when run on >>> earlier OSes? >>>

Re: [Pythonmac-SIG] Python threading.Thread vs PyObjC performOnMainThread

On May 16, 2005, at 2:22 PM, Bob Ippolito wrote: > > On May 16, 2005, at 2:53 PM, [EMAIL PROTECTED] wrote: > >> I should be able to directly send the signal from the IDE to the >> targeted app (since it's a child of the IDE), and the standard >> "catch a unix signal invokes the debugger" act

Re: [Pythonmac-SIG] Python threading.Thread vs PyObjC performOnMainThread

On May 16, 2005, at 2:39 PM, Ronald Oussoren wrote: > > On 16-mei-2005, at 21:28, [EMAIL PROTECTED] wrote: > >> The problem isn't the Cocoa threads (Cocoa knows that the >> application is multithreaded). The problem is that the python >> code that is executing in a threading.Thread calls

Re: [Pythonmac-SIG] Python threading.Thread vs PyObjC performOnMainThread

On May 16, 2005, at 2:12 PM, Ronald Oussoren wrote: > > On 16-mei-2005, at 20:53, [EMAIL PROTECTED] wrote: > >>> >>> NO! That is really really horribly bad to do. Working around a >>> bug in PyObjC by writing code that will break in correct versions >>> of PyObjC is absolutely horrible. You sh

Re: [Pythonmac-SIG] Python threading.Thread vs PyObjC performOnMainThread

On May 16, 2005, at 1:22 PM, Bob Ippolito wrote: > > On May 16, 2005, at 2:01 PM, [EMAIL PROTECTED] wrote: >>> >> >> The debugged app works like that, but the way that the "remote >> object" interface works is also designed to use sync TCP on the host >> side. Since it's pure python, I didn't wan

Re: [Pythonmac-SIG] Python threading.Thread vs PyObjC performOnMainThread

On May 16, 2005, at 11:59 AM, Bob Ippolito wrote: > > On May 16, 2005, at 12:35 PM, [EMAIL PROTECTED] wrote: > > >> So I'm reworking how debugging is handled in PyOXIDE and I've come >> to a problem (several, but this is the biggy for the morning). >> >> My goal is to separate interacting with

[Pythonmac-SIG] Python threading.Thread vs PyObjC performOnMainThread

So I'm reworking how debugging is handled in PyOXIDE and I've come to a problem (several, but this is the biggy for the morning).My goal is to separate interacting with the (remote) debugged client in a separate thread, which forwards messages to the main thread as needed to run the debugger UI (si

[Pythonmac-SIG] [PyOXIDE] Drop support for 10.2?

So given that 10.4 is currently available, I'm considering dropping support for 10.2 from future versions of PyOXIDE. I'm aware that there is at least one user still on 10.2, not sure about others. Given that I can't easily test 10.2 (short of hooking up a firewire drive to a spare machine),

Re: [Pythonmac-SIG] Re: Weird import problem with PythonIDE on Mac (was 'import problem')

On Apr 22, 2005, at 12:21 AM, Bob Ippolito wrote: On Apr 21, 2005, at 9:06 PM, Chris Smith wrote: ### def y1(): pass def foo(): from __main__ import y1 pass foo() ### Here is a version of the code, stripped of the timeit code. The above segment exhibits the same symptoms as the previo

Re: [Pythonmac-SIG] pyoxide 0.7.1 crashes on startup

On Apr 20, 2005, at 11:47 PM, Christopher Smith wrote: I was able to run the 0.6 version of pyoxide, but neither 0.7 nor 0.7.1 are running (for very long) for me. They start up, show me the releasenotes.rtf text for about 3 seconds and then the application quits "unexpectedly". Does anyone know

[Pythonmac-SIG] PyOXIDE wishes?

Sometime between now and WWDC, I'm planning on coming out with a major update for PyOXIDE , and was wondering what sort of functionality others have been hoping for. Right now the list is largely bug fix related: Folding improvements Better tracking of br

Re: [Pythonmac-SIG] Bob Ippolito's synopsis of Python(s) on OS X

On Jan 7, 2005, at 3:55 PM, Brendan Simons wrote: This is an old thread, (and an old topic) but my question is about the state of the "new tools" described in Bob's presentation at last year's pyCon. Scanning the archives, I see Jack and Just have talked about a PyObjC-based python ide since 2002.

Re: [Pythonmac-SIG] BuildApplet in next distro of MacPython?

On Dec 29, 2004, at 2:51 PM, Charles Hartman wrote: Please not PyOxide. I used it for a while, I like it -- but it doesn't work, and it hasn't been worked on or updated in months. The current PythonIDE is minimal and shabby, but it works just fine. Actually, it has been worked on, but there isn