Stefan,
OK--it's in the system as #3183. Thanks again for your help, and anyone
should feel free to let me know if they need more information about this
issue.
--Chris
- Original Message -
From: Stefan Seefeld
To: Development of Python/C++ integration
Sent: Monday, June 15, 2009 3
On 06/11/2009 08:13 PM, Christopher A Mejia wrote:
Stefan / cplusplus-sig,
Based on Stefan's encouragement, I developed a minimal complete test case
Thanks ! Can you please submit that as an issue on
https://svn.boost.org/trac/boost/ ? We may then follow-up there...
Stefan
--
Hello,
I am facing an error when trying to build boost.python. I hope I am in
the right place to address this issue. If not please redirect me ...
So first I ran bootstrap.sh in my boost root dir pro:boost_1_39_0, and
that is the output:
-n Building Boost.Jam with toolset darwin...
tools
Hi Simon,
Did you export your class ResourceManager to python? If this class not
is copyable you can export with some like that:
class_("ClassName")
BR
Renato
On Mon, Jun 15, 2009 at 5:05 PM, Simon Pickles wrote:
> Hi,
>
> I have a c++ class which uses boost::thread and boost::mutex.
>
> I ca
If you send me a patch (against the boost trunk) I'll test it and check it in.
Probably, the file to be changed is
boost/libs/python/src/converter/builtin_converters.cpp
I'd try working with
boost/numeric/conversion/cast.hpp
Ralf
- Original Message
From: Anderson Lizardo
To: cplu
Hi,
I have a c++ class which uses boost::thread and boost::mutex.
I cannot expose this class directly with boost::python, since mutex is
non-copyable.
so I did this:
/// C++
class ResourceManager
{};
ResourceManager* ResourceManagerFactory()
{
return new Reso
Hi,
I noticed that boost.python silently accepts negative (or too long)
integers for constructor/methods that have "unsigned int" parameters.
(signed) "int" arguments seem to be handled just fine. Is it possible
to tell boost.python to check for overflow and raise an exception just
like it happens
