Request access for sympy and python-flint

[oscarbenjamin]

CC @asmeurer @agriyakhetarpal

Following discussions at sympy/sympy#27183 (comment) I am wondering if it would be possible to begin uploading nightly wheels for SymPy and python-flint.

SymPy is not hard to build but it now makes use of python-flint as an optional dependency (and will do so more extensively in future - conda-forge/sympy-feedstock#57) and python-flint is a lot more difficult to build. Without python-flint it is still useful for downstream projects to be able to test nightly builds of SymPy plus other dependencies like NumPy etc all installed from the same index.

I have just made an Anaconda account:
https://anaconda.org/oscarbenjamin

I assume that this is Aaron's Anaconda account:
https://anaconda.org/asmeurer

[tupui]

Hi 👋 I am voting +1 😃

[asmeurer]

I agree we should do this.

Im confused about the Anaconda.org accounts, though. Do they come into play here?

[tupui]

What do you mean exactly?

Scientific Python has an Anaconda account yes. They support us by providing us a bit more storage than a normal account. There is nothing more besides that.

[oscarbenjamin]

I'm not sure I fully understand how all this works but let me try to explain:

Uploads to the Anaconda scientific-python nightly index are authenticated by a secret associated with an Anaconda account. This issue is to request that our Anaconda accounts have the permission to upload these wheels. Then we can generate secrets and add them to SymPy's GitHub and use those in CI to upload the wheels.

https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects

[tupui]

That's correct 👍 And the first step is this issue where some admins vote to say if we think we should add your wheels or not to this org. The Scientific Python org (scientific-python-nightly-wheels: https://anaconda.org/scientific-python-nightly-wheels) is an org on Anaconda, not on conda-forge, in case that could also be a confusion. https://anaconda.org/scientific-python-nightly-wheels.

[matthewfeickert]

I'm also +1 and this seems like an easy enough approve that we can move forward:

Steps to gain upload access to https://anaconda.org/scientific-python-nightly-wheels/

• Create an account on Anaconda Cloud
• Reply here with the link to your account (https://anaconda.org/oscarbenjamin, https://anaconda.org/asmeurer)
• Make a new Anaconda Cloud API token with permissions described in https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects

• Save the API token as a repo GitHub Actions secret named ANACONDA_ORG_UPLOAD_TOKEN
• Direct me (@matthewfeickert) to a sympy nightly wheel for me to upload to create the package in the registry
• Direct me (@matthewfeickert) to a python-flint nightly wheel for me to upload to create the package in the registry
• Verify that I have added you to the sympy team "Group" on https://anaconda.org/scientific-python-nightly-wheels
• Verify that I have added you to the python-flint team "Group" on https://anaconda.org/scientific-python-nightly-wheels
• Verify that I have added the package scientific-python-nightly-wheels/sympy to the sympy team "Group"
• Verify that I have added the package scientific-python-nightly-wheels/python-flint to the python-flint team "Group"

If you'd also like to use the scientific/upload-nightly-action GitHub Action please check out the action repo's README. If you need to collect wheels from different CI jobs, consider creating a new GitHub Actions workflow with logic similar to matplotlib's or Awkward's.

[asmeurer]

@oscarbenjamin mentioned that my anaconda.org account is anaconda.org/asmeurer (this is correct). But does this actually matter for this?

[tupui]

It does, see the message from @matthewfeickert. We need to create a team and put at least 2 people in it so that you can upload wheels. You have to create personal tokens and use them to upload wheels. These tokens only give you the ability to upload wheels to your own projects.

[agriyakhetarpal]

If it helps, I'll be happy to set up the CI job to upload wheels for the SymPy community within my PR (sympy/sympy#27183) itself, as linked above in the PR description.

[oscarbenjamin]

my anaconda.org account is anaconda.org/asmeurer (this is correct). But does this actually matter for this?

I have just created a token under my Anaconda account as described above and added it to the SymPy GitHub repo. I don't think you need to do that as well. The token has an expiry date of 1 year though. After that time the token would need updating and it is better if more than one person can do that. I should have discussed this with you before but for SymPy if we need two names for this then you and me are the obvious choices.

[oscarbenjamin]

• Direct me (@matthewfeickert) to a sympy nightly wheel for me to upload to create the package in the registry
• Direct me (@matthewfeickert) to a python-flint nightly wheel for me to upload to create the package in the registry

Can we just use any of the wheels from the most recent releases for now?

https://pypi.org/project/python-flint/#files
https://pypi.org/project/sympy/#files

Otherwise for SymPy I could build a wheel and put it somewhere. For python-flint the wheels from the most recent build are available as artifacts in CI:
https://github.com/flintlib/python-flint/actions/runs/11184443410

[oscarbenjamin]

Otherwise for SymPy I could build a wheel and put it somewhere.

Here is a SymPy wheel (I had to add the .zip extension for GitHub to allow upload):

sympy-1.14.dev0-py3-none-any.whl.zip