This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients christian.heimes, dmalcolm, doko, lemburg, loewis, pitrou
Date 2012-11-27.19:36:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354044997.1.0.827027333569.issue4555@psf.upfronthosting.co.za>
In-reply-to
Content
I'd like to focus this issue; it has been open long enough, and deserves to get closed once the original issue is resolved - which was that "make smelly" reports symbols. I think dmalcolm's patch is quite a good start for that.

It may well be that other modules need to be considered - but PLEASE not in this issue. For Unix with shared libraries, the extension modules certainly cause problems, in particular if Python gets embedded in a context (e.g. Apache) that also loads separate copies of the same libraries, and may cause problems if one of our functions collide with some library. However, I see *two* issues falling out of this: one to extend the "make smelly" target to include extension modules, and the other to then fix the extension modules - preferably with one issue per extension module.
History
Date User Action Args
2012-11-27 19:36:37loewissetrecipients: + loewis, lemburg, doko, pitrou, christian.heimes, dmalcolm
2012-11-27 19:36:37loewissetmessageid: <1354044997.1.0.827027333569.issue4555@psf.upfronthosting.co.za>
2012-11-27 19:36:37loewislinkissue4555 messages
2012-11-27 19:36:36loewiscreate