Skip to content
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.

python-flask Pipfile not populated with required dependencies after appsody init #748

Open
campnic opened this issue Apr 7, 2020 · 1 comment
Labels
stack/python-flask Issues related to python-flask stack

Comments

@campnic
Copy link

campnic commented Apr 7, 2020

Describe the bug
In order to run resolve the applications dependencies within the development environment, we need the Pipfile in the workspace to be populated with the necessary dependencies after appsody init however, these dependencies are present only within the image.

To Reproduce
Steps to reproduce the behavior:

  1. mkdir my-app
  2. cd my-app
  3. appsody init python-flask
  4. pipenv install

Expected behavior
A python virtual environment to be created with the necessary dependencies

Actual behaviour
A python virtual environment is created, but none of the necessary dependecies are installed. They are not present in the Pipfile. If you deploy to the container, however, you will see:

python -m pip install -r requirements.txt -t /project/deps

The necessary requirements for pip to install the environment are included w/in the image in:
https://github.com/appsody/stacks/blob/master/incubator/python-flask/image/project/Pipfile

Environment Details (please complete the following information):

  • OS: macOSX

If applicable please specify:

  • CLI version: appsody 0.6.0
  • Stack you are using (including the version): python-flask
@neeraj-laad neeraj-laad added the stack/python-flask Issues related to python-flask stack label Apr 14, 2020
@henrynash
Copy link
Contributor

henrynash commented Jul 16, 2020

Could you confirm which version of the python stack you are found this problem in? It may be that this is a consequence of #833, which has now been fixed in python stack 0.2.4.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stack/python-flask Issues related to python-flask stack
Projects
None yet
Development

No branches or pull requests

3 participants