[boost] Organization of Python conversions [was: void * with boost::python]

From: Hubert Holin (Hubert.Holin_at_[hidden])
Date: 2005-02-11 10:09:58

Somewhere in the E.U., le 11/02/2005

   Bonjour

In article <uy8ekakyq.fsf_at_[hidden]>,
 David Abrahams <dave_at_[hidden]> wrote:

> Preston,
> 
> The best place for Boost.Python questions is the C++-sig:
> http://www.boost.org/more/mailing_lists.htm#cplussig
> 
> "Preston A. Elder" <prez_at_[hidden]> writes:

[SNIP]

> > Also, on another note, is there somewhere that has all of boost
> > already pythonized?  
> 
> No.
> 
> > I manually converted boost::date_time (at least all the gregorian
> > and posix_time stuff) myself, however I would have expected most of
> > boost to have been converted to python already ;)
> 
> It seems unlikely to me.  Because so much of Boost is heavily
> templated generic code, a great deal of it would make no sense as
> Python wrappers.  Can you imagine Pythonizing the Boost.Python
> library?  ;-)

      As an organizational note, what would be best, when we add more 
conversions to Python? Various pieces bundled with the lib's doc, or in 
a centralized location TBD?

         Hubert Holin