Hey Sergio, I think it's mostly to keep the Dockerfile size down by
matching the system python package. Of course people can extend the image
and use python 3.6 / 3.7. I think we should follow this up with an update
to the new Ubuntu LTS version as a base docker image at which point it
would use
Python 2.7 reaches End of Life by the end on 2019.Take that into account.
About Python 3.x, why not having 3.6 docker images? I know 3.7 is not yet
supposed by MXNet. But starting with 3 5 doesn't make much sense for me
On Wed, Oct 17, 2018, 11:52 Meghna Baijal
wrote:
> Hi All,
>
> I am current
Thank you Kellen and Steffen for your comments.
I will wait for some more time in case anyone has a different opinion, else
go ahead with the above recommendation.
Meghna
On Wed, Oct 17, 2018 at 10:18 PM Steffen Rochel
wrote:
> +1 on Kellen’s comments and suggestion.
> On Wed, Oct 17, 2018 at
+1 on Kellen’s comments and suggestion.
On Wed, Oct 17, 2018 at 12:39 PM kellen sunderland <
kellen.sunderl...@gmail.com> wrote:
> This feels like something we should get a little data on before making a
> decision, but I also don't have a strong opinion. I would bias towards
> pushing something
This feels like something we should get a little data on before making a
decision, but I also don't have a strong opinion. I would bias towards
pushing something that might be imperfect and moving on to develop other
improvements for users rather than determining a 'perfect' solution.
The questio
Hi All,
I am currently in the process of updating the python docker images for
Apache MXNet such that they are built on top of the pip binaries.
Until now these were built to use python 2.7 but with an upcoming PR I am
also adding python 3.5 docker images. I would like to know the community’s
pref
