On Tue, Mar 20, 2018 at 5:36 PM, Rob Gaddi
wrote:
> If all you're doing is a thin-wrapper around a C library, have you thought
> about just using ctypes?
Yep; the C library whose API I'm using uses macros to cast things to
the right structure, and (similar to Cython), as I already _have_ the
code
On Tue, Mar 20, 2018 at 5:25 PM, Grant Edwards
wrote:
> On 2018-03-20, Neil Cerutti wrote:
>
>> My automotive course will probaly divide cars into Automatic
>> Transmission, and Front Wheel Drive.
>
> I get your point: the two characteristics are, in theory, orthogonal.
> But, in the US, the two
On Tue, Mar 20, 2018 at 4:38 PM, Chris Angelico wrote:
> BTW, have you looked into Cython? It's smart enough to take care of a
> lot of this sort of thing for you.
I did a bit; this work is to replace our old python 2 SAML client,
which used python-lasso and python-libxml2, both packages that are
Hi all
I'm writing my first C extension for Python here, and all is going
well. However, I was reading [1], and the author there is advocating
Py_INCREF 'ing *every* borrowed reference.
Now, I get that if I do something to mutate and perhaps invalidate the
PyObject that was borrowed I can get unp
On Wed, Apr 7, 2010 at 4:10 PM, geremy condra wrote:
> On Wed, Apr 7, 2010 at 10:53 AM, Tom Evans wrote:
>> [ Please keep me cc'ed, I'm not subscribed ]
>>
>> Hi all
>>
>> I've written a bunch of internal libraries for my company, and they
>&
[ Please keep me cc'ed, I'm not subscribed ]
Hi all
I've written a bunch of internal libraries for my company, and they
all use two space indents, and I'd like to be more consistent and
conform to PEP-8 as much as I can.
My problem is I would like to be certain that any changes do not alter
the
