Closed anscfrisson closed 4 months ago
@anscfrisson 0.6.0.dev client packages are not published to pyansys/pypi, that is why you are not able to install latest pyprimemesh dev client when you set PIP_INDEX_URL to pyansys/pypi.
cc @prajaktmahajan @waltersma
@anscfrisson - this is related to the Private PyPI configuration. Could you give it a try again?
I just did some modifications to enable ansys-meshing-prime and ansys-api-meshing-prime upstream versions (i.e. from public PyPI)
@RobPasMue Thanks for the updates! I can confirm via CI checks in a private repository that the ansys private pypi works as pip index (using environment variable PIP_INDEX_URL
instead of PIP_EXTRA_INDEX_URL
) to relay pyprimemesh packages. Closing issue.
π Before submitting the issue
π Description of the bug
From: https://dev.docs.pyansys.com/how-to/releasing.html#artifact-download
If I define environment variables in github actions:
PIP_EXTRA_INDEX_URL: "https://${{ secrets.PYANSYS_PRIVATE_PYPI_PAT }}@pkgs.dev.azure.com/pyansys/_packaging/pyansys/pypi/simple"
:ansys-meshing-prime
can be retrievedPIP_INDEX_URL: "https://${{ secrets.PYANSYS_PRIVATE_PYPI_PAT }}@pkgs.dev.azure.com/pyansys/_packaging/pyansys/pypi/simple"
: fails with:(
***
internal project)Are ansys-meshing-prime versions > 0.3.0.dev0 not relayed by the Ansys Private Pypi?
π Steps to reproduce
Request the value of the
PYANSYS_PYPI_PRIVATE_READ_PAT
token by sending an email to the pyansys.core@ansys.com email.Works
Fails
π» Which operating system are you using?
Windows
π Which ANSYS version are you using?
242
π Which Python version are you using?
3.10
π¦ Installed packages