Scot,
Good of you to take a shot at this. Sorry I didn't notice your
response until recently. I provide below the response from the BBedit
support folks in case anybody else has ever been bothered by this.
The specific problem, it appears, is caused by a runtime condition in
bbedit that they haven't tracked down, but there is this work-around:
Python knows about a special script named "sitecustomize.py"
If you put the following text in sitecustomize.py
import sys
sys.setdefaultencoding('utf-8')
and move this file into
/Path/To/Python/Installation/site-packages/
Then when bbedit spawns a python process, the python 'site' module
automatically calls sys.setdefaultencoding() and then after having set
the default encoding for the session (and this is the weird bit)
removes setdefaultencoding from the sys namespace. See:
http://docs.python.org/library/sys.html#sys.setdefaultencoding
On May 28, 8:42 am, SCatlin <scot.cat...@windsorcircle.com> wrote:
> Jon,
>
> If it's related to environment variables, it might be that the shell
> that BBEdit spawns is different. I had some similar troubles and
> figured out that BBEdit spawns a bash shell when running python
> scripts. If you place the environment variables that you want to have
> set in /etc/bashrc, it should work for you.
>
> -Scot
--
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>
