On Mon, Jun 2, 2014 at 6:13 AM, Paul Moore <p.f.mo...@gmail.com> wrote:
> On 29 May 2014 13:36, Chris Farrow <cfar...@enthought.com> wrote:
> > Numpy should certainly be optional. I have created an issue for this:
> > https://github.com/enthought/comtypes/issues/55. We'll look into it.
>
> I've just added a PR which fixes the BSTR issue for me, basically by
> adding an explicit check for BSTR as a primitive type (like VARIANT).
> It works for me, although it's a long time since I understood COM
> refcounting semantics, so I may not have got the memory management
> right.
>
Thanks for the PR. I'll take a look as soon as I can.
>
> Also, it does nothing for the "numpy should be optional" question, it
> just avoids hitting it in this specific case.
>
> Paul
>
> PS The tests for safearray may need looking at as well - there's a
> BSTR test that seems to rely on the current behaviour of using numpy,
> if I'm reading it right - although I'm not clear why that would be
> seen as correct behaviour.
>
I'll look into this as well. In the off chance that we're breaking
backwards compatibility, then we may have to consider another approach -
something like try numpy first, and fall back to tuple if that fails.
Cheers,
Chris
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
comtypes-users mailing list
comtypes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/comtypes-users
