vaultvulp/action-pipenv

Use pipenv commands in your GitHub Actions Workflow

Pavel Alimpiev - Python Software Engineer @ Collectly

Python = ❤️, know a little bit about JS and C#.

Contacts:

My personal Telegram channel about investments and finance: @Mindful Investor (Russian)

action-pipenv's Issues

Support actions/setup-python

I am using action-pipenv in conjunction with actions/setup-python, but it seems that the correct python version is not detected. In particular consider the following excerpt of an action workflow file (only responsible parts are indicated):

...
...
    steps:
      - name: Setup python version
        uses: actions/setup-python@v2
        with:
          python-version: '3.7'

    - name: Install dependencies
          uses: VaultVulp/[email protected]
          with:
            command: install -d

using a Pipfile of the form

[requires]
python_version = "3.7"

This generates the error

Run VaultVulp/[email protected]
  with:
    command: install --dev --deploy
  env:
    pythonLocation: /__w/_tool/Python/3.7.12/x64
    LD_LIBRARY_PATH: /__w/_tool/Python/3.7.12/x64/lib
...
...
Warning: Python 3.7 was not found on your system...
Neither 'pyenv' nor 'asdf' could be found to install Python.
You can specify specific versions of Python with:
$ pipenv --python path/to/python

However, if instead I manually install pipenv without making use of action-pipenv, the correct python version is indeed detected.

Could this be because the actions install pipenv by making use of a generic python image (and if so, why not installing pipenv making use of the available python versions already installed on the instances)?

Supporting Python Image Versions Beyond Latest?

Hello,

It looks like 2 days ago the base python3 image was changed to be associated with python3.9 on docker hub. I'm curious if whether it is possible to pass an argument from a Github action yaml to this action rather than forcing Pipfiles that use this action to specify python3.9.

Thanks in advance for any thoughts you have!

Broken builds

Seems like the dockerfile isnt too specific with the base python image.

Seems like the default 3 container was recently bumped to 3.11.x
https://hub.docker.com/layers/library/python/3/images/sha256-35483f08b07e42d712ba92576c0d09e7a077d33677855d3276190b65dc4aec30?context=explore

https://github.com/docker-library/python/blob/5d908b0477c003712550c84ac4d133367b912f78/3.11/bookworm/Dockerfile

Which broke my build that relies on 3.9

https://github.com/daxaxelrod/open_insure/actions/runs/5367821262/jobs/9738271071