jameslamb opened a new issue, #47381:
URL: https://github.com/apache/arrow/issues/47381

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   I'm a maintainer of a project called LightGBM that depends on `pyarrow`. For 
a while now, we've been testing against `pyarrow` nightlies from 
https://pypi.anaconda.org/scientific-python-nightly-wheels/simple/pyarrow/ to 
ensure that we get early warning of breaking changes (and so we can possibly 
catch and report bugs in release candidates).
   
   The CI job we use for that started failing recently, like this:
   
   > ERROR: Could not find a version that satisfies the requirement 
pyarrow>=22.0.0.dev0 (from versions: 0.9.0, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 
0.12.1, 0.13.0, 0.14.0, 0.15.1, 0.16.0, 0.17.0, 0.17.1, 1.0.0, 1.0.1, 2.0.0, 
3.0.0, 4.0.0, 4.0.1, 5.0.0, 6.0.0, 6.0.1, 7.0.0, 8.0.0, 9.0.0, 10.0.0, 10.0.1, 
11.0.0, 12.0.0, 12.0.1, 13.0.0, 14.0.0, 14.0.1, 14.0.2, 15.0.0, 15.0.1, 15.0.2, 
16.0.0, 16.1.0, 17.0.0, 18.0.0, 18.1.0, 19.0.0, 19.0.1, 20.0.0, 21.0.0)
   > ERROR: No matching distribution found for pyarrow>=22.0.0.dev0
   
   It looks like the there are `*-cp313-cp313t-manylinux_2_28` wheels at 
https://pypi.anaconda.org/scientific-python-nightly-wheels/simple/pyarrow/, but 
not any non-free-threaded manylinux wheels.
   
   Is this intentional? Or just a temporary disruption in publishing?
   
   I did see https://github.com/apache/arrow/issues/47308 which points to 
https://github.com/ursacomputing/crossbow/actions/runs/16745071346/job/47401564422
 for Windows but I can't quite figure out where Linux nightly wheels are built 
and published from.
   
   Thanks for your time and consideration.
   
   ### Component(s)
   
   Python


-- 
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]

Reply via email to