On 19 feb. 2013, at 02:22, Chip G. wrote:
> Which is pretty much what I managed to determine. The path I get with "which
> python3.2" is /sw/bin/python3.2 and I put that after a #! and it works.
>
> But what's the best way to get which python3 to work and not break when the
> software is upgr
There was no result, just blankness.
On Feb 11, 2013, at 17:37, Lee Hinde wrote:
> try this in terminal:
>
> which python3
>
> then use the resulting path as above.
--
Chip
--
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Grou
Which is pretty much what I managed to determine. The path I get with "which
python3.2" is /sw/bin/python3.2 and I put that after a #! and it works.
But what's the best way to get which python3 to work and not break when the
software is upgraded?
On Feb 11, 2013, at 17:42, Maarten Sneep wrote:
This is a great little gem. I have fiddled with unix for awhile, but there are
still holes in my knowledge. This showed me a new scenario where I had multiple
versions of an important system component and had to use direct paths to access
it. This will take some getting used to.
Thanks for the
On 2013-02-11 at 2:31 PM, n1mie.c...@gmail.com (Chip G.) wrote:
OK, a variation on this worked. When I changed it to a
legitimate path on my system it worked.
#!/sw/bin/python3.2
Now that's working. But since the examples I had from the
author didn't include those, I wonder why I can't get i
On Feb 11, 2013, at 4:31 PM, Chip G. wrote:
> On Feb 11, 2013, at 16:12, Maarten Sneep wrote:
>
>> As a last resort, you could use the full path to python:
>>
>> #!/usr/local/bin/python3
>
> OK, a variation on this worked. When I changed it to a legitimate path on my
> system it worked.
>
>
On Feb 11, 2013, at 16:12, Maarten Sneep wrote:
> As a last resort, you could use the full path to python:
>
> #!/usr/local/bin/python3
OK, a variation on this worked. When I changed it to a legitimate path on my
system it worked.
#!/sw/bin/python3.2
Now that's working. But since the examples
On 11 feb. 2013, at 23:13, "Chip G." wrote:
> On Feb 11, 2013, at 16:12, Maarten Sneep wrote:
>
>> On 11 feb. 2013, at 21:25, "Chip G." wrote:
>>
>>> I'm trying to learn Python. I have a book that is helping me along. I'd
>>> like to use BBEdit as my editor, but I'm having some issues. Part
On Feb 11, 2013, at 2:13 PM, "Chip G." wrote:
> On Feb 11, 2013, at 16:12, Maarten Sneep wrote:
>
>> On 11 feb. 2013, at 21:25, "Chip G." wrote:
>>
>>> I'm trying to learn Python. I have a book that is helping me along. I'd
>>> like to use BBEdit as my editor, but I'm having some issues. Par
On Feb 11, 2013, at 16:12, Maarten Sneep wrote:
> On 11 feb. 2013, at 21:25, "Chip G." wrote:
>
>> I'm trying to learn Python. I have a book that is helping me along. I'd like
>> to use BBEdit as my editor, but I'm having some issues. Part of this is an
>> Apple/Fink thing. Part of the problem
On 11 feb. 2013, at 21:25, "Chip G." wrote:
> I'm trying to learn Python. I have a book that is helping me along. I'd like
> to use BBEdit as my editor, but I'm having some issues. Part of this is an
> Apple/Fink thing. Part of the problem is that the version of python get if I
> run using 'p
I'm trying to learn Python. I have a book that is helping me along. I'd like to
use BBEdit as my editor, but I'm having some issues. Part of this is an
Apple/Fink thing. Part of the problem is that the version of python get if I
run using 'python' is old (v2.7.1). If I force paths I can get v2.7
12 matches
Mail list logo
