On Fri, Jan 15, 2016 at 11:56 AM, Travis Oliphant wrote:
>
[...]
> I still submit that this is not the best use of time. Conda *already*
> solves the problem.My sadness is that people keep working to create an
> ultimately inferior solution rather than just help make a better solution
> mor
> On Jan 15, 2016, at 21:22, Chris Barker wrote:
>
> Indeed, it's not uncommon for folks on the distutils list to say "go use
> conda" in response to issues that pip does not address well.
I was in the room at the very first proto-PyData conference when Guido told the
assembled crowd "if p
On Fri, Jan 15, 2016 at 2:38 PM, Matthew Brett
wrote:
>
> I think there's a distinction between 'promote numpy as wheels' and
> 'make numpy available as a wheel'. I don't think you'll see much
> evidence of "promotion" here - it's not really the open-source way.
>
Depends on how you define "pro
hmm -- didn't mean to rev this up quite so much -- sorry!
But it's a good conversation to have, so...
On Fri, Jan 15, 2016 at 1:08 PM, Benjamin Root wrote:
> That being said... I take exception to your assertion that anaconda is
> *the* solution to the packaging problem.
>
I think we need to
On Fri, Jan 15, 2016 at 2:33 PM, Steve Waterbury
wrote:
> On 01/15/2016 05:19 PM, Matthew Brett wrote:
>>
>> On Fri, Jan 15, 2016 at 2:15 PM, Steve Waterbury
>> wrote:
>>>
>>> On 01/15/2016 05:07 PM, Matthew Brett wrote:
>
>
> I attribute
> some of the conda-ignoring to "NIH" and,
On Fri, Jan 15, 2016 at 9:56 PM, Steve Waterbury
wrote:
> On 01/15/2016 04:08 PM, Benjamin Root wrote:
>
>> So, again, I love conda for what it can do when it works well. I only
>> take exception to the notion that it can address *all* problems, because
>> there are some problems that it just sim
On 01/15/2016 05:19 PM, Matthew Brett wrote:
On Fri, Jan 15, 2016 at 2:15 PM, Steve Waterbury
wrote:
On 01/15/2016 05:07 PM, Matthew Brett wrote:
I attribute
some of the conda-ignoring to "NIH" and, to some extent,
possibly defensiveness (I would be defensive too if I had been
working on pip
On Fri, Jan 15, 2016 at 2:15 PM, Steve Waterbury
wrote:
> On 01/15/2016 05:07 PM, Matthew Brett wrote:
>>>
>>> I attribute
>>> some of the conda-ignoring to "NIH" and, to some extent,
>>> possibly defensiveness (I would be defensive too if I had been
>>> working on pip as long as they had when con
On 01/15/2016 05:07 PM, Matthew Brett wrote:
I attribute
some of the conda-ignoring to "NIH" and, to some extent,
possibly defensiveness (I would be defensive too if I had been
working on pip as long as they had when conda came along ;).
I must say, I don't personally recognize those reasons.
Hi,
On Fri, Jan 15, 2016 at 1:56 PM, Steve Waterbury
wrote:
> On 01/15/2016 04:08 PM, Benjamin Root wrote:
>>
>> So, again, I love conda for what it can do when it works well. I only
>> take exception to the notion that it can address *all* problems, because
>> there are some problems that it jus
On 01/15/2016 04:08 PM, Benjamin Root wrote:
So, again, I love conda for what it can do when it works well. I only
take exception to the notion that it can address *all* problems, because
there are some problems that it just simply isn't properly situated for.
Actually, I would say you didn't m
On Fri, Jan 15, 2016 at 11:56 AM, Travis Oliphant
wrote:
>
>
> I still submit that this is not the best use of time. Conda *already*
solves the problem.My sadness is that people keep working to create an
ultimately inferior solution rather than just help make a better solution
more accessibl
Travis -
I will preface the following by pointing out how valuable miniconda and
anaconda has been for our workplace because we were running into issues
with ensuring that everyone in our mixed platform office had access to all
the same tools, particularly GDAL, NetCDF4 and such. For the longest t
On Fri, Jan 15, 2016 at 12:09 PM, Chris Barker wrote:
> On Fri, Jan 15, 2016 at 11:21 AM, Nathaniel Smith wrote:
>>
>> Sure. Someone's already packaged those for conda, and no one has packaged
>> them for pypi, so it makes sense that conda is more convenient for you. If
>> someone does the work o
On Fri, Jan 15, 2016 at 11:21 AM, Nathaniel Smith wrote:
> Sure. Someone's already packaged those for conda, and no one has packaged
> them for pypi, so it makes sense that conda is more convenient for you. If
> someone does the work of packaging them for pypi, then that difference goes
> away.
>
On Fri, Jan 15, 2016 at 1:21 PM, Nathaniel Smith wrote:
> On Jan 15, 2016 10:23 AM, "Chris Barker" wrote:
> >
> [...]
> > So here is the problem I want to solve:
> >
> > > pip install numpy scipy matplotlib scikit-learn scikit-image pandas
> h5py
> >
> > last I checked, each of those is self-con
On Jan 15, 2016 10:23 AM, "Chris Barker" wrote:
>
[...]
> So here is the problem I want to solve:
>
> > pip install numpy scipy matplotlib scikit-learn scikit-image pandas h5py
>
> last I checked, each of those is self-contained, except for python-level
dependencies, most notably on numpy. So it d
On Thu, Jan 14, 2016 at 12:58 PM, Matthew Brett
wrote:
> On Thu, Jan 14, 2016 at 9:14 AM, Chris Barker - NOAA Federal
> wrote:
> >>> Also, you have the problem that there is one PyPi -- so where do you
> put
> >>> your nifty wheels that depend on other binary wheels? you may need to
> fork
> >>>
On Thu, Jan 14, 2016 at 10:58 AM, Matthew Brett
wrote:
> > but neither the culture nor the tooling support that
> > approach now, so I'm not very confident you could gather adoption.
>
> I don't think there's a very large amount of cultural work - but some
> to be sure.
>
> We already have the fo
Robert beat me to it on einsum, but also check tensordot for general tensor
contraction.
On Fri, Jan 15, 2016 at 9:30 AM, Nathaniel Smith wrote:
> On Jan 15, 2016 8:36 AM, "Li Jiajia" wrote:
>>
>> Hi all,
>> I’m a PhD student in Georgia Tech. Recently, we’re working on a survey
> paper about t
I echo with Robert that the contraction can be done with np.einsum().
Also, check out the np.tensordot() as well - it can also be used to
perform contraction.
Shawn
On Fri, Jan 15, 2016 at 12:32 PM, Robert Kern wrote:
> On Fri, Jan 15, 2016 at 5:30 PM, Nathaniel Smith wrote:
>>
>> On Jan 15, 20
On Fri, Jan 15, 2016 at 5:30 PM, Nathaniel Smith wrote:
>
> On Jan 15, 2016 8:36 AM, "Li Jiajia" wrote:
> >
> > Hi all,
> > I’m a PhD student in Georgia Tech. Recently, we’re working on a survey
paper about tensor algorithms: basic tensor operations, tensor
decomposition and some tensor applicati
On Jan 15, 2016 8:36 AM, "Li Jiajia" wrote:
>
> Hi all,
> I’m a PhD student in Georgia Tech. Recently, we’re working on a survey
paper about tensor algorithms: basic tensor operations, tensor
decomposition and some tensor applications. We are making a table to
compare the capabilities of different
Your first citation is incorrect. It is "VAN DER WALT" (missing V in yours)
Bryan
> On Jan 15, 2016, at 10:36 AM, Li Jiajia wrote:
>
> Hi all,
> I’m a PhD student in Georgia Tech. Recently, we’re working on a survey
> paper about tensor algorithms: basic tensor operations, tensor decomp
Hi all,
I’m a PhD student in Georgia Tech. Recently, we’re working on a survey
paper about tensor algorithms: basic tensor operations, tensor decomposition
and some tensor applications. We are making a table to compare the capabilities
of different software and planning to include NumPy.
25 matches
Mail list logo
