Thanks Jack.
But I'm still confused about a technical question:
Does having python itself in a Framework enable anything that having it
outside a Framework won't let you do?
This is completely aside from the python in an app bundle question, as you
can certainly have a python binary with no app
I was tempted to answer this point-by-point, but I think that would lead to a
discussion that’ll quickly branch into many different ways and won’t lead to
anything.
I think you have to decide who the target audience is, and based on the needs
of the target audience decide. Possibly deciding to
Jack et al,
Yes, lots of deja vu here as well -- I suppose because this hasn't been
resolved.
> Hmm, that was a long sentence for what was intended to be the question:
“What is the problem with using a normal MacOS Framework build of Python
for Anaconda”?
I can't really answer this -- I was not
I’m having an incredible amount of deja-vu in this conversation. We seem to be
heading down the path of talking about little-documented APIs and such the same
way we were doing 15 or 18 years ago….
Christopher,
can you explain what the problem is that you’re running into? Why is there a
problem
> On 13 Mar 2020, at 20:36, Christopher Barker wrote:
>
> There is a private API that makes it possible to use GUI libraries outside of
> an app bundle and that’s used by a number of projects, but I wouldn’t want to
> use that in Python.
>
> Is that what TK is doing?
I don’t know.
>
> And
