Hi,
As part of my GUI, I have lots of fields that people can fill in,
defined like this:
self.selection = Pmw.EntryField(group.interior(),
labelpos='w',
label_text='Selection to use:
',
Hi,
Please CC me in replying as I am off list.
I have an extension module that I've built using distutils. I wonder if
it's possible to use distutils to cross-compile it for windows on my
linux box, and whether the pain involved is great. Can anyone point me
in the right direction?
Hello,
(Please CC me in replies, as I am off-list)
I'm building an application (a game) in python, with a single C module
containing some performance-critical code. I'm trying to figure out the
best way to set it up to build. Distutils seems to be designed only for
building and
Gerhard Häring wrote:
Michael George wrote:
I've tried using automake,
In my opinion, this is serious overkill. automake is good for making
stuff work on a herd of different Unixen with various combinations of
libc functions available etc. But for developing a Python extension,
it doesn't
Martin v. Löwis wrote:
I've tried using automake, however I'm worried about libtool not getting
the options right while building my module.
You should use python-config(1) to obtain the command line options
necessary to build and link extension modules.
HTH,
Martin
Sweet, I think
On Nov 11, 3:25 pm, Rob Wolfe [EMAIL PROTECTED] wrote:
Hi Rob,
Michael GeorgeLerner[EMAIL PROTECTED] writes:
Hi,
(Python 2.5, OS X 10.4.10)
I have a program called pdb2pqr on my system. It is installed so that
pdb2pqr is in my path and looks like:
#\!/bin/zsh -f
Are you sure that
Hi,
(Python 2.5, OS X 10.4.10)
I have a program called pdb2pqr on my system. It is installed so that
pdb2pqr is in my path and looks like:
#\!/bin/zsh -f
/sw/share/pdb2pqr/pdb2pqr.py $@
When I call it via this script:
#!/usr/bin/env python
import subprocess
import tempfile
args =
particularly
tempting. I'm using BoaConstructor for the GUI stuff at the moment.
It has a bit of a learning curve, but it looks nice so far.
-michael
Michael George Lerner wrote:
Aahz [EMAIL PROTECTED] wrote:
Use vim. 80% of the power of emacs at 20% of the learning curve.
A system
Aahz [EMAIL PROTECTED] wrote:
Use vim. 80% of the power of emacs at 20% of the learning curve.
A system administrator said this to me about unix a long time ago,
but it applies equally well to emacs:
Emacs is a great place to live, but I'd hate to visit.
-michael, an (x)emacs user
--
