On Thu, Jan 14, 2021 at 3:14 PM Jack Jansen wrote:
> For example, the brew Python is installed into a framework tucked away
> deep in /usr/local/Cellar but you don’t notice this at all: you can just
> use “python foo.py” and the moment the script does GUI calls it’ll get an
> icon in the doc and
I’m not sure there is a point anymore?
For example, the brew Python is installed into a framework tucked away deep in
/usr/local/Cellar but you don’t notice this at all: you can just use “python
foo.py” and the moment the script does GUI calls it’ll get an icon in the doc
and all that.
What pr
Ned suggested I bring this conversation over here from python-dev, so here
it is.
What I'd like to see done is have the "pythonw" wrapper buildable in an
otherwise non-framework build.
I *think* there are no real technical show stoppers, but it would take some
auto-conf magic, which I am fully un
