We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
the setup.py file currently gets the necessary requirements from requirements.txt as specified here:
amazon-codeguru-profiler-python-agent/setup.py
Line 7 in ea6a2f1
This is not included with the source release in PyPI which makes building from source impossible.
Would it be possible to include that again to be able to build without using the wheel?
I noticed this because I maintain the conda-forge feedstock for this and it was caught in our CI, as can be seen here: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=278441&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d
Edit: This has was caught in the CI but I was able to verify this locally as well.
The text was updated successfully, but these errors were encountered:
Add requirements.txt in PyPI source release
22c6feb
#13
Prepare to release agent version 1.0.3
ad718c5
New release includes change for #13
Released
Sorry, something went wrong.
Thanks
gimki
Successfully merging a pull request may close this issue.
Hi,
the setup.py file currently gets the necessary requirements from requirements.txt as specified here:
amazon-codeguru-profiler-python-agent/setup.py
Line 7 in ea6a2f1
This is not included with the source release in PyPI which makes building from source impossible.
Would it be possible to include that again to be able to build without using the wheel?
I noticed this because I maintain the conda-forge feedstock for this and it was caught in our CI, as can be seen here: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=278441&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d
Edit: This has was caught in the CI but I was able to verify this locally as well.
The text was updated successfully, but these errors were encountered: