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
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,
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:
Stefan Behnel schrieb am 05.11.23 um 23:06:
I'd like to ease our feature development by using more modern Python
features in our code base and by targeting less Python versions in Cython
3.1 compared to the "all things supported" Cython 3.0.
I created a 3.0.x maintenance bra
Lisandro Dalcin schrieb am 06.11.23 um 09:05:
On Mon, 6 Nov 2023 at 01:19, Stefan Behnel wrote:
it looks like Cython 3.0.6 is going to be a "most things fixed" kind of
release for the 3.0.x release series.
I'm having issues using CYTHON_LIMITED_API with some Python versions
da-woods schrieb am 06.11.23 um 08:48:
> I also consider Cython 3.1 a prime target for better Limited API support.
Yes - but I wouldn't treat complete support as a blocker (I don't think
this is what you meant though).
It's experimental in 3.0 and I don't expect it to "fully" work in 3.1.
da-woods schrieb am 04.11.23 um 14:45:
I'm a bit late in replying to this but here are some unordered thoughts.
* I'm fairly relaxed about using `Py_BUILD_CORE` if useful - I think we
mostly do have good fallback paths for most things so can adapt quickly
when stuff changes.
I'm not entirely
Hi all,
it looks like Cython 3.0.6 is going to be a "most things fixed" kind of
release for the 3.0.x release series. Given the work that lies ahead of us
for Cython 3.1, I think we're at a point to get started on that, making the
future 3.0.x releases stable and "boring".
As a reminder, Cyt
Thank you for your comments so far.
Stefan Behnel schrieb am 29.10.23 um 22:06:
I seriously start wondering if we shouldn't just define
"Py_BUILD_CORE" (or have our own "CYTHON_USE_CPYTHON_CORE_DETAILS" macro
guard that triggers its #define) and include the inter
Hi all,
given the latest blow against exposing implementation details of CPython in
their C-API (see https://github.com/cython/cython/pull/5767 for the endless
story), I seriously start wondering if we shouldn't just define
"Py_BUILD_CORE" (or have our own "CYTHON_USE_CPYTHON_CORE_DETAILS" mac
da-woods schrieb am 19.09.23 um 21:38:
I think the detail that was missing is you need to add the `#cython:
fast_gil = True` to enable it.
[...]
So my conclusion is that from 3.11 onwards Python sped up their own GIL
handling to about the same as we used to have, and fastgil has turned into
a
Hi,
I've seen reports that Cython's "FastGIL" implementation (which basically
keeps the GIL state in a thread-local variable) is no longer faster than
CPython's plain GIL implementation in recent Python 3.x versions.
Potentially even slower. See the report in
https://github.com/cython/cython
Hi all,
Cython 3.0.2 is released. It fixes two major regressions in 3.0.1, so
please upgrade if that failed for you.
https://cython.readthedocs.io/en/latest/src/changes.html
Have fun,
Stefan
___
cython-devel mailing list
cython-devel@python.org
http
Hi all,
after close to five long years, I'm proud to announce the release of
Cython 3.0. It's done. It's out. Finally!
The full list of improvements compared to the 0.29.x release series is
entirely incredible.
https://cython.readthedocs.io/en/latest/src/changes.html
Cython 3.0 is better tha
Hi all,
after close to five long years, we're almost there – I've pushed a release
candidate for Cython 3.0 with a long list of bug fixes (followed by a
second one with one important fix).
https://cython.readthedocs.io/en/latest/src/changes.html
Please give it some final testing. Unless we f
Hi,
just a note that the current CI crashes in Py3.12b1 are due to
https://github.com/python/cpython/issues/104614
They fixed it and Py3.12b2 will hopefully support multiple inheritance of
extension types again. It's expected next week (June 6th).
Stefan
_
Dima Pasechnik schrieb am 21.05.23 um 11:38:
On Sun, 21 May 2023, 10:21 Stefane Fermigier, wrote:
IFAIK, 15k lines of Cython makes it among one of the largest Cython
projects I'm aware of (I did some research a couple of years ago):
https://github.com/sfermigier/awesome-cython#some-projects-wi
matus valo schrieb am 16.05.23 um 21:09:
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:
Thanks a lot for doing this, Matúš. It helps Cython as much as it helps
these projects.
When migrating t
PI.
https://cython.readthedocs.io/en/latest/src/changes.html#beta-2-2023-03-26
Have fun,
Stefan
Stefan Behnel schrieb am 26.02.23 um 11:31:
Hi all,
Cython 3.0 has left the alpha status – the first beta release is available
from PyPI.
The changes in this release are huge – and the full list of improvements
c
Hi all,
Cython 3.0 has left the alpha status – the first beta release is available
from PyPI.
The changes in this release are huge – and the full list of improvements
compared to the 0.29.x release series is entirely incredible. Cython 3.0 is
better than any other Cython release before, in a
Hi Matúš,
Matúš Valo schrieb am 06.12.22 um 15:58:
I have a thought about Cython 3.0. Based on discussion in [1] we should be
done with all breaking changes. There is also [2] but PR is already there
[3] (I am not sure what is the state of the PR though).
Is it possible to make final release (I
Hi,
I'll try to push out the next 0.29.x (and hopelfully also 3.0alpha) release
before Christmas. If you think I might have forgotten anything that's ready
to be included in 0.29.33, please comment in the relevant ticket or PR, or
reply to this message on cython-users.
Stefan
___
Hi everyone,
with the release of the first 3.0 alpha that supports Python 3.11 (aptly
named "alpha 11"), I'm happy to announce that David Woods has been promoted
to a Cython core developer.
David has shown an extraordinary commitment and dedication over the last
years. His first merged commi
Hi,
nested prange loops seem to be a common gotcha for users. I can't say if
there is ever a reason to do this, but at least I can't think of any. For
me, this sounds like we should turn it into a compile time error – unless
someone can think of a use case? Even in that case, I'd still emit a
Dear Cython community,
it's now 20 years since Greg Ewing posted his first announcement of Pyrex,
the tool that is now known and used under the name Cython.
https://mail.python.org/pipermail/python-list/2002-April/126661.html
It was a long way, and I've written up some of it in a blog post:
website.reader via cython-devel schrieb am 25.01.22 um 01:09:
I am not familiar with Cython, but have spent a few weeks looking at compiler warnings
posted when the mathematical package called "sage v9.4" is compiled, which
takes several hours to build, since hundreds of code units are invovled
Hi,
I just released 0.29.25 and would like to let the next 3.0 alpha follow it
soon. Please ping me on any PRs that you think are ready enough to include
and short enough to merge quickly.
Thanks,
Stefan
___
cython-devel mailing list
cython-devel@p
Am 26. Oktober 2021 07:54:10 MESZ schrieb Lisandro Dalcin:
>In any case, if you know how and can implement the __future__ import,
>that
>would be great. Otherwise, valid Python3 code using that import
>currently fails to compile in Cython.
Probably just an oversight. A no-op future import is trivi
This should also have gone to cython-users (not just cython-devel), as it
has the larger audience.
Stefan Behnel wrote:
Hi,
I looked up where Python 3.4 is still being used.
Ubuntu 14.04 – EOS 2019, EOL April 2022
Debian 8 – EOL
Centos 6 – EOL
Later distribution versions have newer CPythons
Hi,
I looked up where Python 3.4 is still being used.
Ubuntu 14.04 – EOS 2019, EOL April 2022
Debian 8 – EOL
Centos 6 – EOL
Later distribution versions have newer CPythons:
Ubuntu 16.04: Py3.5 (EOS April 2021, EOL 2024)
Debian 9: Py3.5 (EOL June 2022)
Centos 7: Py3.6 (EOL June 2024)
I thin
Hi all,
I just released the next alpha version of Cython 3.0.
It's been a while since the last release, almost 10 months, it seems, so
there is a fairly long list of changes. And I haven't even merged all PRs
yet that are still waiting to make it into the final release.
https://github.com/cython
Hi Lisandro! :)
Lisandro Dalcin schrieb am 24.03.21 um 21:27:
> On Wed, 24 Mar 2021 at 23:08, Stefan Behnel wrote:
>> I'll prepare a new 3.0 alpha release during the next days. If you have or
>> know anything that is ready for inclusion that I should take a look at,
>> p
Hi,
I'll prepare a new 3.0 alpha release during the next days. If you have or
know anything that is ready for inclusion that I should take a look at,
please send me a quick note.
Stefan
___
cython-devel mailing list
cython-devel@python.org
https://mail.
Am 2. August 2020 17:02:39 MESZ schrieb da-woods:
> I'm not convinced that compiler directives like "infer_types" should
> propagate into the cimported files at all.
>
> It seems reasonable to me that these should be controlled by the author
> of the pxd file, not by the eventual cimporter.
I agr
Oliver Haas schrieb am 02.08.20 um 13:44:
> The array.pxd (
> https://github.com/cython/cython/blob/master/Cython/Includes/cpython/array.pxd)
> requires infer_types = True when cimported. Is there a reason not to
> explicitly type the variable op as array in the lines 134 and 141?
The return type
Hi Marcel,
thanks for testing this, and for triaging the issues!
Marcel Plch schrieb am 27.05.20 um 10:27:
> In Fedora, we rebuilt 152 packages against Cython 3.0a5 we have found
> some breakages that might be relevant to you. We are not entirely sure
> whether these issues are caused by the indi
S.rst
Let's see where fate takes these releases.
Stefan
Stefan Behnel schrieb am 05.05.20 um 19:32:
> Hi all,
>
> here's yet another alpha release for you, with some great new features and
> even more bug fixes this time, and now hopefully generating proper C code
> for n
Jakub Wilk schrieb am 06.05.20 um 20:31:
> Hi Stefan!
>
> Could you push the 3.0a4 tag to GitHub?
Done, thanks for the reminder.
Stefan
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
S.rst
I'll wait a day or two for reports on bugs and regressions and then also
prepare the corresponding 0.29.18 release with the relevant beckported bug
fixes.
Have fun,
Stefan
Stefan Behnel schrieb am 27.04.20 um 18:36:
> … and a third alpha is out, with several fixes (thanks!)
//github.com/cython/cython/blob/master/CHANGES.rst
>
> Have fun,
> Stefan
>
>
>
> Stefan Behnel schrieb am 12.04.20 um 12:24:
>> Dear Cython users and devs,
>>
>> today, I'm happy to announce the first alpha release of Cython 3.0.
>>
>> htt
da-woods schrieb am 23.04.20 um 22:54:
> On 23/04/2020 21:32, Stefan Behnel wrote:
>> The question is: how bad is it for existing code, and how can we either
>> keep things working or make it easy for users to adapt? Should we implement
>> some kind of fallback lookup that
da-woods schrieb am 23.04.20 um 20:47:
> On closer inspection I believe both are following Python behaviour (and
> thus behaving correctly). In Python any
> `__name_preceded_by_double_underscores` used within a class ends up looking
> up `_Classname__name_preceded_by_double_underscores`. Therefore
Hi,
thanks for the very detailed report.
I'm CC-ing cython-devel, but let's keep the discussion for this on the
cython-users list.
The background here is Github issue 1382 and PR 3123
https://github.com/cython/cython/issues/1382
https://github.com/cython/cython/pull/3123
This was newly merged
Hi all,
here's the second alpha. I hope we got all major regressions fixed for this
release that were reported since alpha 1.
Download:
https://pypi.org/project/Cython/3.0a2/
Changelog:
https://github.com/cython/cython/blob/master/CHANGES.rst
Have fun,
Stefan
Stefan Behnel schri
Hi Volker!
Volker Weißmann schrieb am 22.04.20 um 20:44:
> cy exec print(localvar)
>
> currently does not work. And I need your help to fix it.
Do you mean "cy exec print(x)" or "cy print x" here? (The latter is what
you used in your example at the end.)
> If I'm not mistaken, the function "_f
Dear Cython users and devs,
today, I'm happy to announce the first alpha release of Cython 3.0.
https://pypi.org/project/Cython/3.0a1/
It took us a while to get to this point, well more than a year's time, but
we received a lot of help along the way, most notably from David Woods,
Jeroen Demeyer
Hi all,
I'm curently preparing a first alpha release for Cython 3.0 (alpha 1).
Please ping me on any open pull requests that you think are ready and
should be included.
Note that this is not the end of the journey – anything that's not included
right now can still come in later, before the first
da-woods schrieb am 12.03.20 um 16:11:
> The process of wrapping a C struct or C++ class in an extension type often
> has the user doing a pretty mechanical duplication of attributes/functions
> that Cython already knows about. I'm looking at doing:
>
> cdef struct S:
> int a
> # etc.
>
>
John Skaller2 schrieb am 01.02.20 um 15:38:
> On 1 Feb 2020, at 20:00, Greg Ewing wrote:
>> On 1/02/20 3:29 pm, John Skaller2 wrote:
>>> But the all hell breaks loose for pointers. Your hack only
>>> works for rvalues.
>>
>> Yes, using these it's possible for Cython to accept something
>> that will
John Skaller2 schrieb am 01.02.20 um 15:32:
> My problem is trying to read the generated code.
You might be looking for "cython -a".
Stefan
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
Robert Bradshaw schrieb am 01.02.20 um 00:49:
> Taking a quick glance at an auto-generated file for an empty .pyx, we have
> [...]
> ~300 lines module setup code. Even for trivial modules, we still
> declare and call functions for creating globals, preparing types, etc.
> even if we don't have any
John Skaller2 schrieb am 30.01.20 um 03:47:
> Ok, I have processed most of the Cython/Include/python/*.pxd files.
>
> Seems these were mechanically derived from docs?
They were manually copied over time.
> Because some of the bugs in the docs are also in these files. Not sure what
> you
> woul
John Skaller2 schrieb am 28.01.20 um 10:57:
> What’s a “descr” when its at home?
A descriptor, a special protocol in Python.
https://docs.python.org/3/howto/descriptor.html
> There are some special words in pxd files like “list” which mean
> PyObject that happens to be a list. Is there a list o
John Skaller2 schrieb am 27.01.20 um 06:56:
> Hi! I have just built Cython but haven’t used it yet.
>
> I want to check I understand what it does whilst examing the sources in the
> repository.
> Please let me know if I have it wrong!
>
> Given a Python file, Cython parses it, and translates it
Hi Frank,
sorry for leaving this unresponded for a while. I'm far from an expert in
this, but it looks like no-one else jumped in, so here's my response.
Schlimbach, Frank schrieb am 06.01.20 um 12:09:
> I would like to work on extending cython with a way to offload cython code to
> a GPU. I fo
omár sweidán schrieb am 08.01.20 um 22:47:
> Is there a way for me to contribute to the C files in the Cython folder?
> When I changed them, it does not show in the changed files list (e.g. in
> Git GUI). Why are the C files put in the gitignore file?
We exclude all files that are generated by Cyt
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/5
Jeroen Demeyer schrieb am 27.06.19 um 12:44:
> Since Cython 3.0 doesn't seem close to being released, is there any chance
> to backport https://github.com/cython/cython/pull/2792
>
> It's a fairly simple and reasonable bugfix.
Done:
https://github.com/cython/cython/commit/d019d9f3e057cae5f873280b
Jeroen Demeyer schrieb am 18.06.19 um 13:47:
> What's the purpose of commit
> https://github.com/cython/cython/commit/8ac1a6a55fc44ff858cc367af556250a91f71d16
>
> I can't think of any reasonable scenario where Py_TPFLAGS_METHOD_DESCRIPTOR
> would be defined differently than in CPython (i.e. with v
Jeroen Demeyer schrieb am 13.06.19 um 15:14:
> Is there any particular reason why Cython has specific code like
> __Pyx_PyObject_Call2Args, __Pyx_PyObject_Call3Args, ...
>
> And then there is even more complicated Python code in PyMethodCallNode
> generating something like __Pyx_PyObject_Call2Args
Stefan Behnel schrieb am 16.02.19 um 22:39:
> - The list append/pop optimisations seem to slow down non-lists
> unproportionally, for deques by 3x compared to CPython. That seems worth
> improving.
>
> CPython 3.8 (63fa1cfece)
>
> Stack (or queue) op
Hi,
Raymond Hettinger wrote a micro benchmark script for comparing the
performance of basic attribute and item access patterns across Python
versions and build configurations, so I tested the initially committed
version with Cython.
https://github.com/python/cpython/blob/master/Tools/scripts/var_
Robert Bradshaw schrieb am 11.02.19 um 16:54:
> On Fri, Feb 8, 2019 at 12:45 PM Stefan Behnel wrote:
>> Robert Bradshaw schrieb am 06.02.19 um 10:37:
>>> Realistically, I think that if we don't support 2.7 in the 3.0
>>> release, we're signing up for maintaini
Hi everyone,
Cython 0.29.5 was released with an important bug fix for extension types
that have "cpdef" methods. If they get subclassed by Python classes that do
not define additional attributes (or anything that would require them to
have an instance `__dict__`), then calling the cpdef-methods re
Stefan Behnel schrieb am 02.02.19 um 12:22:
> We currently support Py3.3+ for Py3. Py3.4 is expected to reach its EOL
> in March, but still seems worth supporting for another while. Not sure
> about 3.3, probably an "as long as it doesn't hurt" case.
Actually, I just
[CC-ing cython-devel, but please keep the discussion on cython-users]
Hi all,
we were recently asked on the bug tracker [1] when Cython is planning to
end its support for Python 2.x, so I'd like to get some more user opinions
on this.
We are planning to release Cython 3.0 this year [2], with som
Hi all,
I just released Cython 0.29.4 with an important bug fix(*) for division
operations that involve constant numerators. If the denominator turns out
to be zero at runtime, it could happen that no ZeroDivisionError gets
raised, and instead an arbitrary result returned.
https://github.com/cyth
Hi all,
there is currently a discussion on python-dev about letting the compiler
generate more SyntaxWarnings for "obviously unintended" code.
https://mail.python.org/pipermail/python-dev/2019-January/156113.html
Serhiy Storchaka has written a proof-of-concept patch for CPython here:
https://bu
Jeroen Demeyer schrieb am 09.01.19 um 15:43:
> (reviving this thread after I thought about it some more...)
>
> As I mentioned in the original post, I want something like __dealloc__ but
> with access to a particular cdef attribute (representing a Python object).
> Since Python attributes of cdef
Hi!
Nice idea.
Prakhar Goel schrieb am 29.12.18 um 15:02:
> I wanted to test the waters on this idea.
>
> The idea is to allow debugging Cython programs with PDB. This relies
> on making call-backs to trigger the sys.trace functionality every now
> and then. It is very similar to how profiling i
Ricardo Dias schrieb am 11.12.18 um 23:16:
> On 11/12/18 19:39, Stefan Behnel wrote:
>> Ricardo Dias schrieb am 10.12.18 um 14:42:
>>> In the recent Cython 0.29 version was introduced a commit [1] that
>>> hinders the usage of python subinterpreters.
>>>
>
Ricardo Dias schrieb am 10.12.18 um 14:42:
> In the recent Cython 0.29 version was introduced a commit [1] that
> hinders the usage of python subinterpreters.
>
> I discovered this the hard way when suddenly a component I was working
> on started to crash. The component in question is the ceph-mgr
Robert Bradshaw schrieb am 24.10.2018 um 01:44:
> On Tue, Oct 23, 2018 at 10:22 PM Stefan Behnel wrote:
>> My guess is that MinGW is just fairly rarely used to build CPython
>> extensions overall.
>>
>>> but perhaps we should even consider releasing bugfixes fo
Robert Bradshaw schrieb am 22.10.2018 um 11:03:
> Given that https://bugs.python.org/issue4709 results in extension
> modules that seem to work, but silently produce completely incorrect
> answers, I'm thinking we should either disable our long-unpacking code
> on these platforms, or at the very le
Jeroen Demeyer schrieb am 21.10.2018 um 12:47:
> On 2018-10-16 20:30, Stefan Behnel wrote:
>> Difficult to say why this would fail to find the package. Could it be an
>> import path problem? Current directory missing from the PYTHONPATH or
>> something like that?
>
> Th
Jeroen Demeyer schrieb am 16.10.2018 um 12:42:
> I'm getting various reports of the test reimport_from_subinterpreter
> failing (within Sage, Cython 0.29, Python 2.7.15).
>
> Annoyingly, the problem can only be reproduced when running the full Cython
> testsuite, not when running the test in isola
Dear Cythonistas,
after half a year of development, many community pull requests and a lot of
feedback and good ideas in online discussions and at conferences, I'm proud
to release Cython 0.29. This is a major feature release that comes with
many great improvements and several important bug fixes.
https://github.com/cython/cython/archive/0.29rc2.tar.gz
Updated changelog:
https://github.com/cython/cython/blob/0.29rc2/CHANGES.rst
Stefan
Stefan Behnel schrieb am 16.09.2018 um 17:48:
> Hi all,
>
> after half a year of development, many community pull requests and a lot of
>
Stefan Behnel schrieb am 21.09.2018 um 09:38:
> There are two parts of
> information here, so maybe we should actually split them internally (in
> "Main.Context.set_language_level() ?) and keep the language_level = 3 but
> just avoid the "unicode_literals" part.
I t
John Ehresman schrieb am 25.09.2018 um 16:27:
> On 9/25/18 1:24 AM, Stefan Behnel wrote:
>> I started off with "unicode_literals=False", and then renamed it because
>> this name didn't cover the change of "str" to "unicode" (i.e. renaming the
>
Daniele Nicolodi schrieb am 25.09.2018 um 00:28:
> On 24-09-2018 14:05, Stefan Behnel wrote:
>> I added a new directive "str_is_str=True" which can be combined with
>> "language_level=3" to get the desired behaviour. It keeps the 'str' builtin
>>
S.rst
Stefan
Stefan Behnel schrieb am 16.09.2018 um 17:48:
> Hi all,
>
> after half a year of development, many community pull requests and a lot of
> feedback and good ideas in online discussions and at conferences, I'm proud
> to release the first beta of Cython 0.29. This i
Stefan Behnel schrieb am 21.09.2018 um 17:46:
> Robert Bradshaw schrieb am 21.09.2018 um 17:30:
>> I agree that this doesn't really feel like a language-level thing.
>>
>> There seem three desired behaviors here:
>>
>> language_level=2 where cu
Jeroen Demeyer schrieb am 20.09.2018 um 10:59:
> On 2018-09-20 10:15, Jeroen Demeyer wrote:
>> On 2018-09-20 07:55, Stefan Behnel wrote:
>>> I can see that this would be helpful. It's unfortunate, though, that this
>>> would introduce a temporary option that
Jeroen Demeyer schrieb am 18.09.2018 um 10:23:
> On 2018-09-16 17:48, Stefan Behnel wrote:
>> * Cython now emits a warning when no ``language_level`` (2 or 3) is set
>> explicitly
>
> Currently, language_level=3 breaks a lot of code due to unicode_literals.
> As I m
Robert Bradshaw schrieb am 17.09.2018 um 15:44:
> One of the pain points in Cython is that one must explicitly annotate
> non-object returning functions with except clauses. Would it be worth
> trying to change the default here, making exception-suppressing opt-in
> rather than opt-out?
>
> There
Robert Bradshaw schrieb am 17.09.2018 um 15:44:
> One of the pain points in Cython is that one must explicitly annotate
> non-object returning functions with except clauses. Would it be worth
> trying to change the default here, making exception-suppressing opt-in
> rather than opt-out?
>
> There
Hi all,
after half a year of development, many community pull requests and a lot of
feedback and good ideas in online discussions and at conferences, I'm proud
to release the first beta of Cython 0.29. This is a major feature release
that comes with many great improvements and several important bu
Jeroen Demeyer schrieb am 22.08.2018 um 13:10:
> On 2018-08-19 08:26, Stefan Behnel wrote:
>> Should we make that a new directive rather than a language level? Like
>> "py2_str=str"? That would allow its use together with language_level=3
>> already in the ne
Jeroen Demeyer schrieb am 07.09.2018 um 10:14:
> On 2018-09-07 06:35, Stefan Behnel wrote:
>> Maybe you actually want "tp_finalize"?
>>
>> https://www.python.org/dev/peps/pep-0442/
>>
>> Cython moves "__del__" methods there in Py3.4+.
>
>
Jeroen Demeyer schrieb am 06.09.2018 um 22:54:
> Cython's __dealloc__ special method is meant to deal with cleaning up
> instances of cdef classes. However, this hooks tp_dealloc() and does not
> have meaningful access to Python attributes, since those might have been
> cleared by tp_clear().
>
>
Am 18. August 2018 21:11:14 MESZ schrieb Jeroen Demeyer:
>>> Basically I am asking for
>>>
>>> type("foo") is str
>>>
>>> both on Python 2 and Python 3.
>>
>> That's another breaking change
>
>I'm not following here... what I'm asking is how Cython behaves
>currently (with language_level=2).
But
Am 18. August 2018 12:06:15 MESZ schrieb Jeroen Demeyer:
>On 2018-08-18 10:52, Robert Bradshaw wrote:
>> Do the existing c_string_type and c_string_encoding directives not
>> cover this usecase?
>
>Those seem to refer to C strings, I am talking about the Python type of
>string literals.
>
>> I supp
Hi all,
following the versioning discussion, I created a milestone to collect
(breaking) changes that should go into the future Cython 3.0 release.
https://github.com/cython/cython/milestone/58
While a major version change is a good time to fix things that, in
retrospect, have led us too far in
Yury V. Zaytsev schrieb am 17.08.2018 um 10:59:
> On Fri, 17 Aug 2018, James C. McPherson wrote:
>> 1.0 runs the risk of hitting "never install a 1.0 release" habits.
>
> How about 2.9.0 ;-) ?
Sold! :)
Proposal: we'll release a 2.9.0 next, which gives a warning that users
should explicitly enabl
Robert Bradshaw schrieb am 16.08.2018 um 00:48:
> If we're going to ditch the 0.x, I'd go for 1.0 as well. I'm a huge fan of
> semantic versioning.
I'm ok with it, just fear that it might become excessive for Cython (ok,
I'm the one who proposed jumping to 29.0, but...). Basically, any time we
add
Hello everyone,
I had a request during my talk at EuroPython this year to help the aspiring
Cython users out there convince their managers to accept Cython in their
tech stack.
Cython has been around for more than a decade now, has been in heavy
production use pretty much all of that time, has pr
Hi all,
when building Cython, it compiles a couple of its own modules. I was
interested in what this brings for the separate parts of the compiler, so I
used the compilation of Cython's compiled modules as benchmark and compiled
the separate parts incrementally, using the latest CPython 3.7.0.
Ba
Hi,
Python 3 is clearly taking over the world these days, so it starts feeling
arcane to require Py2 syntax in .pyx files. Increasingly, it means that
people cannot just rename .py files anymore to start optimising them,
because the .py file has a high chance of being written in Py3 syntax.
Event
Hi Patrick!
Patrick Kunzmann schrieb am 18.05.2018 um 10:50:
> I would like to contribute to the Cython project but it is difficult for me
> to find an angle to understand the code base. Is there some kind of
> developers' tutorial or another resource to start with?
Welcome, looks like you found
1 - 100 of 1422 matches
Mail list logo
