From stefan_ml at behnel.de Sun Aug 4 03:16:22 2019 From: stefan_ml at behnel.de (Stefan Behnel) Date: Sun, 4 Aug 2019 09:16:22 +0200 Subject: [Cython] Progress towards Cython 3.0 Message-ID: Hi, tl;dr: help with the remaining work would be appreciated. The "3.0" milestone on github currently lists 24 open tickets, so there's still quite a bit to do before the release. Some of them are already PRs that need more work in one way or another. https://github.com/cython/cython/milestone/58 The upside is that we've already closed twice as many issues as are still open. https://github.com/cython/cython/issues?utf8=?&q=is%3Aclosed+type%3Aissue+milestone%3A3.0 I went through the open issues and marked everything as "blocker" that represents behavioural changes. We should make sure to include those in this release, or postpone them to the next major release. https://github.com/cython/cython/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3A%22P%3A+blocker%22+milestone%3A3.0 Some tickets seem easy to do (marked as "good first issue"). But also the "binding" PR is a big one that will need some more fiddling with the details, some of which can be investigated separately. https://github.com/cython/cython/pull/2864 Any help with the open issues would be greatly appreciated. Stefan From J.Demeyer at UGent.be Sun Aug 4 17:36:00 2019 From: J.Demeyer at UGent.be (Jeroen Demeyer) Date: Sun, 4 Aug 2019 23:36:00 +0200 Subject: [Cython] Progress towards Cython 3.0 In-Reply-To: References: Message-ID: <5D474FC0.9090407@UGent.be> On 2019-08-04 09:16, Stefan Behnel wrote: > But also the > "binding" PR is a big one that will need some more fiddling with the > details, some of which can be investigated separately. Does that have to be part of Cython 3.0? It may not be worth blocking Cython 3.0 for this. From jeroen.k.demeyer at gmail.com Thu Aug 8 16:32:25 2019 From: jeroen.k.demeyer at gmail.com (Jeroen Demeyer) Date: Thu, 8 Aug 2019 22:32:25 +0200 Subject: [Cython] How to detect CyFunction? Message-ID: Hi, I have a very technical question about Cython.Compiler.Nodes.DefNode: how can I know whether the instance represents a PyCFunction (built-in function) or a CyFunction (Cython function)? I've tried all the obvious conditions such as checking self.is_cyfunction, self.py_cfunc_node.binding and env.directives['binding'] I'm asking because I want to implement METH_FASTCALL support for PyCFunction instances. See https://github.com/cython/cython/pull/3021 To keep things simple, I don't want to deal with CyFunction initially. But I really can't figure how to make that distinction from the DefNode.