On 29 May 2015 01:04, "Steve Dower" wrote:
>
> Paul Moore wrote:
> > On 28 May 2015 at 15:28, Steve Dower wrote:
> >> I don't have the issue number handy, but it should be near the top of
> >> the recently modified list.
> >
> > I recall seeing that issue. I'm fine with that - getting the two in
ev<mailto:python-dev@python.org>
Subject: [Python-Dev] Usability of the limited API
With Python 3.5 shipping an embeddable copy of the interpreter on
Windows, I thought I'd try out a simple embedded interpreter as an
experiment. I wanted to use the limited API, as I'd rather it were
easy
Paul Moore wrote:
> On 28 May 2015 at 15:28, Steve Dower wrote:
>> I don't have the issue number handy, but it should be near the top of
>> the recently modified list.
>
> I recall seeing that issue. I'm fine with that - getting the two in sync is
> obviously worth doing (and clearly in hand). I'
On 28 May 2015 at 15:28, Steve Dower wrote:
> I don't have the issue number handy, but it should be near the top of the
> recently modified list.
I recall seeing that issue. I'm fine with that - getting the two in
sync is obviously worth doing (and clearly in hand). I'm personally
not sure whethe
On 29 May 2015 at 00:11, Paul Moore wrote:
> I was hoping to be able to suggest as an application bundling option
> that people could write a trivial wrapper script in C to fire up a
> Python script, and bundle that along with its dependencies and the
> embeddable Python distribution. Looks like t
With Python 3.5 shipping an embeddable copy of the interpreter on
Windows, I thought I'd try out a simple embedded interpreter as an
experiment. I wanted to use the limited API, as I'd rather it were
easy to upgrade the interpreter without recompiling the embedding app.
But the "Very high-level em
