Logged In: YES
user_id=71407
> IOW I think that the correct solution would be a change to
> Boost. But I'm open to persuasion.
In principle I agree with you, but here are a few arguments
to
justify the easy fix:
- The old Boost.Python metaclass system is a dead branch.
We would prefer to concentrate our time on the ongoing
rewrite of Boost.Python which will be fully based on
the new Python 2.2 type system.
- A significant number of people are using released versions
of Boost(.Python). If the easy fix is integrated in
Python 2.2.1,
they could continue to use what they have.
- Other people might be affected by your change. The
suggested solution
will restore backward-compatibility with more people's
existing code.
- This is more a question: can you envision that the
suggested
fix has negative side-effects?
Thanks,
Ralf