Skip to main content

Python: Don't Mix Wing IDE and sshfs

Wing IDE Professional is awesome. sshfs is awesome. Massively large codes bases are, well, sometimes you're stuck with them.

But note, Wing IDE, sshfs, and massively large code bases don't mix; it's slooooowwwww. Use NFS instead.

By the way, the ability to run Wing IDE on my Linux laptop in order to debug a process running on a remote FreeBSD server (using stackless Python no less!) is fickin' awesome!

Comments

Anonymous said…
Did your wings IDE work with stackless python ? What's the version of Wings and stackless you were using ? I tried many combinations, stackless python always crack during debug with wings. Any trick you are using to them work together ? Thanks.
12:50 PM
jjinux said…
I was running the IDE using a normal version of Python, and I was using the debug hooks under stackless. I was using a proprietary version of stackless, so your mileage may vary. I was specifically *not* using Wing IDE on stackless threads or doing any heavy context switching under stackless.
3:15 PM
jjinux said…
I was running the IDE using a normal version of Python, and I was using the debug hooks under stackless. I was using a proprietary version of stackless, so your mileage may vary. I was specifically *not* using Wing IDE on stackless threads or doing any heavy context switching under stackless.
3:15 PM
Anonymous said…
Shannon, thanks for the info. Is
the debug hooks you mentioned replacing tasklet.__call__ as the following ? Thanks again.

def new_call(self, *args, **kwargs):
f = self.tempval
def new_f(old_f, args, kwargs):
print "wrapper.start", args, kwargs
old_f(*args, **kwargs)
print "wrapper.end"
self.tempval = new_f
tasklet.setup(self, f, args, kwargs)

tasklet.__call__ = new_call
10:48 AM
jjinux said…
The proprietary version of stackless I was using didn't have tasklets, so I guess that means no ;)

I was running this stuff on FreeBSD, so the Wing guys gave me a tarball that contained the debug hooks. It was called wingide-debugger, or something like that.
2:32 AM
Post a Comment

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe
1 comment
Read more

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo
50 comments
Read more

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p
66 comments
Read more