-
Notifications
You must be signed in to change notification settings - Fork 293
Description
When using package individually, the requirements are not pulled from a Pipfile/peotry file if present, only requirements.txt
(this is a completely different behaviour than when not using package individually as at the root of the project on can use Pipfile/poetry)
If there is a Pipfile/poetry file at the root when using package individually the root level requirements are only packaged not the root+function or just function requirements.
I would like to continue to use Pipfile at the root level as this contains development packages for pytest and other frameworks. I would then like to include a Pipfile in each function that needs to be package with that function's requirements. Currently if serverless-python-requirements detects a Pipfile at the root all other function requirements are ignored.
Activity
antoinechamot commentedon Apr 8, 2021
same here with:
package:
individually: true
if i have a Pipfile in my module it is just ignored
[-]individual requirements allow pipenv/peotry for functions[/-][+]Individual requirements should allow pipenv/poetry for functions[/+]bsamuel-ui commentedon Apr 11, 2021
What would you expect the layout to look like? For instance:
michael-c-hoffman commentedon Jul 23, 2021
yes, that would be the expected layout
gerbenoostra commentedon Nov 25, 2021
I also expected to have pyproject.toml & requirements.txt to behave similar: if there's a pyproject.toml in the module directory, it would be used as preprocessing step to create the requirements.txt in the module dir.
However, only a pyproject.toml in the root folder results in creating a requirements.txt (in the root folder)
poetry
#682