pip-tools is not pinned in requirements.in, and pip-tools==6.2.0 breaks zappa update

Context

• setup.py references requirements.in: https://github.com/zappa/Zappa/blob/master/setup.py#L10
• requirements.in does not pin pip-tools https://github.com/zappa/Zappa/blob/master/requirements.in#L22
• pip-tools released 6.2.0 3 days ago, which added setuptools to setup.cfg https://github.com/jazzband/pip-tools/releases/tag/6.2.0
• pip install zappa installs pip-tools 6.2.0
• Zappa explicitly adds setuptools to its dependencies in create_handler_venv https://github.com/zappa/Zappa/blob/master/zappa/core.py#L495
• Doing a zappa update {env} results in the error:

Double requirement given: setuptools (already in setuptools==47.1.0, name='setuptools')
...
...
web/venv/lib/python3.7/site-packages/zappa/core.py", line 440, in create_handler_venv
    raise EnvironmentError("Pypi lookup failed")
OSError: Pypi lookup failed

Expected Behavior

zappa update should work

Actual Behavior

zappa update does not work

Possible Fix

Options include:

• pin deps in requirements.in,
• reference requirements.txt in setup.py
• remove manual injection of setuptools

Steps to Reproduce

Your Environment

• Zappa version used: 0.52.0
• Operating System and Python version:
• The output of pip freeze:
• Link to your project (optional):
• Your zappa_settings.json:

[evelyn-f-king]

I am still experiencing this problem. Not clear on what the fix is, anyone able to offer a clearer solution? I tried pinning pip-tools to 6.1.0 as some other places suggested and it didn’t work.

[JacobDel]

@Joshuamjv2 No, I reduced the project size so that I could avoid that type of build. It only occurs when you add slim_handler