Outdated pip is causing builds with namespace packages to fail

[theacodes]

• Read the Docs project URL: https://google-cloud-python.readthedocs.io
• Build URL (if applicable):

Recent failures:

• https://readthedocs.org/projects/google-cloud-python/builds/7229979/
• https://readthedocs.org/projects/google-cloud-python/builds/7225937/
• https://readthedocs.org/projects/google-cloud-python/builds/7225738/

Last successful build:
https://readthedocs.org/projects/google-cloud-python/builds/7225188/

It seems that this is due to pypa/setuptools#885, which indicates that pip and setuptools need to be updated in the baseline environment.

[theacodes]

Also, this appears to be deterministic. Some of our builds pass, like this most recent one: https://readthedocs.org/projects/google-cloud-python/builds/7230426/

[stsewd]

The pip message is just a warning, so it shouldn't be the cause of the failure. I'm not sure why is this happening, I'll try to see if I can reproduce this on my local instance. Let us know if the build keeps failing.

[theacodes]

The most recent few have failed. Here's one: https://readthedocs.org/projects/google-cloud-python/builds/7230941/

[theacodes]

Seems like our recently builds today have consistently failed due to this: https://readthedocs.org/projects/google-cloud-python/builds/

Is there anything we can do to help? I'm happy to make the change to update pip/setuptools, I just don't know where to do it.

[stsewd]

Maybe you can try wiping the environment, you can do this in the Versions section then Edit button.

What I can see is that the pip version comes from the docker image https://github.com/rtfd/readthedocs-docker-images/blob/9b0816d1b610373036ce16eb3653c99ca30e4207/Dockerfile#L92

So, the team needs to rebuild the image to get the latest versions, I think we should support upgrade pip before installing deps. I'm going to ask to the team.

[theacodes]

Thanks, @stsewd! Clearing the environment seems to have helped.

Since we're using 'latest', it seems you'd need to rebuild the 3.x docker image from here.

[tswast]

Adding pip_install: true to the config in pandas-gbq seemed to be the right fix for a similar error. googleapis/python-bigquery-pandas@ee9955f

[stsewd]

Probably we can close this in favor of #4823

[stsewd]

Closing in favor of #4823, but let me know if there are any other problems!