octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suggestion on priorities for improving pytave


From: Abhinav Tripathi
Subject: Re: Suggestion on priorities for improving pytave
Date: Thu, 7 Jul 2016 21:52:55 +0530


On Jul 7, 2016 1:01 PM, "Colin Macdonald" <address@hidden> wrote:
>
>
> At least for now, I think you're right.
>
>
>> pystore ("var_with_req_name", req_octave_value);
>
>
> Its possible that we don't want to expose such a thing (although we may want it internally).
>
> Why?  We don't really want the user to have to track a mental model of variables in Python space.  She should just have some Octave objects (doubles, strings) and some @pyobjects (dicts, modules, whatever).  And then do things to those objects.
>

Ohk. I understand. But still, if it an extra feature and we don't let the user rely on it. It can be helpful?!

>>     Maybe some kind of support for function kwargs as well? A scalar struct
>>     to pass named parameters?
>>
>> This could prove to be a bit tricky. I tried but couldn't use map
>> unpacking to call a python function.
>
>
> Please file an issue for this kwargs stuff.  It'll be important, even if we can't do it right now.
>
> Colin

Oh sorry. I think I missed kwargs thing and only remembered scalar struct thing.
I have used/created functions with variable arguments in c++ but never in python. I see how to do that.
I'll file an issues on bitbucket.

Abhinav


reply via email to

[Prev in Thread] Current Thread [Next in Thread]