On 6/5/19 at 5:35 PM, [email protected] (Jon Crump) wrote:

Thanks for the quick response Rich. Yes, setting that boolean
RunUsingPython3 "fixed" the problem. But now I can't get bbedit to use my
python 3 installation if I put it in the shebang line.

When running Perl, Python, or Ruby scripts, BBEdit does not use or interpret the #! line. This decision goes back a long way in time, I think to 11.0 but possibly before. (The issue this solves is that everyone who's trying to learn Python uses the same tutorial pattern which involves "#!/usr/bin/env python" or something similar, then they install Python3 and wonder why BBEdit doesn't use that.)

It's clear that where bbedit once respected the shebang line, now it
does not. It seems like poor practice to teach your software to ignore
explicit instructions right in the script it's supposed to run. Yes
it's true that using "Run in Terminal" will respect shebang, but:

1. I liked getting a log file right there in bbedit;
2. this isn't the behavior I'm accustomed to; and
3. it's inconvenient.

I get this, and I'm sorry about it. But unfortunately we have to deal with an enormous variety of use cases, and so the best we can do is make the behavior adjustable when possible.

This does not seem like an improvement to me. It seems like a bug. Is there
really no way to instruct bbedit which python installation to use without
setting and resetting system-wide preferences from the command line?

If you'll forgive the nit: the expert preference is application-specific, and does not affect the system behavior.

That being said, there are numerous Python-specific ways to control which Python installation and/or version gets used without involving BBEdit at all; they're global and will affect all Python execution.

If you have a use case that involves a need to frequently switch between different versions of Python, please write to <[email protected]> and describe your needs in detail, and we'll see what we can do.

Anything that doesn't involve trying to read your mind at the moment you press Command-R may be possible, but I can't make any promises right now.

R.
--
Rich Siegel                                 Bare Bones Software, Inc.
<[email protected]>                      <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they sedate me.

--
This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <https://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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/bbedit.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/r480Ps-10145i-CD00D0182C0844FCB520FB6ABC7A8D43%40Stormwind.local.

Reply via email to