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:
> So it is working. No, really: BBEdit ran the env tool, but the env tool did
> not find python3. You could try python2.7 instead, or python3.2, but I'd
> rather get python3 working correctly.
>
> What does "which python3" in the terminal say? The python3 command is a
> generic description of, well, python3, without tying you directly to python
> 3.2.3 or even 3.2.x
--
Chip
--
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
---
You received this message because you are subscribed to the Google Groups
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bbedit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
