potiuk commented on PR #1268:
URL: 
https://github.com/apache/cassandra-python-driver/pull/1268#issuecomment-3873486622

   > I've confirmed that package installs are only failing on Python 3.14. The 
following sequence works without issue on everything exception that version:
   
   Yeah. It's not a **huge** problem - in our case it also failed for 3.13 when 
we installed 3.29.1  - see for example 
https://github.com/apache/airflow/actions/runs/21804090800/job/62904899230#step:8:1365
  - mostly because there were no 3.13 wheels in this version (and it did not 
support it "officially" - yet we we have >=3.29.1 as minimum specified as 
airlfow dependencies. 
   
   The test where it failed was the "lowest dependency" test - so the test when 
we attempt to bring all dependencies to their minimum specified versions and we 
want to check that our tests are still passing with them. So even if 3.29.1 did 
not support 3.13 officially, we got it working there because we built it from 
sdist and ... it worked.
   
   I guess other people might have similar issues when they are installing 
older versions.
   
   Sadly - indeed - there is not much you can do for already released versions. 
 They are immutable and they are what they are -  and if people  will want to 
use sdist to build "unsupported" version for 3.13 with sdist - they are able to 
do it and it will work as long as they apply workarounds.
   
   So, this is true that there is no urgency here, some CI failures will happen 
in edge cases here, most installations will work with binary wheels and there 
is already a workaround - especially if you use modern tool versions - like 
25.3+ of `pip` that supports --build-constraints, people can specify 
constraints to not install newer setuptools version.
   
   It would however be great to get it fixed for the next release :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to