Re: Python25: wrong sys.path for pythonw2.5

2008-02-09 Thread Guido Soranzio
On Feb 9, 2008, at 9:24 AM, Bas den Hond wrote: But if I call pythonw2.5 to execute the program, the modules are not found. The problem is clearly the search path, which is somehow different for pythonw2.5. Is there a way to solve this, or should I just report a bug? MacPorts' version of

Re: Python25: wrong sys.path for pythonw2.5

2008-02-09 Thread Bas den Hond
Thanks for your explanation. This clears it up, but of course it begs the question: why does python25 not come with a pythonw2.5 command? How could I possibly use the py25-wxpython module without it? Is this a MacPort problem of does it just come with Python25? Best regards, Bas Op 9

all sorts of port failures

2008-02-09 Thread Stefan
Just did a $sudo port selfupdate, followed by a $sudo port upgrade outdated, and I have been failing tons of ports: *** ffmpeg, with: Undefined symbols: _av_crc_get_table, referenced from: _ac3_decode_frame in ac3dec.o _AC3_encode_frame in ac3enc.o _AC3_encode_frame in ac3enc.o

Re: Port Names - How to choose?

2008-02-09 Thread js
FYI, in FreeBSD ports, they are simply called libICE and libSM respectively. http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/libICE/ http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/libSM/ On Feb 10, 2008 3:27 AM, Michael Franz [EMAIL PROTECTED] wrote: Hi, I have a few ports that I would like

Re: Port Names - How to choose?

2008-02-09 Thread Michael Franz
I submitted then as xorg-libice and xorg-libsm. I guess they can be changed to be consistent, but are the existing xorg-* ports consistent? On 2/9/08, js [EMAIL PROTECTED] wrote: FYI, in FreeBSD ports, they are simply called libICE and libSM respectively.