Hi All,
> That said, I propose following:
It seems there is no opposition to my proposal so I took liberty and
implemented it in the PR. Let me know what you think.
> In general, changing the code is not for everyone, passing a CLI option is
> easy. We should therefore prefer the CLI option over
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 take fully
qualified module name:
When we will introduce new `--shared` option we will have 3 places where we
can
Snap! Clicked send by mistake.
Another question popped in my mind. How we will deal with:
> Introduce new `cython` command parameter `--shared` which will take fully
qualified module name:
When we will introduce new `--shared` option we will have 3 places where we
can specify shared module ffull
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:
>>
>> I am not sure how
>
>
> 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
> What I understood from past discussions was that build systems (specifically
> Meson) would rather prefer calling "cython" over a "setup.py" build.
> Especially for larger packages like SciPy. Thus my comments regarding the
> "cython" CLI interface.
Yeah - agree with this.
My point with this
da-woods schrieb am 13.02.25 um 09:16:
> Most people will probably want to do this from setup.py instead of
> calling an executable [...]
we need something that can be run from the command-line, but the main users
are build systems (e.g. scikit-build/ meson) and not people.
What I understood fr
Hi,
I try not to think too hard about build systems because I don't really
understand them. But:
Most people will probably want to do this from setup.py instead of
calling an executable, so that's probably the most important interface.
I do agree we need something that can be run from the c
Hi,
matus valo via cython-devel schrieb am 11.02.25 um 20:25:
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.
I think the tool should be part of the normal cython command, maybe:
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.
10 matches
Mail list logo
