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
Zach has a patch to automate putting the right exports in python3.dll, which
I'm strongly in favor of, but it was rejected because people may have added
APIs that aren't meant to be stable.
Right now, you can #include a number of prototypes that aren't actually
available because there are two p
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
