Jeremy Hylton <[EMAIL PROTECTED]> writes: > On 1/3/06, Thomas Heller <[EMAIL PROTECTED]> wrote: >> Jeremy Hylton <[EMAIL PROTECTED]> writes: >> > On 1/3/06, Thomas Heller <[EMAIL PROTECTED]> 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). >> >> > 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.) >> >> 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.
I see. I doesn't help on Windows, though, since the functions are not declared DL_EXPORT(). All in all, I'm unsure if it is worth fixing this - maybe it would be better to change py2exe. Thomas _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
