Re: TensorFlow, PyTorch, and manylinux1

2019-02-04 Thread soumith
PA is 100% reliable", we would've been in a better state. Until then, I think it's best that we find a solution for PyPI users that can work out of box with PyPI. On Mon, Feb 4, 2019 at 12:52 PM Antoine Pitrou wrote: > On Tue, 5 Feb 2019 01:45:34 +0800 > Jason Za

Re: TensorFlow, PyTorch, and manylinux1

2019-02-04 Thread soumith
Unfortunately I'll be on a long flight, and cannot make it to the SIGBuild meeting. I'm definitely interested in the meeting notes and any follow-up meeting. > I think we should leave CUDA out of the discussion initially and see if we can get the cpu-only wheel working correctly. Hopefully cpu-onl

Re: TensorFlow, PyTorch, and manylinux1

2018-12-17 Thread soumith
hlan and Nathaniel Smith, but we never got > far. > > I'm a little late to the party, but basically, what Soumith said. We have > the exact same constraints (C++-11, CUDA/cuDNN). These would be extremely > common for any computation-heavy packages, and properly solving this issue >

Re: TensorFlow, PyTorch, and manylinux1

2018-12-17 Thread soumith
ns already exist. > > Thanks, > > Travis > > > On Mon, Dec 17, 2018, 12:32 AM soumith > > I'm reposting my original reply below the current reply (below a dotted > > line). It was filtered out because I wasn't subscribed to the relevant > > mailing lis

Re: TensorFlow, PyTorch, and manylinux1

2018-12-16 Thread soumith
ed to use > > > nvidia-docker to build GPU binaries [10]. This causes various levels of > > > pain for the rest of the Python community, see for example [1] [2] [3] > [4] > > > [5] [6] [7] [8]. > > > > > > The purpose of the e-mail is to get a discus