Open kloczek opened 1 month ago
There doesn't seem to be any interesting changes that might cause this https://github.com/aio-libs/yarl/compare/v1.12.0...v1.13.1
I wonder if a build dep has changed
Linux x86/64
This is not helpful. It clearly works in our CI under this platform. Something changed in your environment, maybe setuptools or Cython. Debug that, please. Until then, there's nothing actionable for us. We have to be able to validate this in our CI.
Did you chr=ech versions of cython and setuptools which are used by your CI and me?
That's your responsibility. We have no way of knowing what you got.
Please confirm the following
[X] I agree to follow the aio-libs Code of Conduct
[X] I have checked the current issues for duplicates.
[X] I understand this is open source software provided for free and that I might not receive a timely response.
[X] I am positive I am NOT reporting a (potential) security vulnerability, to the best of my knowledge. (These must be shared by submitting this report form instead, if any hesitation exists.)
[ ] I am willing to submit a pull request with reporoducers as xfailing test cases or even entire fix. (Assign this issue to me.)
Describe the bug
After
yarl
1.12.1 I cannot build correctly module because pep517 based build looks like is not buildingyarl._quoting_c
DSO module and looking on the output cannot find any cause of that. Result is that pytest fails because it cannot findyarl._quoting_c
module. May I ask for any hint about possible cause? 🤔To Reproduce
Just run
pip
orbuild
to perform pep517 based build. I\m using/usr/bin/python3 -sBm build -w --no-isolation --config-setting=pure-python=false --config-setting=with-cython-tracing=true
command.Expected behavior
As long as is used
--config-setting=pure-python=false
my understanding is that it should be build loadable DSO module.Logs/tracebacks
Python Version
multidict Version
yarl Version
OS
Linux x86/64
Additional context
No response