his case just for creating new cleaner APIs
+ possibly doing slow deprecation of the old stuff.
For a widely used library, if the code exists then someone, somewhere
depends on it, regardless of how broken or obscure you think the feature
is. We just have to live with that.
Cheers,
f
--
Fernando Perez
ience,
working locally with Fernando Perez, Matthias Bussonnier, and our new
postdoctoral scholars. But the scope of this role is the entire project, so
we are looking for a candidate who will be regularly communicating with
project stakeholders from all locations, traveling to conferences,
develo
with the full scope of the questions we intend to
tackle.
We'd like to thank the support of the Helmsley Trust, the Gordon and Betty
Moore Foundation and the Alfred P. Sloan Foundation.
Cheers,
Brian Granger and Fernando Perez.
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.n
Ah, great, glad to hear that. Thx!
On Wed, Sep 23, 2015 at 5:43 PM, Matthew Brett
wrote:
> Hi,
>
> On Wed, Sep 23, 2015 at 5:30 PM, Fernando Perez
> wrote:
> > Chance this will be merged into 1.10? I know there's an rc floating out
> > there for 1.10, and t
- do you want to get your mingw-w64 PR in for this?
>
> Cheers,
>
> Matthew
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
--
Fernando Perez (@
o as to clarify what my proposal actually is in the
> context of that document.
>
No worries, I wasn't digging it up further, really! Just clarifying for
other reasons, not digging into you :)
Glad to see the other thread proceeding further, let's let this one die as
peacefully
I was simply asking Travis to separate individuals
from institutions. But I should have realized that calling anyone out by
name in a context like this is a bad idea regardless.
Cheers,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this wh
On Wed, Sep 23, 2015 at 2:31 PM, Stefan van der Walt
wrote:
> Perhaps some kind of group bonding activity, such as working on a shared
> project, would help? ;)
>
Indeed, there's a bunch of fresh 2x4s, screws and bolts with your name on
them ;)
Cheers,
f
--
Fernando Perez (@fp
ut we'll do it, as
we hope this will be useful to the entire community.
Cheers,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
___
t aiming at you personally.
b) a suggestion that we discuss it further personally, taking advantage of
the fact that we happen to be physically close.
If anyone else would like me to answer in public because they feel a slight
on my part, I will do so.
Best,
f
--
Fernando Perez (@fperez_org; http
s point.
The process of establishing governance has to come organically from within
a community.
Cheers
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me h
mmunity, where at any point in time,
any of us should be judged on the merit of our actions, not the
hypotheticals of our intentions or our affiliations (commercial,
government, academic, etc).
Sorry for the long wall of text, I rarely post on this list anymore. But I
was saddened to see the turn
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http
ing we're nearly
certain we won't merge it, but it will make it easier for us to have a
fruitful discussion with you".
Back to lurking ;)
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this whe
Hi all,
the newly founded Berkeley Institute for Data Science is hiring researchers
with a focus on open source tools for scientific computing, please see here
for details:
https://aprecruit.berkeley.edu/apply/JPF00590
Cheers,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at
thanks, reported.
On Tue, Oct 28, 2014 at 11:23 AM, Jean-Baptiste Marquette
wrote:
>
> Le 28 oct. 2014 à 19:09, Fernando Perez a écrit :
>
> a colleague from NCAR in Boulder just sent me this link about a conference
> they are organizing in the spring:
>
>
> Wrong year
ite for an upcoming
call when they post it (I'm not directly involved, just passing the message
along).
Cheers
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for
eri) machine and Intel KNC MIC are coming soon.
Xianyi
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
___
NumP
This same heads-up was also sent out by Stefan Behnel to the cython ML,
please feel free to pass it to other communities that might be interested
in this problem and can provide feedback to python-core while this is in
the discussion phase.
Cheers,
f
--
Fernando Perez (@fperez_org; http
__
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernan
s a stable interface for working with array data.
Boost::Python
- Nothing official from numpy for using numpy arrays in C++
- Not prioritized.
- Numpy has gotten better about namespace pollution?
- It kind of works already. Talk to Mike Droettboom
--
Fernando Perez (@fperez_org; http://fperez.o
_
>> Python-ideas mailing list
>> python-id...@python.org
>> https://mail.python.org/mailman/listinfo/python-ideas
>> Code of Conduct: http://python.org/psf/codeofconduct/
>>
>> ___
>> NumPy-Discussion
>
>>
>>
>>
>> On Sat, Jun 28, 2014 at 8:29 PM, Fernando Perez
>> wrote:
>>
>>> Hi folks,
>>>
>>> I've just created a page on the numpy wiki:
>>>
>>> https://github.com/numpy/numpy/wiki/Numpy-BoF-at-Scipy-2014
;
> -Chris
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists o
ussion mailing list
> > NumPy-Discussion@scipy.org
> > http://mail.scipy.org/mailman/listinfo/numpy-discussion
> >
>
>
>
> --
> Nathaniel J. Smith
> Postdoctoral researcher - Informatics - University of Edinburgh
> http://vorpus.org
> __
Quick question on this: has anyone looked at the Open Watcom compiler?
There was a lighting talk at Pycon about a guy who's been working on
getting Python itself to build on Windows with this compiler. I don't know
if it might help in all this, if nothing else it mitght be good to have.
This was th
On Mon, Apr 7, 2014 at 4:23 PM, Nathaniel Smith wrote:
> Hey all,
>
> Guido just formally accepted PEP 465:
> https://mail.python.org/pipermail/python-dev/2014-April/133819.html
> http://legacy.python.org/dev/peps/pep-0465/#implementation-details
Congratulations!! Getting a PEP through is v
On Mon, Mar 17, 2014 at 10:01 AM, Aron Ahmadia wrote:
>
> On Mon, Mar 17, 2014 at 7:53 AM, Nathaniel Smith wrote:
>
>> The thread so far, it sounds like the consensus answer is "meh,
>> whatever". So I'm thinking we should just drop @@ from the PEP, and if
>> it turns out that this is a problem
obviously be scientific computing, I'd be happy to mention a few
talks from our community in my slides.
Cheers,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contac
d hopefully a
starting point for much more work in slightly better conditions.
Here are some additional resources for anyone interested:
http://bitly.com/bundles/fperezorg/1
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando
On Thu, Sep 5, 2013 at 11:43 AM, Charles R Harris
wrote:
> Oh, nice one ;) Should be fixable if you want to submit a patch.
Strategy? One option is to do, for structured arrays, a shuffle of the
indices and then an in-place
arr = arr[shuffled_indices]
But there may be a cleaner/faster way to
s ago.
Is this my misuse? It really looks like a bug to me...
Cheers,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct
nks to everyone! Please enjoy IPython 1.0, and report all bugs as usual!
Fernando, on behalf of the IPython Dev Team.
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct
its easily into the mnemonic
pattern suggested by .T, yet the extra () are indicative that
something potentially big/expensive is happening...
Cheers,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when
On Sat, Feb 16, 2013 at 4:24 PM, Travis Oliphant wrote:
> If you want to discuss this in public. Let's have the discussion over at
> numfo...@googlegroups.com until a more specific list is created.
Sounds good. I actually think numfocus is a great list for these kind
of 'in-between' discussion
On Sat, Feb 16, 2013 at 3:56 PM, Travis Oliphant wrote:
> We should take this discussion off list.
Just as a bystander interested in this: why? It seems that OCL is
within the scope of what's being proposed and another entrant into the
vibrant new world of compiler-extended machinery for fast nu
Hi all,
please do NOT respond to this thread or to me directly. This is
strictly to spread this message as widely as possible, so that anyone
who receives it and can act on it does so. Needless to say, do
forward this to anyone you think might be in a position to take useful
action.
The Python
On Fri, Jan 18, 2013 at 2:22 PM, Matthew Brett wrote:
> I personally find 'fill' OK. I'd read:
>
> a = np.empty((10, 10), fill=np.nan)
>
> as
>
> "make an empty array shape (10, 10) and fill with nans"
>
> Which would indeed be what the code was doing :) So I doubt that the
> semantic clash woul
On Thu, Nov 22, 2012 at 1:30 AM, Peter Cock wrote:
> Perhaps http://numfocus.org/ could take them on, or the PSF?
> (even if they don't have a specific use in mind immediately)
> For the short them I'd just have them redirect to www.scipy.org ;)
I asked on the numfocus list and nobody was really
Hi folks,
years ago, John Hunter and I bought the py4science.{com, org, info}
domains thinking they might be useful. We never did anything with
them, and with his passing I realized I'm not really in the mood to
keep renewing them without a clear goal in mind.
Does anybody here want to do anythi
On Sat, Oct 20, 2012 at 4:40 AM, Daπid wrote:
a=np.arange(10)
print a
> [0 1 2 3 4 5 6 7 8 9]
repr(a)
> 'array([0, 1, 2, 3, 4, 5, 6, 7, 8, 9])'
>
Note that you don't need to explicitly call repr() at the interactive
prompt: by default, Python prints the repr of an object when you t
On Fri, Oct 19, 2012 at 8:56 AM, Travis Oliphant wrote:
> Kudos! Ray.
>
> Very impressive and useful work.
Indeed, many thanks, Ray!! This has been a ton of work, and somewhat
thankless b/c it's for a one-off thing. What I did for our lanunchpad
bug migration was a far more hackish/dirty job pre
On Fri, Sep 28, 2012 at 3:11 PM, Charles R Harris
wrote:
> Bitch, bitch, bitch. Look, I know you are pissed and venting a bit, but this
> problem could have been detected and reported 6 months ago, that is, unless
> it is new due to development on your end.
It would be great if we could keep thes
Hi folks,
you may have already seen this, but in case you haven't, I'm thrilled
to share that the Python Software Foundation has just created its
newest and highest distinction, the Distinguished Service Award, and
has chosen John as its first recipient:
http://pyfound.blogspot.com/2012/09/announ
Hi all,
I have just received the following information from John's family
regarding the memorial service:
John's memorial service will be held on Monday, October 1, 2012, at
11.a.m. at Rockefeller Chapel at the University of Chicago. The exact
address is 5850 S. Woodlawn Ave, Chicago, IL 60615.
Dear friends and colleagues,
I am terribly saddened to report that yesterday, August 28 2012 at
10am, John D. Hunter died from complications arising from cancer
treatment at the University of Chicago hospital, after a brief but
intense battle with this terrible illness. John is survived by his
w
Dear friends and colleagues,
[please excuse a possible double-post of this message, in-flight
internet glitches]
I am terribly saddened to report that yesterday, August 28 2012 at
10am, John D. Hunter died from complications arising from cancer
treatment at the University of Chicago hospital, af
m, please contact
us directly at:
"C. Titus Brown" ,
"Fernando Perez"
with your name and affiliation, the title of your proposed talk and a
brief description (actual abstracts are due later so an informal
description will suffice for now), by Wednesday August 29. For more
detai
On Fri, Jul 27, 2012 at 9:43 AM, Derek Homeier
wrote:
> thanks, that was exactly what I was looking for - together with
>
> c.TerminalIPythonApp.exec_lines = ['import sys',
>'import numpy as np',
>'import matplotlib as mpl',
>
, Thouis (Ray) Jones wrote:
>> On Wed, Jul 25, 2012 at 6:53 AM, Fernando Perez wrote:
>>> Hi Thouis,
>>>
>>> On Tue, Jul 24, 2012 at 2:46 PM, Thouis (Ray) Jones
>>> wrote:
>>>> I would estimate I'm between a fourth and halfway through t
Hi Thouis,
On Tue, Jul 24, 2012 at 2:46 PM, Thouis (Ray) Jones wrote:
> I would estimate I'm between a fourth and halfway through the
> implementation of the trac-to-github-issues migration code. The work
> lives in at https://github.com/thouis/numpy-trac-migration
mmh, I would have thought you
On Mon, Jul 2, 2012 at 7:49 PM, Fernando Perez wrote:
> It appears you're right!
>
> http://pymc-devs.github.com/pymc/distributions.html?highlight=hypergeometric#pymc.distributions.multivariate_hypergeometric_like
Furthermore, the code actually calls a sampler implemented in
On Mon, Jul 2, 2012 at 7:31 PM, Skipper Seabold wrote:
> I could be wrong, but I think PyMC has sampling and likelihood.
It appears you're right!
http://pymc-devs.github.com/pymc/distributions.html?highlight=hypergeometric#pymc.distributions.multivariate_hypergeometric_like
Thanks :)
Cheers,
Useful-looking:
http://gcc.gnu.org/wiki/CompileFarm
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Mon, Jul 2, 2012 at 3:15 PM, Andrew Dalke wrote:
>
> Thus, I don't see any way that I can import 'multiarray' directly,
> because the underlying C code is the one which imports
> 'numpy.core.multiarray' and by design it is inaccessible to change
> from Python code.
I was just referring to how
On Mon, Jul 2, 2012 at 2:26 PM, Andrew Dalke wrote:
>
> so the relevant timing test is more likely:
>
> % time python -c 'import numpy.core.multiarray'
> 0.086u 0.031s 0:00.12 91.6% 0+0k 0+0io 0pf+0w
No, that's the wrong thing to test, because it effectively amounts to
'import numpy', sicne t
Hi all,
in recent work with a colleague, the need came up for a multivariate
hypergeometric sampler; I had a look in the numpy code and saw we have
the bivariate version, but not the multivariate one.
I had a look at the code in scipy.stats.distributions, and it doesn't
look too difficult to add
Hi all,
sorry for the slightly off-topic post, but I know that in our
community many people often struggle with deployment issues (to
colleagues, to experimental/hardware control machines, to one-off test
machines, ...). I just stumbled upon this announcement by accident,
and figured it might pro
On Sat, Jun 30, 2012 at 11:36 AM, Dag Sverre Seljebotn
wrote:
> It is rumored that a problem with some stackexchange sites is the host
> of nay-sayers saying that a question doesn't belong here but in this
> other silo instead, instead of just letting a culture develop (though my
> only interface
On Sat, Jun 30, 2012 at 10:13 AM, Jason Grout
wrote:
>
> I'm curious: do you mean using stackexchange.com itself, or using
> http://scicomp.stackexchange.com/ specifically?
I meant the latter, which seems like it would be the best suited for
the topic of this discussion. I don't use the site mys
On Sat, Jun 30, 2012 at 9:51 AM, Matthew Brett wrote:
> As a matter of interest - do y'all hang out much on stackexchange? I
> notice that I often go to stackexchange for a good answer, but it
> doesn't seem that good for - discussion. Or maybe it's just I'm not
> used to it.
I'm in the same bo
Hi all,
on behalf of the IPython development team, and just in time for the
imminent Debian freeze and SciPy 2012, I'm thrilled to announce, after
an intense 6 months of work, the official release of IPython 0.13.
This version contains several major new features, as well as a large
amount of bug
On Thu, Jun 28, 2012 at 3:06 PM, srean wrote:
> What I like about having two lists is that on one hand it does not
> prevent me or you from participating in both, on the other hand it
> allows those who dont want to delve too deeply in one aspect or the
> other, the option of a cleaner inbox, or
On Thu, Jun 28, 2012 at 3:03 PM, Matthew Brett wrote:
> Fernando - you told me a week or so ago that you'd come across a blog
> post or similar advocating a single list - do you remember the
> reference?
Found it after some digging:
http://www.kitware.com/blog/home/post/263
and upon rereading i
On Thu, Jun 28, 2012 at 2:07 PM, Matthew Brett wrote:
> I see that sympy, for example, has only one mailing list, and that
> works extremely well. I'd be interested to hear from the Cython and
> IPython guys as to whether they feel the user / devel split has helped
> or hurt. Ferando? Dag?
Ther
On Thu, Jun 28, 2012 at 5:50 AM, Travis Oliphant wrote:
>> Python in fact has the __future__ imports that help quite a bit for
>> people to start adapting their codes. How about creating a
>> numpy.future module where new, non-backward-compatible APIs could go?
>> That would give the adventurous
On Tue, Jun 26, 2012 at 11:02 PM, Travis Oliphant wrote:
> I just want to speak up for the people who are affected by API breakage who
> are not as vocal on this list.
Certainly! And indeed I bet you that's a community underrepresented
here: those of us who are on this list are likely to be up
On Tue, Jun 26, 2012 at 10:25 PM, Ralf Gommers
wrote:
>
> On Tue, Jun 26, 2012 at 5:33 AM, Travis Oliphant
> wrote:
> ...
>>
>> What should have happened in this case, in my mind, is that NumPy 1.4.0
>> should have been 1.5.0 and advertised that there was a break in the ABI and
>> that all extens
On Tue, Jun 26, 2012 at 5:40 PM, Ondřej Čertík wrote:
> Do you use anything else besides Travis CI?
Yes, we use both Shining Panda and Travis CI:
https://jenkins.shiningpanda.com/ipython/
http://travis-ci.org/#!/ipython/ipython
The SP setup is more complete, including Mac and Windows bots.
> I
On Tue, Jun 26, 2012 at 1:10 PM, Travis Oliphant wrote:
> One issues is the one that Sage identified about the array interface
> regression as noted by Jason. Any other regressions from 1.5.x need to be
> addressed as well. We'll have to decide on a case-by-case basis if there
> are issues t
On Mon, Jun 25, 2012 at 10:20 PM, Travis Oliphant wrote:
> Eventually we will need to break the ABI. We might as well wait until 2.0
> at this point.
Ah, got it; thanks for the clarification, I just didn't understand the original.
Cheers,
f
___
Num
On Mon, Jun 25, 2012 at 9:48 PM, Travis Oliphant wrote:
> I agree a decision needs to be made. I think we will need to break the ABI.
> At this point, I don't know of any pressing features that would require it
> short of NumPy 2.0.
Sorry, I don't quite know how to parse the above, do you
On Mon, Jun 25, 2012 at 6:39 PM, Travis Oliphant wrote:
>
> On Jun 25, 2012, at 7:21 PM, Fernando Perez wrote:
>
> For context, consider that for many years, the word "gratuitous" has been
> used in a non-derogatory way in the Python ecosystem to describe changes to
&g
On Mon, Jun 25, 2012 at 5:10 PM, Travis Oliphant wrote:
> You are still missing the point that there was already a choice that was
> made in the previous class --- made in Numeric actually.
>
> You made a change to that. It is the change that is 'gratuitous'.
As someone who played a role in that
Hi folks,
sorry for the cross-post, but I expect all replies to this to happen off-list.
I'm in the process of writing an NSF grant that will partly include
IPython support, and along with Brian we will soon be doing more of
the same. In the past we haven't had the best of luck with the NFS,
hop
On Tue, Jun 5, 2012 at 4:15 PM, Charles R Harris
wrote:
> There are other advantages to pulling down the patch. Fixups can be merged
> together, commit comments enhanced, whitespace removed, style cleanups can
> be added, tests can be run, and the PR is automatically rebased. I still
> like fast f
A couple of notes from the IPython workflow in case it's of use to you guys:
On Tue, Jun 5, 2012 at 10:52 AM, Charles R Harris
wrote:
>
> For the commits themselves, the github button doesn't do fast forward or
> whitespace cleanup, so I have the following alias in .git/config
>
> getpatch = !sh
Hi Nathaniel,
On Sun, May 27, 2012 at 4:11 AM, Nathaniel Smith wrote:
> You guys are probably aware, but just in case, note that there's an
> earlier (quite featureful) version of this idea included in the old
> rnumpy code:
> https://bitbucket.org/njs/rnumpy/wiki/IPython_integration
> https:/
Hi folks,
[ Sorry for the slightly off-topic post, but I know that a number of
people on this list have long wanted more seamless ways to integrate
with tools like Cython and R, and you may not necessarily follow the
ipython lists...]
I'm excited to report that we now have cell magics in IPython.
On Fri, May 11, 2012 at 4:54 PM, Nathaniel Smith wrote:
> I
> have lying around my homedir that it would generally be a free speed
> win
Don't forget the case where the copy semantics may actually provide an
*improvement* in performance by allowing a potentially large array to
get deallocated if
On Wed, May 16, 2012 at 7:10 AM, Nathaniel Smith wrote:
> I tried checking this before, actually, but can't figure out how to
> build scipy against a copy of numpy that is installed in either a
> virtualenv or just on PYTHONPATH. (Basically, I just don't want to
> install some random development n
On Thu, May 10, 2012 at 11:44 PM, Scott Sinclair
wrote:
> That's pretty much how things already work. The documentation is in
> the main source tree and built docs end up at http://docs.scipy.org.
> NEPs live at https://github.com/numpy/numpy/tree/master/doc/neps, but
> don't get published outside
On Thu, May 10, 2012 at 11:03 PM, Scott Sinclair
wrote:
> Having thought about it, a page on the website isn't a bad idea. I've
> added a note pointing to this discussion. The document now appears at
> http://numpy.scipy.org/NA-overview.html
Why not have a separate repo for neps/discussion docs?
Interesting, given the recent discussion on sparsity...
-- Forwarded message --
From: James Demmel
Date: Fri, May 4, 2012 at 12:03 PM
Subject: [SIAM-CSE] pOSKI - Autotuner for parallel
sparse-matrix-vector multiplication
To: siam-...@siam.org
We are pleased to announce the first
Interesting, given the recent discussion on sparsity...
-- Forwarded message --
From: James Demmel
Date: Fri, May 4, 2012 at 12:03 PM
Subject: [SIAM-CSE] pOSKI - Autotuner for parallel
sparse-matrix-vector multiplication
To: siam-...@siam.org
We are pleased to announce the first
On Tue, May 1, 2012 at 6:04 PM, wrote:
> maybe searching issues and pull requests is ok.
> The problem is that in statsmodels we did a lot of commits without
> pull requests, and I'm not very good searching in git either.
> (I don't remember which change I looked for but I got lost for half an
>
On Tue, May 1, 2012 at 5:24 PM, Charles R Harris
wrote:
> I would agree that a good search facility is essential, and not keyword/tag
> based.
Github issues does have full-text search, and up until now I haven't
really had too many problems with it. No sophisticated filtering or
anything, but ba
On Tue, May 1, 2012 at 1:36 PM, Jason Grout wrote:
> This example indicates that basing your decision on what it is like
> *today* may not be valid either. You'd hope that they won't do
Very true ;)
> Anyway, like everyone else has said, Ralf, Pauli, et. al. are really the
> ones to vote in th
Hi folks,
sorry for not jumping in before, swamped with deadlines...
On Mon, Apr 30, 2012 at 8:14 PM, Jason Grout
wrote:
> I've been pretty impressed with the lemonade that the IPython folks have
> made out of what I see as pretty limiting shortcomings of the github
> issue tracker. I've been
On Wed, Apr 25, 2012 at 6:28 PM, Benjamin Root wrote:
>> It would be nice if every pull request created a message to this list.
>> Is that even possible?
>>
>> -Travis
>>
>
> This ha been a concern of mine for matplotlib as well. The closest I can
> come is to set up an RSS feed, but all the tit
On Tue, Apr 24, 2012 at 10:02 PM, wrote:
> Sorry that I missed this part of numpy history, I always had the
> impression that numpy is run by a community led by Chuck and the young
> guys, David, Pauli, Stefan, Pierre; and Robert on the mailing list .
> (But I came late, and am just a balcony mup
On Tue, Apr 24, 2012 at 8:50 PM, Charles R Harris
wrote:
> Turnover is a problem with open source, and no matter how much discussion
> there is, if people aren't doing the work the whole thing sort of peters
> out.
That's very true, and I hope that by building a friendly and welcoming
environment
On Tue, Apr 24, 2012 at 8:02 PM, Charles R Harris
wrote:
> Fernando, I'm not checking credentials, I'm curious.
Well, at least I think that an inquisitive query about someone's
background, phrased like that, can be very easily misread. I can only
speak for myself, but I immediately had the impre
On Tue, Apr 24, 2012 at 6:12 PM, Charles R Harris
wrote:
> I admit to a certain curiosity about your own involvement in FOSS projects,
> and I know I'm not alone in this. Google shows several years of discussion
> on Monotone, but I have no idea what your contributions were
Seriously???
Please,
On Mon, Apr 23, 2012 at 8:49 PM, Stéfan van der Walt wrote:
> If you are referring to the traditional concept of a fork, and not to
> the type we frequently make on GitHub, then I'm surprised that no one
> has objected already. What would a fork solve? To paraphrase the
> regexp saying: after for
On Mon, Apr 23, 2012 at 4:02 PM, Travis Oliphant wrote:
> That is an excellent thought.
>
> We could make the odd numbered releases "experimental" and the even-numbered
> as stable.
>
> That makes some sense. What do others think?
I think the concern with that is manpower: it effectively requ
Hi Nathaniel,
thanks for a solid writeup of this topic. I just want to add a note
from personal experience, regarding this specific point:
On Sun, Apr 22, 2012 at 3:15 PM, Nathaniel Smith wrote:
> Usually disagreements are an indication that a
> better solution is possible, even when it's not c
On Fri, Apr 20, 2012 at 11:27 AM, Dag Sverre Seljebotn
wrote:
>
> I don't think you gain that much by using a different type though? Those
> optimized code paths could be plugged into NumPy as well.
Could be: this was years ago, and the bottleneck for me was in the
constructor and in basic arith
On Fri, Apr 20, 2012 at 9:49 AM, Chris Barker wrote:
>
> I recall discossion a couple times in the past of having some
> special-case numpy arrays for the simple, small cases -- perhaps 1-d
> or 2-d C-contiguous only, for instance. That might be a better way to
> address the small-array performanc
Hi folks,
A number of you expressed interest in attending the PyData workshop
last month and unfortunately we had very tight space restrictions.
But thanks to the team at Marakana, who pitched in and were willing to
film, edit and post videos for many of the talks, you can access them
all here:
h
1 - 100 of 427 matches
Mail list logo
