[C++-sig] multiply defined to_python_converter

David Abrahams dave at boost-consulting.com
Wed Dec 11 02:38:06 CET 2002

"Langston, Matthew David" <langston at SLAC.Stanford.EDU> writes:

> I just ran into a problem where my Boost.Python module is conflicting
> with a third-party library's Boost.Python module. I get a run-time
> error when I import both modules into python because they both provide
> a to_python_converter that converts a std::vector<std::string> to a
> python tuple of strings.
> The methods are named differently at the source-level (i.e. both
> modules gave their to_python_converter a unique name), so it appears
> to be a "run-time type matching" problem.
> How do I work around this problem of "multiply defined
> to_python_converter"?

Hmm.  I'm not sure what the best answer is.  Does Python have a
warning mechanism?  Maybe it would be best to maks such multiple
definitions trigger a Python warning instead of a hard error.


                       David Abrahams
   dave at boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution

More information about the Cplusplus-sig mailing list