Hi All,
I would like to kindly ask about the status of PR
https://github.com/cython/cython/pull/4625. Is there any blocker accepting
it? I am asking since it is a prerequisite of
https://github.com/cython/cython/pull/4630.
Thanks
Matus
___
cython-devel
Hi All,
I opened several PRs several weeks/months ago. I understand that a
maintainer is an unpaid role so there are no expected deadlines, but still
I would kindly ask for code review of the PRs. All PRs except one underwent
several rounds of review, so they should be close to accepting (at least
Hi All,
I am working on porting scipy to Cython3. The last missing part in order to
have a test suite is 2 tests failing [1]. When I investigated the issue, I
found out that Cython has changed the type of Exception. Consider following
example:
cimport numpy as cnp
import cython
ctypedef fused np
Hi All,
I would like to request review of following PR:
https://github.com/cython/cython/pull/5386
PR is not complex and is important because of two reasons:
1. It blocks PR https://github.com/scipy/scipy/pull/18242. Hence, it will
allow us to have Cython 3 Beta in scipy which can help us test Cy
Hi All,
I would like to inform you about recent porting of projects to Cython 3.
Recently, I participated in migration of 3 bigger projects to Cython 3:
* Scipy - scipy main branch is currently compilable with Cython 3 with test
suite passing. Cython 3 master branch is used in CI to ensure that a
Hi All,
I was recently migrating uvloop to cython3 [1]. Unfortunately, after
switching to cython3, uvloop testsuite fails [2]. I am puzzled mainly about
following error:
==
ERROR: test_process_delayed_stdio__paused__no_stdin
(tes
> TypeError: C.f() got an unexpected keyword argument '__kwd'
> >>> C().f(_C__kwd=1)
> {'self': <__main__.C object at 0x7f299ef878d0>, '_C__kwd': 1}
>
>
> I haven't looked in much detail at exactly what's happening in uvloop, but
Hi All,
>
>> I seriously start wondering if we shouldn't just define
>> "Py_BUILD_CORE"
>
>
> This sounds just too much, and it's like a war declaration on what they
> are trying to do.
>
I have the same opinion. I think this will negate all effort that the C/API
workgroup is trying to do - to
Hi all,
There are several PRs targeted to Cython 3.0.X [1]. Is it possible to push
all of them or some of them are not ready? At least
https://github.com/cython/cython/pull/5754 we can kick of without any
doubt. Me personally, I would prefer to include following two PRs:
* https://github.com/cyt
