Why is there a strict dependency to Cython 0.29.14 ?

[rmedaer]

The commit 7cb31bc updated the Cython dependency version. It's now required to have cython version strictly equals to 0.29.14

I have 2 questions about this:

• Why did you changed from 0.29 to 0.29.14 ? Is there a feature/fix in .14 which is required for asyncpg ? If yes, which one ?
• Shouldn't it be greater or equals (>=0.29.14) instead of equals (==0.29.14) ?

Maybe a question for @1st1 who did the commit.

Kind regards,

[1st1]

What's the actual problem with pinning Cython? 99.9% of users install wheels so this is irrelevant to them.

[rmedaer]

@1st1 Sorry, I'm not sure to understand your point.

What's the actual problem with pinning Cython?

If there is a fixed version dependency of Cython, I have to install this specific version and I can't even use a later bugfix release. This is annoying. I guess not only for me.

99.9% of users install wheels so this is irrelevant to them.

Could you help me to understand what's the relationship between this assertion and the question(s) of the issue ?

[1st1]

Could you help me to understand what's the relationship between this assertion and the question(s) of the issue ?

The question is how you build asyncpg and why does the way we pin our dependencies matter for your workflow. Typically when you do pip install asyncpg it installs a wheel and it does not matter what Cython you have installed locally. Our Cython dependency is a "dev" dependency, so it should matter to you only if you develop asyncpg itself.

If the reason why you created this issue is that you're trying to develop asyncpg itself, then our recommendation is that you should use virtual environments (python -m venv) and then you wouldn't care about the Cython version.