At Wed, 27 Jan 2010 12:17:07 +0100,
Nicolas Lelong wrote:
>
> My thought was to leave the library files as-is, and to simply enable
> the unit tests on 'toolsets' related to Microsoft compilers, and perhaps
> add later other compilers that might support these calling conventions,
> based on use
At Mon, 25 Jan 2010 10:47:06 +0100,
Nicolas Lelong wrote:
>
> Thanks Dave,
>
> not quite sure of it, but it looks like you added the unit tests to
> the Jamfile, but you did not add the tests source code to the svn,
> did I miss something.
Gah, I hate SVN.
> Also, the tests i submitted do not c
At Fri, 15 Jan 2010 18:09:36 +0100,
Nicolas Lelong wrote:
>
> My previous mail once again got lost, gotta be more careful...
>
> > Changes (by dave):
> >
> > This looks terrific! I'll try to get it applied ASAP. Please poke me if
> > you don't see it in trunk by the end of the week.
>
> Th
on Sat Sep 19 2009, Stefan Seefeld wrote:
> Hi there,
>
> as some of you may know, Haoyu Bai has worked over the summer on Python 3
> support for
> Boost.Python. This work happened on a branch, which I merged back into trunk
> last
> night.
Whoo hoo!
> Now we need to set up testers to run th
It's fine as far as I'm concerned. On vacation right now so can't
give it more attention.
Sent from my iPhone
On Aug 21, 2009, at 4:54 AM, Stefan Seefeld
wrote:
Anderson,
let me forward that mail to the main boost list, and ping Beman
(release manager) and David (boost.python maintai
on Wed Apr 08 2009, David Abrahams wrote:
> I think you raised a number of irrelevant issues whose relevance I can't
> see, but I agree with the substance of your argument.
And I raised a number of redundant issues that were redundant with one
another... sorry, I didn't mea
on Thu Mar 19 2009, "Niall Douglas" wrote:
> On 19 Mar 2009 at 21:53, Haoyu Bai wrote:
>
>> I'm felling the difference between char*, unsinged char* and the
>> constant version and std::vector version of them would be a bit
>> complicated and confusing. We may document it clearly, but things are
on Wed Mar 18 2009, "Niall Douglas" wrote:
> On 18 Mar 2009 at 2:07, Haoyu Bai wrote:
>
>> According to the current behavior of Boost.Python converters, the
>> wrapped function in Python 3 will return a b"Hello" (which is a bytes
>> object but not a string). So code like this will broken:
>>
>>
on Wed Apr 01 2009, Haoyu Bai wrote:
> Hi,
>
> I did some preliminary work on BPL py3k support in these days.
>
> With Troy's help we have a py3k SVN tree in sandbox now, which is
> branched from trunk. I also tried to compile BPL with Python 3, and by
> following the error report of the compile
on Wed Mar 18 2009, "troy d. straszheim" wrote:
> The current rule for overload resolution are simply 'first match in reverse
> order of
> registration'. You could relatively easily make this 'first match in forward
> order of
> registration'. The library currently has no notion of one func
#x27;t do the trick.
Well, that's news to me. If that's the case, I'd say it's a
Boost.Build bug that you should take up on the boost-build list.
--
David Abrahams
BoostPro Computing
http://boostpro.com
___
Cplusplus-sig
On Mar 14, 2009, at 4:28 AM, Niall Douglas wrote:
On 13 Mar 2009 at 12:10, David Abrahams wrote:
On Mar 13, 2009, at 11:19 AM, Stefan Seefeld
wrote:
I'm willing to participate, in particular, if other folks such as
David, I notice you already indicated support. Could we team up for
Sent from my iPhone
On Mar 13, 2009, at 11:19 AM, Stefan Seefeld
wrote:
I'm willing to participate, in particular, if other folks such as
David, I notice you already indicated support. Could we team up for
this ?
Sure, I'd be glad to
___
on Thu Mar 12 2009, ZaeX wrote:
> I just built the boost.python 1.36 with Python2.6.1 and tried again, and it
> still turned out to be 0x in debug build.
Have you read
http://www.boost.org/doc/libs/1_38_0/libs/python/doc/building.html#python-debugging-builds
?
--
Dave Abrahams
BoostPr
on Wed Mar 11 2009, Haoyu Bai wrote:
> Hi,
>
> I have posted this to Boost development mailling list before and many
> people suggested me to repost here, so I did.
>
> I'm a student who has finished SWIG's Python 3.0 support in GSoC 2008.
> I'd like to contribute my knowledge of Python 3 migrat
on Thu Mar 12 2009, athor wrote:
> * You don't *need* a const& to break cyclic reference. Passing a shared_ptr
> by value works too.
And that's almost always a better idea. If you *do* have a reference
cycle, consider weak_ptr instead.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.
on Thu Feb 19 2009, "Martin Walser" wrote:
> Hi! :)
>
>
> I'm on the best way to become completely insane.
>
> I'm trying to set up VS2005 to run Boost Python in debug mode.
>
> Sorry for the long text...
>
>
> Problem summary:
>
> - applications crash in debug mode
> - dependencies to python25_
on Tue Feb 10 2009, Gennadiy Rozental wrote:
> Hi,
>
> I need to implement some translation in a getter and setter for particular
> field.
>
> I am getting compile time errors, I am not sure how to fix. I am using 1.33.1.
>
> Here is what I do:
>
> template
> struct Getter {
> explicit Get
on Tue Feb 10 2009, Hugo Lima wrote:
> David, any comments about the patch?
Please attach the patch to a Trac ticket and I'll have a look.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
___
Cplusplus-sig mailing list
Cplusplus-sig@pytho
on Mon Feb 02 2009, yamini sardana wrote:
> Hi,
>
> How do we pass a pointer to a c++ function from python.
>
> I have to call the below mentioned function from python
>
> long afSigGenDll_Manual_LevelMax_Get(afSigGenInstance_t sigGenId, double*
> pLevelMax);
>
> When i am calling the function w
on Sun Feb 01 2009, Eric Jonas wrote:
> I am trying to return a shared pointer to a class Foo and then
> test the results in python for equality, but they always seem to fail.
> I've created the following two trivial classes:
>
> class Foo : public boost::noncopyable
> {
> };
>
> typedef boos
on Wed Feb 04 2009, Paul Melis wrote:
> Hello,
>
> Classes with protected destructors (as found when custom reference
> counting is used) seem to cause some trouble when using bp::wrapper<>
> containing a method that takes a const reference to a refcounted class.
>
> struct CallbackWrap : Call
l try to copy it. You declared
BaseCmp to be noncopyable, so no converter was registered that would
copy a BaseCmp object into a new Python object.
> David Abrahams a écrit :
>> on Wed Jan 28 2009, William Marié wrote:
>>
>>
>>> I need to call my testVirtualPure fu
on Wed Jan 28 2009, Cameron Royal wrote:
> David Abrahams-3 wrote:
>>
>> Have you tried the build and test with Boost.Build/bjam as instructed in
>> the tutorial?
>>
>
> I had hoped the precompiled binaries would be fine, but it seems not. After
> buildin
on Wed Jan 28 2009, William Marié wrote:
> I need to call my testVirtualPure function from C++ side :
> BaseCmp* bc = BaseCmp();
> Base* b = Base();
> b->testVirtualPure( bc );
>
> But this causes an error :
> TypeError: No to_python (by-value) converter found for C++ type: class
> BaseCmp
Th
on Tue Jan 27 2009, ZaeX wrote:
> Thanks, Roman. It solved the problem.
> Can't believe this '&' takes me two days.
Using T const& as a parameter would've worked too. The thing to remember
with Boost.Python is that a T& parameter has a very special meaning:
there has to be a T hanging around i
on Tue Jan 27 2009, Cameron Royal wrote:
> So I'm having some difficulty getting one of the boost.python tutorial
> examples working. In particular the class with a string constuctor.
>
> http://www.boost.org/doc/libs/1_37_0/libs/python/doc/tutorial/doc/html/python/exposing.html#python.construct
on Fri Jan 23 2009, Renato Araujo wrote:
> I'm current using "CXXFLAGS=-ffunction-sections -Os" and "LDFLAGS
> --gc-sections", and the library already striped, without strip the
> size is about 12MB.
There's a lot more you can do. -fomit-frame-pointer,
-finline-functions, ...man gcc, man
Ther
on Fri Jan 23 2009, Renato Araujo wrote:
> hi all,
> After some vacation I got back to my library binding. Most problems
> have been solved
> but now I got another big problem here. My current binding library is very
> huge
> compared to the wrapped C++ library (about four times). Checking the
on Tue Jan 20 2009, Ricardo Abreu wrote:
> Thank you very much for your answer, but what I really wanted was to expose
> to Python
> just the first element of the pair and not the whole pair, so that the fact
> that it is
> a pair in c++ would be transparent to python.
Looks like you want to
on Sat Jan 17 2009, "Sebastian Walter"
wrote:
> Hello,
>
> I want to call a Python function from C++ with an object of a C++ class
> as argument.
> The Python-function should change the argument, so changes are visible
> on the C++ side.
> Boost::Python automatically makes a copy of all the arg
on Thu Jan 15 2009, Ricardo Abreu wrote:
> Hello,
>
> How do I extract elements from a tuple that I receive from python?
> boost::python::tuple doesn't seem to have anything for that in its
> interface...
t[n]
is the nth element of tuple t.
--
Dave Abrahams
BoostPro Computing
http://www.b
on Thu Jan 08 2009, "Del Robins" wrote:
> Sorry, the problem is being able to find classes/types wrapped and
> exported from module A that are used as a parameter/argument type to a
> function in module B. It all works fine when they are in the same
> module.
>
> You may have hit the nail on th
on Thu Jan 08 2009, "Del Robins" wrote:
> Hi all,
>
>
>
> I am new to Python and just recently started using boost python to
> create some wrappers for some C++ static libraries. I have been able
> to get most everything to work from the documentation and community
> examples. Thank you for
on Wed Jan 07 2009, Neal Becker wrote:
> This would require filling in tp_as_buffer field in the PyTypeObject
> structure for the
> class. Is this possible? Any clue how/where this could be done?
I honestly don't know the answers to these questions, sorry.
--
Dave Abrahams
BoostPro Computi
on Mon Dec 22 2008, "Ralf W. Grosse-Kunstleve" wrote:
> Thanks for the patches! They are now in the boost trunk:
>
>
> r50368 | rwgk | 2008-12-22 23:55:33 -0800 (Mon, 22 Dec 2008) | 4 lines
>
> Boost.Python enable_shared_fr
on Thu Dec 18 2008, "lin yun" wrote:
> Would you please elaborate your idea a little more?
>
>
> On Thu, Dec 18, 2008 at 10:18 AM, David Abrahams wrote:
>
>>
>> on Wed Dec 17 2008, "lin yun" wrote:
>>
>> >> Yes. I believe Py++ d
on Wed Dec 17 2008, "Hugo Lima" wrote:
> Hi;
>
> I need wrap enums with duplicated values, but boost::python do not
> support it. At the boost website you can find the quote:
>
> "Scott Snyder provided a patch; Dave was dissatisfied for some reason,
I think I didn't really like the asymmetry of
on Wed Dec 17 2008, "lin yun" wrote:
>> Yes. I believe Py++ deals with boost::shared_ptr without invoking the
>> user. Just use default call policy.
> That's good news! How about vector> ?
If you use the facilities of
http://www.boost.org/doc/libs/1_37_0/libs/python/doc/v2/iterator.html,
everyt
on Wed Dec 17 2008, "Roman Yakovenko" wrote:
> 2008/12/18 lin yun :
>> Hi, folks:
>>
>> I am trying to wrap a c++ function that returns a boost::shared_ptr> class> type using boost.python, is that possible?
>
> Yes. I believe Py++ deals with boost::shared_ptr without invoking the
> user. Just us
on Thu Nov 20 2008, fileoffset wrote:
> To best explain my problem, here is some code:
>
> struct A
> {
> A()
> {
> mTest = 1;
>
> std::cout << "Test: " << mTest;
>
> Py_Initialize();
> object main_module = import("__main__");
>
on Fri Dec 12 2008, "Renato Araujo" wrote:
> Hi guys,
>
> I'm creating a 2 new call_policy to my functions where I need take and
> give back the ownership of my object. I would like reproduce this in
> my precall or postcall function policy functions.
>
> http://www.boost.org/doc/libs/1_36_0/lib
on Fri Dec 12 2008, "Rocketman-AT-JSC" wrote:
> Yes it's probably user error--but I have no clue why this is happening. I
> did not do the build and the guy doing the build is not an expert boost user
> either.
Did he use bjam?
You can verify the build by following the Boost.Python tutorial
on Fri Dec 12 2008, "Rocketman-AT-JSC" wrote:
> Seems like this function only gets built into the debug version.
Are you certain? It's hard to imagine that's actually the case.
> We built the gcc library for 1.35 and it only appears in the
> libboost_python_gcc32-mt-d-1_35 version.
How did
on Mon Nov 24 2008, "Renato Araujo" wrote:
> Hi all,
> I would like to specify during the class_ declaration use a shared_ptr
> with custom release function.
>
> shared_ptr has a constructor where you can pass a function to call in
> the release, I would like to use this in a generic form.
>
> I
on Sat Nov 15 2008, "Leonard Ritter" wrote:
> yields ===
>
> /usr/include/boost/python/object/pointer_holder.hpp: In constructor
> 'boost::python::objects::pointer_holder Value>::pointer_holder(PyObject*)
> [with Pointer = boost::shared_ptr, Value = halebopp::Act
on Sat Nov 15 2008, "Leonard Ritter" wrote:
> I think I know what the issue is, and it indeed relates to a piece of code I
> have
> not posted yet.
>
> void Actor::add(const ActorPtr &actor) {
> assert(actor);
> assert(!actor->parent);
> actor->parent = ActorPtr(this);
Whoa, this i
Run bjam with "-n -a" and it will show you all the commands it
executed to build and run the test. That includes the info you're
looking for. Oh, unless you pass --preserve-test-targets, the
extension module is deleted when the test passes, so you might want to
touch the .cpp file and try
on Thu Nov 13 2008, Stefan Seefeld wrote:
> Alan Baljeu wrote:
>>
>> As best I could figure, I needed to write Python code, execute a script
>> file, get
>> that code to call a C function that I register, in order to have that
>> function. At
>> least the tutorial implied that was the way.
>
on Wed Nov 12 2008, Paul Melis wrote:
> David Abrahams wrote:
>> on Mon Nov 10 2008, Paul Melis wrote:
>>
>>
>>> The FAQ entry on this doesn't really help, so perhaps I'm not using the
>>> return
> policy
>>> correctly or
on Wed Nov 12 2008, Alan Baljeu wrote:
>>This sounds perfectly reasonable to me, FWIW.
>>An interesting question then is how you embed your interactive Python shell
>>into the
> application's main event loop. But that's mainly an implementation detail. :-)
>>
>>Regards,
> > Stefan
>
> Well
on Mon Nov 10 2008, Gennadiy Rozental wrote:
> Simple scenario:
>
> class IObject {};
>
> class Base : public IObject {
> public:
>virtual void foo() {}
> };
>
> class Derived : public Base {
>virtual void foo() {}
> };
>
> Both IObject and Base are exported into Python:
>
> bp::class_(
on Mon Nov 10 2008, Paul Melis wrote:
> The FAQ entry on this doesn't really help, so perhaps I'm not using the
> return policy
> correctly or missing something else. The full test code (which is actually
> quite
> small) is attached.
Please reduce it to its absolute minimum. Remove every si
on Sat Nov 01 2008, Paul Melis wrote:
> Gustavo Carneiro wrote:
>>
>> There's an interesting question about whether it's better to use
>> boost.python or SWIG. I've been using boost.python for years, so I
>> have a lot invested in it, but if I were starting from scratch, I
>> mig
Looks like you have a bug somewhere else. Trying to reduce this to a
minimal reproducible case will doubtless help you find it.
Sent from my iPhone
On Oct 30, 2008, at 5:38 AM, christophe grimault <[EMAIL PROTECTED]
> wrote:
Hi,
I wrote a function to speedup a part of my Python code that
on Wed Oct 29 2008, Hans Meine wrote:
> On Mittwoch 29 Oktober 2008, David Abrahams wrote:
>> The above should be a complete guide. Any questions?
>
> Great, thanks a lot for the write-up. I think my second question is still
> left, at least from your post and
on Wed Oct 29 2008, "Dan Eloff" wrote:
> On Wed, Oct 29, 2008 at 3:55 PM, David Abrahams <[EMAIL PROTECTED]> wrote:
>> The above should be a complete guide. Any questions?
>
> Just two.
>
> 1) Should it be object(handle<>(borrowed(ptr))) or
>
on Wed Oct 29 2008, Hans Meine wrote:
> On Mittwoch 29 Oktober 2008, Dan Eloff wrote:
>> When creating an object from a PyObject *, how do you distinguish
>> between a PyObject pointer that is a new reference (must not be
>> increfed, but must be decrefed) versus a PyObject * that is a borrowed
on Mon Oct 27 2008, "Robert Dailey" wrote:
> On Fri, Oct 24, 2008 at 1:07 PM, Stefan Seefeld <[EMAIL PROTECTED]> wrote:
>
> Robert Dailey wrote:
>
> Hi,
>
> What happens if I do the following?
>
> using namespace boost::python;
>
>
on Fri Oct 17 2008, "Furkan Kuru" wrote:
> Yes, that seems very likely; this looks a bit like the small string
> optimization gone awry. Perhaps you have mixed the MS runtime lib
> headers with a different version of the binary library.
>
> Is there any way to remove this string opt
on Fri Oct 17 2008, Stefan Seefeld wrote:
> Furkan Kuru wrote:
>> By the way
>>
>> I tried
>> "resize"ing and "reserve"ing of strings
>> by
>>
>> name.resize(1024);
>> or
>> name.reserve(1024);
>>
>> but it did not fix the problem.
>>
>> It seems that it allows up to 15 chars + null character to
61 matches
Mail list logo