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

Encoding python runtime variant in build string #4252

Open
h-vetinari opened this issue Jul 22, 2021 · 4 comments
Open

Encoding python runtime variant in build string #4252

h-vetinari opened this issue Jul 22, 2021 · 4 comments
Labels
stale::recovered [bot] recovered after being marked as stale stale [bot] marked as stale due to inactivity

Comments

@h-vetinari
Copy link
Contributor

Currently, the default CONDA_PY in the build string resolves to py37 for both cpython & pypy. It would help IMO to see immediately from the artefact name for which python variant a package has been built.

Example for a current numpy build (using pypy37 instead of py37 for the pypy variant)

  • linux-64/numpy-1.21.1-py37h038b26d_0.tar.bz2
  • linux-64/numpy-1.21.1-py37h620df1f_0.tar.bz2 --> linux-64/numpy-1.21.1-pypy37h620df1f_0.tar.bz2

This would also apply if conda-forge ever packages other runtimes, e.g. conda-forge/staged-recipes#13019


Since defaults doesn't distribute pypy, I originally considered this more of a conda-forge problem and had opened conda-forge/conda-forge.github.io#1479, but was then asked to open the issue here.

@h-vetinari
Copy link
Contributor Author

Now that anaconda hired the pyston devs, this is going to become more relevant here as well. :)

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label May 31, 2023
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Jul 1, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 1, 2023
@h-vetinari
Copy link
Contributor Author

Ah damn, missed the initial ping here. Could this be reopened please?

@h-vetinari
Copy link
Contributor Author

@mbargull @kenodegard @jezdez @beeankha could someone reopen this issue please?

@jezdez jezdez reopened this Jul 17, 2023
@jezdez jezdez added stale::recovered [bot] recovered after being marked as stale and removed stale::closed [bot] closed after being marked as stale labels Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale::recovered [bot] recovered after being marked as stale stale [bot] marked as stale due to inactivity
Projects
Status: 🏗️ In Progress
Development

No branches or pull requests

2 participants