please include python26_d.lib in the installer

Carl Banks pavlovevidence at gmail.com
Tue Mar 31 22:53:49 CEST 2009


On Mar 31, 12:50 pm, Compie <joh... at gmail.com> wrote:
> On 27 mrt, 17:01, Carl Banks <pavlovevide... at gmail.com> wrote:
>
> > OTOH, it's possible that SWIG and Python just happen to use the same
> > macro to indicate debugging mode.  So I think you raise a valid point
> > that this can be problematic.  Perhaps something like _Py_DEBUG should
> > be used instead.
>
> This would be a good solution IMHO. I'm not the only one facing this
> problem. The internet is full of people looking for this file...http://www.google.com/search?q=python25_d.lib+error+cannot
>
> _DEBUG is automatically defined by Visual Studio when you build the
> Debug version of a project.http://msdn.microsoft.com/en-us/library/0b98s6w8.aspx
>
> So I'm proposing: please use _PYTHON_DEBUG for this purpose. Would
> this cause any problems?

Go to bugs.python.org and file a bug report with the conflict it is
causing you.  (Well, first, make sure no one else has reported it.)  I
advise you to stress the downfalls of the current approach in a
professional, respectful manner.  You have been coming off as slightly
whiny in this thread, and that'll hurt your chances of getting such a
change approved.  In particular, don't ask for anything, or ask why it
was implemented that way; just report the issue and suggest a fix.

I suspect they used _DEBUG deliberately.  I disagree with that: a
generic symbol like _DEBUG should be avoided in general, and should
really be avoided when it entails a change in interface.


Carl Banks



More information about the Python-list mailing list