Assertion Error have_directory_for_build

[vinayan3]

Environment

• pip version: 19.01
• Python version: 3.6.7
• OS: alpine:3:6
  https://github.com/gliderlabs/docker-alpine/blob/f57570e8dafadf7ab0116548bfdcc6a9b7ffc25a/versions/library-3.6/x86_64/Dockerfile

Description

In my docker build I upgrade pip to the 19.01 and now I'm getting an Assertion Error related to having a directory for build. I'm providing a docker file which will make it very easy to reproduce the error. Furthermore, if you run a terminal within the container you can try the failing install command by hand.

Expected behavior
It should install.
How to Reproduce

You can run this docker file and you should see the error.

FROM alpine:3.6

ARG BUILD_DEPS=".build-deps"
ENV PYTHONUNBUFFERED 1
RUN apk add --no-cache --update python3 \
    && apk add --no-cache --update --virtual ${BUILD_DEPS} \
        build-base \
        musl-dev \
        libffi-dev \
        python3-dev \
        openssl-dev \
    && python3 -m ensurepip \
    && rm -r /usr/lib/python*/ensurepip \
    && pip3 --no-cache-dir install --upgrade pip setuptools

RUN pip3 --no-cache-dir install moto[server] \
    && find /usr/local \
            \( -type d -a -name test -o -name tests \) \
            -o \( -type f -a -name '*.pyc' -o -name '*.pyo' \) \
            -exec rm -rf '{}' + \
    && runDeps="$( \
        scanelf --needed --nobanner --recursive /usr/local \
                | awk '{ gsub(/,/, "\nso:", $2); print "so:" $2 }' \
                | sort -u \
                | xargs -r apk info --installed \
                | sort -u \
    )" \
    && apk add --virtual .rundeps $runDeps \
    && apk del ${BUILD_DEPS}


ENTRYPOINT /usr/bin/moto_server s3 -H 0.0.0.0

EXPOSE 5000

Output

Installing collected packages: pip, setuptools
  Found existing installation: pip 9.0.3
    Uninstalling pip-9.0.3:
      Successfully uninstalled pip-9.0.3
  Found existing installation: setuptools 39.0.1
    Uninstalling setuptools-39.0.1:
      Successfully uninstalled setuptools-39.0.1
Successfully installed pip-19.0.1 setuptools-40.6.3
Collecting moto[server]
  Downloading https://files.pythonhosted.org/packages/57/40/cec89fa5c13108eb1c8de435633f8b7639e0e43fcbcdc8ac52633efeeabe/moto-1.3.7-py2.py3-none-any.whl (552kB)
Collecting pytz (from moto[server])
  Downloading https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3-none-any.whl (510kB)
Collecting Jinja2>=2.7.3 (from moto[server])
  Downloading https://files.pythonhosted.org/packages/7f/ff/ae64bacdfc95f27a016a7bed8e8686763ba4d277a78ca76f32659220a731/Jinja2-2.10-py2.py3-none-any.whl (126kB)
Collecting cryptography>=2.3.0 (from moto[server])
  Downloading https://files.pythonhosted.org/packages/69/ed/5e97b7f54237a9e4e6291b6e52173372b7fa45ca730d36ea90b790c0059a/cryptography-2.5.tar.gz (487kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
    Preparing wheel metadata: started
    Preparing wheel metadata: finished with status 'done'
Collecting botocore>=1.12.13 (from moto[server])
[ Tons of log output]
[ . . . ] 
Collecting pycparser (from cffi!=1.11.3,>=1.8->cryptography>=2.3.0->moto[server])
  Downloading https://files.pythonhosted.org/packages/68/9e/49196946aee219aead1290e00d1e7fdeab8567783e83e1b9ab5585e6206a/pycparser-2.19.tar.gz (158kB)
Exception:
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/pip/_internal/cli/base_command.py", line 176, in main
    status = self.run(options, args)
  File "/usr/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 346, in run
    session=session, autobuilding=True
  File "/usr/lib/python3.6/site-packages/pip/_internal/wheel.py", line 886, in build
    assert have_directory_for_build
AssertionError

[cjerdonek]

Closing as this is a duplicate of #6158 #6197.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.