Older version of pip used during staging?

snapcraft
1

Hi Folks,

Trying to snap my project up and I noticed a funny thing.

I get the following console output

Staging python-stuff 
Cleaning later steps and re-pulling incuvers-app ('python-stuff' changed)
Cleaning later steps and re-pulling requirements ('python-stuff' changed)
WARNING: You are using pip version 19.3.1; however, version 20.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
WARNING: You are using pip version 19.3.1; however, version 20.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Yet at the beggining it shows this

Processing /root/parts/python-stuff/python-packages/pip-20.0.1-py2.py3-none-any.whl

Saved /tmp/tmp9ah6dr0o/pip-20.0.1-py2.py3-none-any.whl

How can I get pip to stay at version 20 during the staging?

2

I’m having a related problem, whereby I’d like to use a slightly older version of pip (20.0.2) in the snap itself, but despite many ways of trying to pin the pip version, the snapped app ends up with the newest version (20.1). An example of one of the many yaml configs I’ve tried:

parts:                                                                          
  my-part-1:                                                         
    plugin: python                                                              
    python-version: python3                                                     
    python-packages:
      - pip==20.0.2
  my-part-2:                                                               
    plugin: nil                                                                 
    build-packages:                                                             
      - python3-pip 
    install: |
      python -m pip install --upgrade pip==20.0.2
      ...