Hey all,
Just a quick reminder that we're gonna have the follow-up call tomorrow
(Tuesday) 5pm UTC, 9am PST, noon EST, 1am Wednesday Singapore. (About 23hrs
from this email) so the folks in europe can make the call too.
It'll be a hangouts call same as before and we'll put the link and dial-in
numb
Thanks everyone for attending the meeting! It was great to have people
from so many different groups so we can figure out how to solve this
best for everyone. :)
A lot was discussed, I split the notes from the wheel part of the
discussion out into a separate doc:
https://docs.google.com/document/d
t allow a good dependency resolution, also with taking
>> > CUDA into account, a dependency resolution that differs between
>> > source and binary builds of a package. For this case, exactly
>> > conda was developed because it was considered out-of-scope for
>
hether we actually can fit all the
>>> requirements of the packages that take part in this mail thread into pip
>>> without simply reimplementing conda inside of pip.
>>
>>
>> One question is probably: what would that entail, and why would it be bad? :)
>>
be able to join the meeting as it's at midnight CEST
> - looking forward to the conclusions from the meeting!
>
> On Mon, Feb 4, 2019 at 6:00 AM Jason Zaman wrote:
>>
>> Hey all,
>>
>> We're having the TensorFlow SIG-Build meeting on 5th Feb 3pm PST
>&g
Hey all,
We're having the TensorFlow SIG-Build meeting on 5th Feb 3pm PST
(https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190205T15&p1=224).
Agenda is linked from:
https://groups.google.com/a/tensorflow.org/forum/#!topic/build/akyPcGoBIy4
I'd like to invite everyone from this thread
