scoder

> 4. I want to use VSCode. > 5. I want to use Intellisense. Both can probably learn about Cython's cimports. Maybe you can also create a bug report on...

>I wasn't able to find the relevant CI log easily so I'm not sure what's >being debugged/whether that's likely to indicate a bigger Cython bug. There's nothing else in the...

I'll try to get a new release out during the next days, to get things rolling again.

Good call @h-vetinari. We'll definitely continue to use three parts. It should be `3.0.0` then, although both would be [PEP-440](https://www.python.org/dev/peps/pep-0440/) compliant. It's probably not strictly SemVer that we use, just...

@h-vetinari, I think you're right. Most of the truly critical 3.0 issues are solved. What remains with regard to incompatible changes is: https://github.com/cython/cython/issues/4280 https://github.com/cython/cython/issues/2304 [The rest](https://github.com/cython/cython/issues?q=is%3Aopen+is%3Aissue+label%3A%22P%3A+blocker%22) are mostly bugs, which...

> I can't see a PR for #4280? Sorry, I mixed it up with another ticket. #4280 is easy to implement but has a potentially large impact on user code.

The most critical change for this alpha was https://github.com/cython/cython/pull/4606. Now that that's in, I'm mostly looking through PRs that are ready to be included, then it's time for 3.0a11.

3.0.0a11 is released. I could live with starting the beta release phase now. Since this was the first 3.0 release to support the upcoming Py3.11, I postponed a couple of...

There's https://github.com/cython/cython/issues/5088 to help with migration after changing the default exception propagation in #4280. Turns out that migration isn't easy for some code bases, so we'll have to help with...

Copying the PyInstaller+Cython tutorial link from #2147 here for future reference: https://github.com/mobiusklein/cython_pyinstaller_example