https://github.com/boostorg/python/pull/315
Hello
Is there some further testing required for this to be merged to be
candidate to make it in the next release?
rds,
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/l
he flat_map and takes a single argument of the value_type, but I can't
find any.
If there's one, I would need pick a return value policy for it.
As a matter of fact, I've switched to std::unordered_map and std::map, and
I am encountering the same problem
MM
___
I thought I'd post this SO question here as well, thanks:
I exposed boost::gregorian::date with the following:
date_from_python_date{};
to_python_converter{};
where *date_to_python_date* is a struct with the right convert function: it
converts it to a python datetime.date. Some c++ functions ret
, i get the following error:
TypeError: No to_python (by-value) converter found for C++ type: T const*
Do I need another converter for T const* in particular? or for both T* and
T const*?
Does the class_ above only expose T itself, not pointers to it?
Thanks
MM
__
On 28 August 2015 at 16:05, Stefan Seefeld wrote:
> On 28/08/15 10:15 AM, MM wrote:
> >
> > Load 1 then 2 it should trigger the warning.
> > Apologies for missing the includes.
>
> I had to modify your code a bit as it triggers errors when compiled
> as-is. And with
On 28 August 2015 at 15:01, Stefan Seefeld wrote:
> On 28/08/15 09:26 AM, MM wrote:
> > This is in too separate modules.
> > The converter is registered in module1, and the class_ in
> > module 2.
> > I import 1 then 2, then it happens
> >
> > Also the i
On 28 August 2015 at 13:41, Stefan Seefeld wrote:
> On 28/08/15 07:49 AM, MM wrote:
> >
> > I expose the return type of a C++ function that is a pair of strings
> > with the following snippet:
> >
> > |to_python_converter,Converter>();|
> >
&g
for std::pair already registered; second conversion method ignored.
Is there a way to avoid this warning?
MM
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/listinfo/cplusplus-sig
On 13 August 2015 at 12:01, Stefan Seefeld wrote:
> On 13/08/15 06:58 AM, MM wrote:
> > On 13 August 2015 at 10:24, MM > <mailto:finjulh...@gmail.com>> wrote:
> >
> > I have the following class:
> >
> > class T {
> > };
On 13 August 2015 at 10:24, MM wrote:
> I have the following class:
>
> class T {
> };
> // T has been exposed to python with class_
>
> and free function:
>
> void add_T( T* );
>
> Ownership of the T* is taken by this C++ function.
>
>
> If I create a
I have the following class:
class T {
};
// T has been exposed to python with class_
and free function:
void add_T( T* );
Ownership of the T* is taken by this C++ function.
If I create an instance of the python version of T, how do I "def" the
add_T function?
def("add_T", add_T)
fails to co
On 3 October 2014 18:23, Jim Bosch wrote:
> On Fri, Oct 3, 2014 at 1:15 PM, Stefan Seefeld
> wrote:
>
>> On 2014-10-03 12:56, MM wrote:
>> > yes i did that.
>> >
>> > class C {
>> > public:
>> > const std::string&a
rty("name", &C::get_name, &C::set_name);
Which policy do I specify? and how do I set it in add_property?
MM
On 3 October 2014 17:50, Stefan Seefeld wrote:
> On 2014-10-02 16:09, MM wrote:
> > Hi
> >
> > class C {
> > public:
> > const std::s
do I use 2 mem function pointers to distinguish the 2 names, and pass
those 2 pointers?
MM
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/listinfo/cplusplus-sig
14 matches
Mail list logo
