On Wednesday, June 14, 2006, at 05:18PM, Bob Ippolito <[EMAIL PROTECTED]> wrote:
>python itself needs to be in a directory containing a colon.
>
>bump:~/src/python/:colon bob$ ./python.exe -c "import sys; print
>sys.path"
>'import site' failed; use -v for traceback
>['', '/usr/local/lib/python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a new twist on an old problem.
I'm trying to build a standard Unix version of Python (without
- -enable-framework) and link it against an X11-based version of Tcl/Tk.
However, no matter what I do, it builds against the system-installed
Tk/Aqua
On Jun 16, 2006, at 9:40 AM, Kevin Walzer wrote:
> This is a new twist on an old problem.
>
> I'm trying to build a standard Unix version of Python (without
> - -enable-framework) and link it against an X11-based version of
> Tcl/Tk.
> However, no matter what I do, it builds against the system-
On 15-jun-2006, at 23:21, Bob Ippolito wrote:
>
> On Jun 15, 2006, at 2:12 PM, Bob Ippolito wrote:
>
>> FWIW, this isn't at all Mac OS X specific..
>>
>> $ uname -rs && pwd && ./python -c "import sys; print sys.path"
>> FreeBSD 6.0-RELEASE
>> /usr/home/bob/src/python/:colon
>> 'import site' faile
On Jun 16, 2006, at 12:21 AM, Ronald Oussoren wrote:
>
> On 15-jun-2006, at 23:21, Bob Ippolito wrote:
>
>>
>> On Jun 15, 2006, at 2:12 PM, Bob Ippolito wrote:
>>
>>> FWIW, this isn't at all Mac OS X specific..
>>>
>>> $ uname -rs && pwd && ./python -c "import sys; print sys.path"
>>> FreeBSD 6.0
