Allow python_pip builder to install relative packages #153
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Local requirements.txt references are relative to the process's cwd.
This changes the cwd during pip install, so
sam buildprocessesrelative to the location of requirements.txt, in the same way
sam build --use-containerdoes.Semantic differences between the purpose of requirements.txt and
setup.py:
supports additional project features: runtime version restriction,
extra_requires, entrypoints
application's environment
This change provides support for installing packages using setup.py.
If your application is also a package, including "." in your
requirements.txt will defer dependancies resloution to your package's
setup.py.
This change also provides support for local sub-packages. If your
application contains local sub-packages, listing them in the form of
"./" in your requirements.txt will allow you to resolve
and install each package's dependancies.
Fixes #152
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.