Re: [Cython] Shared utility Option vs. Compilation Directive

t; will usually be right (it forces a setting on every module that you're > processing in a batch, which is what most people will want here. But maybe > not everyone). > > David > > > On 03/03/2025 19:47, matus valo wrote: > > Hi All, > > Based on the comment

[Cython] Shared utility Option vs. Compilation Directive

Hi All, Based on the comment https://github.com/cython/cython/pull/6531#discussion_r1975502026 I would like to start a discussion about using Option vs Compilation Directive. Basically, we have 3 options: 1. Use PR https://github.com/cython/cython/pull/6531 as is. I will proceed with the rest of

Re: [Cython] CLI for using Shared utility module

17:37, Stefan Behnel via cython-devel < cython-devel@python.org> wrote: > matus valo via cython-devel schrieb am 15.02.25 um 00:07: > > Another question popped in my mind. How we will deal with: > > > >> Introduce new `cython` command parameter `--shared` which will ta

Re: [Cython] CLI for using Shared utility module

uld do if 1. and 2. are set but have different values? Matus On Sat, 15 Feb 2025 at 00:00, matus valo wrote: > Another question popped in my mind. How we will deal with: > > Introduce new `cython` command parameter `--shared` which will take > fully qualified module name: > > O

Re: [Cython] CLI for using Shared utility module

Another question popped in my mind. How we will deal with: > Introduce new `cython` command parameter `--shared` which will take fully qualified module name: On Fri, 14 Feb 2025 at 16:06, matus valo wrote: > >> I think I tend to agree with David. Here is my point of view: >>

Re: [Cython] CLI for using Shared utility module

> > > I think I tend to agree with David. Here is my point of view: > > I am not sure how to implement it. cython command *does not know* about > the build directory. This is more part of the build system > (setuptools/meson etc). My point is that the cython command should be > stupid and just gene

[Cython] CLI for using Shared utility module

Hi All, I am writing to you to not get lost in https://github.com/cython/cython/pull/6531. I would like to get an agreement on how we would like to proceed with a CLI. The PR has two parts: 1. Utility for generating C file of shared utility. Here, I propose to pass the full path to the file e.g.

Re: [Cython] Ready for Cython 3.1 ?

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

Re: [Cython] Should we start using the internal CPython APIs?

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

Re: [Cython] uvloop issue in Cython3

> 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

[Cython] uvloop issue in Cython3

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

[Cython] cython 3 migration update and next releases

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

[Cython] PR review request

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

[Cython] fused type error changed in Cython 3

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

[Cython] Open PRs

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

[Cython] PR #4625 status and next steps

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