Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No wheels for py3.13 which causes failed install in docker. #879

Closed
2 tasks done
dekoza opened this issue Feb 20, 2025 · 2 comments
Closed
2 tasks done

No wheels for py3.13 which causes failed install in docker. #879

dekoza opened this issue Feb 20, 2025 · 2 comments

Comments

@dekoza
Copy link

dekoza commented Feb 20, 2025

  • I am on the latest Pendulum version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • OS version and name: python3.13-slim
  • Pendulum version: 3.0.0

Issue

fix tl;dr - use python3.12 image instead of 3.13 for now

I was wondering why I can do poetry add pendulum in my local env but the docker image fails on poetry install. After I found reports that pointed to either not working patches or resolved issues, I stumbled upon suggestion that the wheels are not there. I downgraded the Python docker image do 3.12 and pendulum installed like a charm. I know I could have added a ton of build tools to compile the version for py313 but that would be not optimal in my workflow.

I also thought that this might be helpful for someone stumbling on this bug in near future.

@potiuk
Copy link

potiuk commented Feb 20, 2025

Yes. I had exactly the same problem yesterday when I attempted first time to migrate Airflow to Python 3.13. It's not a complete blocker - as with pip pendulum can be build an dinstalls, but in order to do so, you need to have rather new cargo installed (I tried with cargo that comes via "apt" with Debian bookworm, but it falis on "unstable let else" and in order to make it builds I had to install latest cargo from Rust pages.

I think it's quite a heavy blocker for Pendulum usage, to require the users who want to install it to have cargo (and generally build-essentials) - as Python 3.13 is becoming mainstream.

Are there any plans for that @sdispater ?

I am asking also because in Airlfow we run "Airflow Beach Cleaning" project when we review all our 700+dependencies with the context of security, maintainability, responsiveness of maintainers - and we also offer help to the maintainers of the projects we depend on in case they need it, or decide to abandon them if they seem not really maintained/secure enough.

Is there anything we can help with @sdispater to make Python 3.13 wheels / new release ? I would love to hear back - we are weeks away from first beta version of Airflow 3 and this is the right time to make decisions on what we do with "somewhat problematic" dependencies.

@raphaelauv
Copy link

an existing issue #844

@ashb ashb closed this as completed Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants