scoder

I currently don't have time to look into this, but if you could dig up the generated C code snippet(s), then I might have an idea on what to do...

Right, thanks for investigating. Since this is essentially legacy code that will be used much less (but will still be there) starting with Cython 3.0, I think it's best to...

I was wondering whether this fairly old ticket is still relevant, but seeing the references in https://github.com/cython/cython/issues/6129 makes me think that it still solves a user issue. I'm not sure...

We could allow something like import cython cython = cython.in_version(">=3.0") It would be ignored in compiled code (or maybe fail the build if the Cython version is older), but could...

> However there's no reason not to do it right. Except speed. For short data structures (which are not uncommon), even just trying to read the length hint from a...

> ``` > '/usr/bin/python3 -m pip install .' > ``` I don't understand that line in the test. It probably won't work outside of venvs, and it modifies the venv...

In any case, it's a bug in the test, not in Cython itself. Excluding the test is fine if you want to make the test suite pass again.

We're using Tempita for the memoryview code already, so if we add feature tracking, it should be easy to spread template conditions over the code.

Yeah, there are a couple of issues here. One thing is that the C data type cross reference apparently doesn't work. Not sure why. The rest are mostly legitimate ReST...

@cjdsellers difficult to say. To me, it feels like this PR is trying to do way too many things, but @nocarryr apparently got there by trying simpler things first, so...