| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
In order to build Python3.7 packages for manylinux1
platform, we need our Docker image to include
Python3.7. Unfortunately, since Python 3.7 is still
in RC1 stage, the official docker image does not
include that Python release, so we temporarily
rely on our own underlying docker image to build.
|
| |
|
|
|
|
|
| |
89ce16b removed a few package installations from the dockerfiles for
building python artifacts. Revert them.
Revert certain package install removal from python artifact dockerfiles
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Due to a recent change (Feb 2018) in Github's policy to discontinue
support for weak cryptographic standards, older git versions stopped
working with Github repositories. The Dockerfiles for building python
artifacts currently uses git 2.0.5, that fails with an error `tlsv1
alert protocol version`.
The CentOS image by the latest source Dockerfile, `manylinux` comes
with the latest version of git as well, removing the need to manually
build git from source.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Before, namespace packages would break in auditwheel due to a
superfluous check (fixed in the commit referenced in the Dockerfiles).
Now, the auditwheel used in the manylinux1-support Docker images can
handle namespace packages, and we may thus use them. This should
alleviate future user pain w.r.t. installation of grpcio-tools causing
loss of grpcio files and vice versa (e.g. requiring a reinstall of
grpcio following installation of grpcio-tools).
|
| |
|
Mehrdad Afshari
Naresh
Matt Kwong
Jan Tattermusch
Ken Payson
Masood Malekghassemi