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

GH-45288: [Python][Packaging][Docs] Update documentation for PyArrow nightly wheels #45289

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

amoeba
Copy link
Member

@amoeba amoeba commented Jan 16, 2025

Rationale for this change

We now upload nightly PyArrow wheels to https://anaconda.org/scientific-python-nightly-wheels/pyarrow so we should document it. In addition, the current documentation incorrectly points to the arrow-nightlies channel which AFAICT is no longer used and also points to Gemfury which we'd like to stop using.

What changes are included in this PR?

Updates the relevant section in the docs with instructions on how to use the scientific-python-nightly-wheels repository.

Are these changes tested?

I've tested installing a wheel from https://anaconda.org/scientific-python-nightly-wheels/pyarrow.

Are there any user-facing changes?

Updated docs.

@github-actions github-actions bot added the awaiting review Awaiting review label Jan 16, 2025

This comment was marked as outdated.

@amoeba amoeba changed the title 45288: [Python][Packaging][Docs] Update documentation for PyArrow nightly wheels GH-45288: [Python][Packaging][Docs] Update documentation for PyArrow nightly wheels Jan 16, 2025
@amoeba
Copy link
Member Author

amoeba commented Jan 16, 2025

@github-actions crossbow submit preview-docs

Copy link

⚠️ GitHub issue #45288 has been automatically assigned in GitHub to PR creator.

Copy link

Revision: 886cdea

Submitted crossbow builds: ursacomputing/crossbow @ actions-9eba8d2216

Task Status
preview-docs GitHub Actions

Copy link
Member

@raulcd raulcd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I tested successfully the links and commands

@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting review Awaiting review labels Jan 17, 2025
@raulcd raulcd merged commit c9f417f into apache:main Jan 17, 2025
8 of 9 checks passed
@raulcd raulcd removed the awaiting merge Awaiting merge label Jan 17, 2025
Comment on lines +739 to +741
pip install \
-i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple \
pyarrow
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't need the --pre to get it actually from the nightly index?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't seem to be required:

$ pip install -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple pyarrow
Looking in indexes: https://pypi.anaconda.org/scientific-python-nightly-wheels/simple
Collecting pyarrow
  Downloading https://pypi.anaconda.org/scientific-python-nightly-wheels/simple/pyarrow/20.0.0.dev4/pyarrow-20.0.0.dev4-cp312-cp312-manylinux_2_28_x86_64.whl (42.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 42.2/42.2 MB 13.2 MB/s eta 0:00:00
Installing collected packages: pyarrow
Successfully installed pyarrow-20.0.0.dev4

@github-actions github-actions bot added the awaiting changes Awaiting changes label Jan 17, 2025
Copy link

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit c9f417f.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 7 possible false positives for unstable benchmarks that are known to sometimes produce them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting changes Awaiting changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants