RetroSearch Browse

Tue Jan 3 18:40:14 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-January/059379.html

On 1/3/06, Thomas Heller <theller at python.net> wrote:
> Jeremy Hylton <jeremy at alum.mit.edu> writes:
> > On 1/3/06, Thomas Heller <theller at python.net> wrote:
> >> The ast-branch merge apparently changed some formerly public functions
> >> to macros.  The two that I found out about are PyRun_SimpleString and
> >> PyRun_InteractiveLoop, I have not checked if there are more or not.
> >>
> >> This breaks apps which dynamically link at runtime to the Python dll
> >> (the latest py2exe does this).
> >>
> >> Was this change intentional, or can it be reverted?
> >>
> >> Thanks,
> >>
> >> Thomas
> >>
>
> > The intent was to provide binary compatibility, but redirect all newly
> > linked code to the newer variants.  We did this correctly for
> > PyParser_SimpleParseFile and PyParser_SimpleParseString, but didn't do
> > it for the rest of the changed functions.  Can you file a bug report?
> > (Or just fix the ones that bother you.)
> >
> > We ought to update the docs, too.
>
> I'm not sure I understand the 'we did this correctly for ...'.
> PyParser_SimpleParseFile is a function in 2.4, and a macro in 2.5.

There's a function by the same name at the end of pythonrun.c. 
Nothing in the Python core should link to it, but it's still available
for third-party code.  Now we can mark PyParser_SimpleParseFile as
deprecated remove it in some future release.

Jeremy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-January/059379.html below:

[Python-Dev] API changes