If we replace the official CPU build, won't there still be new dependencies
so it is not even guaranteed to work depending on whether the user has the
dependencies (e.g. libgfortran) installed? I think there is also a
performance degradation if we remove mkl.
But, we could still have a
On Tue, May 12, 2020 at 12:08 PM Lausen, Leonard
wrote:
> On Mon, 2020-05-11 at 13:56 -0400, Carin Meier wrote:
> > Does removing the jars from both of these solutions also remove them from
> > maven central?
>
> Does Maven Central automatically mirror jars from repository.apache.org?
> Or were
It is going to be closer to a complete rewrite. On the other hand, making a new
Scala API would be imperative instead of symbolic and I think there are going
to be a lot of operator changes to better match numpy in 2.0. I don't think the
migration costs for a Scala 2.0 would be that much less
@gigasquid Yeah, you can view the download statistics from
https://repository.apache.org/#central-stat.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-595522607
I just saw this email on the incubator general mailing list. MXNet is
missing an apache download page. Is anyone interested in adding one?
Zach
-- Forwarded message -
From: Justin Mclean
Date: Tue, Mar 3, 2020 at 5:44 PM
Subject: [MENTORS] Podlings with releases but no download
Is there a plan to create a branch either for the 1.x version and have master
reflect 2.0 or to create a branch for the 2.0 version and keep master on 1.x
for now?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
We had a discussion a while back about trying to improve the way we handle
issues by assigning them to users who are working on them. However, the
discussion ended because issues could only be assigned to those with write
access (committers).
I just came across a new Github feature where issues
I would like to raise another option to get back on the topic of changing
the Operator graph structure. On the page discussing Relay IR [1], it
discusses mainly the difference between a data flow graph like we use now
and A-normal [2] which is used in some functional compilers. Is there a
reason
; I think our installation instructions and tutorials can be updated
> to
> > > > > default to Python3 and we should update Python2-only tutorials. I
> > know
> > > > > we have a handful of those, and when I spot them, I'll create an
> > > > > issue.
> &
Right now, the official date for ending support for Python 2.7 (and all of
python2) is set to January 1 [1]. As part of it, a number of projects have
pledged to drop support for Python2 in or before 2020 including Tensorflow,
requests, pandas, ipython, numpy, pillow, and Cython [2]. I believe we
As part of the current MXNet release process, the R-package is removed from
the source release [1]. If we are advertising that MXNet has an R package
as an Apache project, it really should be part of the official Apache
release process. I know there were a few missing license headers within the
Hi,
A little over a month ago, we announced the nightly build of the Scala
package on Nexus [1]. It featured the same statically linked binary build
logic used by the Python pip to make the adoption as easy for our JVM users
as for our python users. However, that release occurred on a private
There should not be a problem including MKLML since the above (BSD
3-clause) is Category A under apache (
https://www.apache.org/legal/resolved.html#what-can-we-include-in-an-asf-project-category-a
).
However, what I noticed from some other apache projects is they created
additional LICENSE files
I would like to raise a PR for discussion here. In the mxnet installation
docs, we currently have three inconsistent ways of compiling the mxnet
backend:
1. Use make by passing in the configuration directly
make USE_BLAS=openblas
2. Use make with config.mk
echo "USE_BLAS=openblas" >>
14 matches
Mail list logo
