On 19 Sep, 2007, at 19:23, Ian Bicking wrote:
> Ronald Oussoren wrote:
>> On Wednesday, September 19, 2007, at 07:26AM, "Ian Bicking" <[EMAIL
>> PROTECTED]
>> > wrote:
It is in the python.org source tree: Modules/getpath.c
>>> That's the file used in the Framework build of Python? I only
Ronald Oussoren wrote:
>
> On Wednesday, September 19, 2007, at 07:26AM, "Ian Bicking" <[EMAIL
> PROTECTED]> wrote:
>
>>> It is in the python.org source tree: Modules/getpath.c
>> That's the file used in the Framework build of Python? I only see some
>> small references to __APPLE__, none of
On Wednesday, September 19, 2007, at 07:26AM, "Ian Bicking" <[EMAIL PROTECTED]>
wrote:
>>
>> It is in the python.org source tree: Modules/getpath.c
>
>That's the file used in the Framework build of Python? I only see some
>small references to __APPLE__, none of which seem related to Framewor
Ronald Oussoren wrote:
>
> On 19 Sep, 2007, at 6:25, Ian Bicking wrote:
>
>> Ronald Oussoren wrote:
>>> On 16 Sep, 2007, at 21:55, Ian Bicking wrote:
Ronald Oussoren wrote:
> On 16 Sep, 2007, at 21:44, Ian Bicking wrote:
>> Ronald Oussoren wrote:
>>> On 15 Sep, 2007, at 18:09, Ia
On 19 Sep, 2007, at 6:25, Ian Bicking wrote:
> Ronald Oussoren wrote:
>> On 16 Sep, 2007, at 21:55, Ian Bicking wrote:
>>> Ronald Oussoren wrote:
On 16 Sep, 2007, at 21:44, Ian Bicking wrote:
> Ronald Oussoren wrote:
>> On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
>>> Hi all. I
Ronald Oussoren wrote:
> On 16 Sep, 2007, at 21:55, Ian Bicking wrote:
>> Ronald Oussoren wrote:
>>> On 16 Sep, 2007, at 21:44, Ian Bicking wrote:
Ronald Oussoren wrote:
> On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
>> Hi all. I'm kind of giving up on workingenv, and have started
>
On 16 Sep, 2007, at 21:55, Ian Bicking wrote:
> Ronald Oussoren wrote:
>> On 16 Sep, 2007, at 21:44, Ian Bicking wrote:
>>> Ronald Oussoren wrote:
On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
> Hi all. I'm kind of giving up on workingenv, and have started
> working
> from vir
On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
> Hi all. I'm kind of giving up on workingenv, and have started working
> from virtual-python as a basis instead
> (http://pypi.python.org/pypi/virtualenv/).
>
> So the basic technique here is to copy the executable into
> /ENV/bin/python, and then s
Ronald Oussoren wrote:
>
> On 16 Sep, 2007, at 21:44, Ian Bicking wrote:
>
>> Ronald Oussoren wrote:
>>> On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
Hi all. I'm kind of giving up on workingenv, and have started working
from virtual-python as a basis instead
(http://pypi.python.o
On 16 Sep, 2007, at 21:44, Ian Bicking wrote:
> Ronald Oussoren wrote:
>> On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
>>> Hi all. I'm kind of giving up on workingenv, and have started
>>> working
>>> from virtual-python as a basis instead
>>> (http://pypi.python.org/pypi/virtualenv/).
>>>
>>
Ronald Oussoren wrote:
>
> On 15 Sep, 2007, at 18:09, Ian Bicking wrote:
>
>> Hi all. I'm kind of giving up on workingenv, and have started working
>> from virtual-python as a basis instead
>> (http://pypi.python.org/pypi/virtualenv/).
>>
>> So the basic technique here is to copy the executable
Andreas Jung wrote:
>
>
> --On 15. September 2007 11:09:44 -0500 Ian Bicking <[EMAIL PROTECTED]>
> wrote:
>
>> Hi all. I'm kind of giving up on workingenv, and have started working
>> from virtual-python as a basis instead
>> (http://pypi.python.org/pypi/virtualenv/).
>>
>
> I tried virtualen
--On 15. September 2007 11:09:44 -0500 Ian Bicking <[EMAIL PROTECTED]>
wrote:
Hi all. I'm kind of giving up on workingenv, and have started working
from virtual-python as a basis instead
(http://pypi.python.org/pypi/virtualenv/).
I tried virtualenv - however the python in the new environ
FWIW, the same thing seems to happen for me on Tiger using the
original virtual-python.py against the Apple-compiled Python that
ships with it:
[EMAIL PROTECTED] macsandbox]$ /usr/bin/python ~/bin/virtual-python.py
--prefix=.Creating ./lib/python2.3
Creating ./lib/python2.3/site-packages
Cre
On 15 Sep 2007, at 18:09 , Ian Bicking wrote:
> Hi all. I'm kind of giving up on workingenv, and have started
> working from virtual-python as a basis instead (http://
> pypi.python.org/pypi/virtualenv/).
>
> So the basic technique here is to copy the executable into /ENV/bin/
> python, and th
Hi all. I'm kind of giving up on workingenv, and have started working
from virtual-python as a basis instead
(http://pypi.python.org/pypi/virtualenv/).
So the basic technique here is to copy the executable into
/ENV/bin/python, and then sys.prefix will be '/ENV'. The standard
Python installe
16 matches
Mail list logo