RE: [C++-sig] Boost.Python v2: A few small changes
By the way, I've been pondering the merits of having a <boost/python.hpp> header which exposes all of the public headers, just for ease-of-use. Opinions?
Not really bothered either way. However, on a related issue, I'd definitely like to see <boost/python/detail/wrap_python.hpp> moved up out of detail. It's useful in its own right if you're embedding and neither including a "detail/" header directly nor including an arbitrary public header to get at it are very elegant. best, Greg -----Original Message----- From: David Abrahams [mailto:dave@boost-consulting.com] Sent: 01 October 2002 14:09 To: pysig Subject: [C++-sig] Boost.Python v2: A few small changes [...]
However, on a related issue, I'd definitely like to see <boost/python/detail/wrap_python.hpp> moved up out of detail. It's useful in its own right if you're embedding and neither including a "detail/"
From: "Greg Hawkins" <Greg.Hawkins@softwire.co.uk> header directly nor including an arbitrary public header to get at it are very elegant. Well, embedding isn't really well-supported for 1.29.0. The problem is that there are global objects keeping some Python objects alive, and those Python objects need to be released before the interpreter is finalized (preferably using Python's atexit module) or the application will crash on exit. When we finally get that going, I'm happy to consider changes which are specifically for embedding support. ----------------------------------------------------------- David Abrahams * Boost Consulting dave@boost-consulting.com * http://www.boost-consulting.com
participants (2)
-
David Abrahams -
Greg Hawkins