Hello,
The CFP for SciPy India 2012, to be held in IIT Bombay from December
27-29 is open. Please spread the word!
Scipy.in is a conference providing opportunities to spread the use of
the Python programming language in the Scientific Computing community
in India. It provides a unique opportunit
On Mon, Nov 28, 2011 at 1:19 PM, Matthew Brett wrote:
> Maybe the content could be put in
> http://github.com/scipy/scipy.github.com so we can make pull requests
> there?
>
The source is here:
https://github.com/scipy/scipy.org-new
___
NumPy-Discussio
Organizers
======
* Jarrod Millman, Neuroscience Institute, UC Berkeley, USA (Conference Co-Chair)
* Prabhu Ramachandran, Department of Aerospace Engineering, IIT
Bombay, India (Conference Co-Chair)
* FOSSEE Team
___
NumPy-Discussion mailing list
NumP
4-5, 2011, Sunday-Monday: Conference
December 6-7 2011, Tuesday-Wednesday: Tutorials/Sprints
Organizers
------
* Jarrod Millman, Neuroscience Institute, UC Berkeley, USA (Conference Co-Chair)
* Prabhu Ramachandran, Department of Aerospace Engineering, IIT
Bombay, India (Conference Co-Cha
Hi,
It is time to start preparing for the 2011 Google Summer of Code
(SoC). As in the past, we will participate in SoC with the Python
Software Foundation (PSF) as our mentoring organization. The PSF has
requested that every project, which wishes to participate in the SoC,
provide a list of at l
On Tue, Jan 4, 2011 at 7:49 PM, Justin Peel wrote:
> I've been submitting some patches recently just by putting them on
> Trac. However, I noticed in the Numpy Developer Guide that it says:
>
> The recommended way to proceed is either to attach these files to
> an enhancement ticket in the Numpy
ials/Sprints
Saturday, Dec. 18: Sprints
Organizers
======
* Jarrod Millman, Neuroscience Institute, UC Berkeley, USA (Conference Co-Chair)
* Prabhu Ramachandran, Department of Aerospace Engineering, IIT
Bombay, India (Conference Co-Chair)
*
Hello,
I plan to update the export controls settings for both numpy and scipy to:
"This project does NOT incorporate, access, call upon, or otherwise
use encryption of any kind, including, but not limited to, open source
algorithms and/or calls to encryption in the operating system or
underlying
On Tue, Jul 13, 2010 at 8:15 PM, Charles R Harris
wrote:
> How should we handle commits during the next week or two? I have a few
> things I want to get in before 1.5 is tagged.
Just keep committing as normal using svn for now. Once we are ready
to make the transition (which includes having docu
Hello all,
On May 26th, I sent an email titled "curious about how people would
feel about moving to github." While there were a few concerns raised,
everyone was generally positive and were mainly concerned that this
transition would need to be done carefully with clear workflow
instructions and
On Wed, Jun 2, 2010 at 10:08 AM, Matthew Brett wrote:
> Do y'all think opt-in? Or opt-out? If it's opt-in I guess you'll
> catch most of the current committers, and most of the others you'll
> lose, but maybe that's good enough.
I think it should be opt-in. How would opt-out work? Would som
On Thu, May 27, 2010 at 2:28 AM, Anne Archibald
wrote:
> * Set up a git repository somewhere on scipy.org.
It's a minor point, but setting up and maintaining our own git
repository will require extra work without gaining anything useful.
Github has a number of very useful features and is gaining
On Thu, May 27, 2010 at 2:28 AM, Anne Archibald
wrote:
> To get back to the original point of the thread: nobody has yet
> objected to git, and all we have are some debates about the ultimate
> workflow that don't make much difference to whether or how git should
> be adopted. Is this a fair descr
On Wed, May 26, 2010 at 7:38 PM, Benjamin Root wrote:
> I wouldn't call myself a developer, but I have been wanting to contribute
> recently. I learned source control with svn, so I am much more comfortable
> with it. My one attempt at using git for a personal project ended in
> failure.
>
> The
On Wed, May 26, 2010 at 8:08 PM, Matthew Brett wrote:
> That's the model we've gone for in nipy and ipython too. We wrote it
> up in a workflow doc project. Here are the example docs giving the
> git workflow for ipython:
>
> https://cirl.berkeley.edu/mb312/gitwash/
>
> and in particular:
>
> ht
On Wed, May 26, 2010 at 6:37 PM, Bruce Southey wrote:
> All that I ask is that there is one official place to do 'git clone'
> or 'git pull' from a single official branch. I do not think that it is
> good to tell users to pull from different branches especially if these
> branches have conflicts.
ems to be interest (which there
currently seems to be). So for now just keep sending emails with
issues you want addressed in any actual proposal for this transition.
Let's move this discussion to the git thread and use the thread for
the discussion related directly to the subject line.
Thank
On Wed, May 26, 2010 at 4:12 PM, Travis Oliphant wrote:
> I think we are ready for such a move. Someone should think about the
> implications, though (with Trac integration, check-in mailings, etc.) and
> make sure we get something we all like. Somebody probably has thought
> through all of t
Hello,
I changed the subject line for this thread, since I didn't want to
hijack another thread. Anyway, I am not proposing that we actually
decide whether to move to git and github now, but I am just curious
how people would feel. We had a conversation about this a few years
ago and it was quit
2010/5/25 Stéfan van der Walt :
> Awesome! Since github now supports SVN interaction, and all the core
> devs use Git, now might be a good time to move the entire numpy source
> tree? It will certainly make it easier to merge the refactor changes!
I would love to move numpy to github as well. Al
On Wed, Apr 28, 2010 at 2:46 PM, David Warde-Farley wrote:
> Would it be acceptable to retain the matrix class but not have it imported in
> the default namespace, and have to import e.g. numpy.matlib to get at them?
+1
Jarrod
___
NumPy-Discussion mai
I added Titus' email regarding the PSF's focus on Py3K-related
projects to our SoC ideas wiki page:
http://projects.scipy.org/scipy/wiki/SummerofCodeIdeas
Given Titus' email, this is the most likely list of projects we will
get accepted this year:
- finish porting NumPy to Py3K
- port SciPy to Py
Hello,
Given the interest in participating in the GSoC this summer, I am
forwarding a very interesting email from Titus Brown. If you are
interested in doing a GSoC or mentoring, please read his email
carefully.
Basically, the PSF will be focuing on Py3K-related projects. Given
Pauli's work on
scipy 0.7.2 = OK
> numpy 1.4.1 + scipy 0.7.1 = NOT OK (Cython issue)
>
> So either release 1.4.1 and 0.7.2 at the same time, or scipy 0.7.2 first.
You should release scipy 0.7.2 first. Since this is your first time
managing the release process, it would be easier to do them one at a
time.
Good catch. I just removed the 1.4.0 tarball from PyPI.
Thanks,
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkeley.edu/
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http
On Mon, Feb 15, 2010 at 10:04 AM, David Huard wrote:
> In the list of things to do, I suggest deleting completely the old
> histogram behaviour and the `new` keyword.
+1
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/
On Sat, Feb 13, 2010 at 1:49 PM, Travis Oliphant wrote:
> This is exactly what I was worried about with calling the next release
> 2.0.
>
> This is not the time to change all the things we wish were done
> differently.
>
> The release is scheduled for 3 weeks.
Hey Travis,
I agree with your gener
release,
though. I would also like to mark the numarray and numeric support as
deprecated and planned for removal in NumPy 3.0. Just marking it
deprecated shouldn't cause any problems and should give anyone left
using the old interfaces plenty of time to migrate prior to a future
3.0 rele
On Mon, Feb 8, 2010 at 2:08 PM, Darren Dale wrote:
>> You don't matter. Nor do I.
>
> I definitely should have counted to 100 before sending that. It wasn't
> helpful and I apologize.
No worries, your first email brought a smile to my face.
___
NumPy-Di
On Mon, Feb 8, 2010 at 1:57 PM, Charles R Harris
wrote:
> Should the release containing the datetime/hasobject changes be called
>
> a) 1.5.0
> b) 2.0.0
My vote goes to b.
Jarrod
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.
I went ahead and set the default download for NumPy back to the 1.3.0
release on sourceforge. I also added a news item stating that 1.4.0
has temporarily been pulled due to the unintended ABI break pending a
decision by the developers. Currently, the 1.4.0 release can still be
accessed if you go
ead and set the default download for NumPy back to the 1.3.0
release on sourceforge. I also added a news item stating that 1.4.0
has temporarily been pulled due to the unintended ABI break.
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://ci
-3 weeks. Then close the discussion and try to
get the 2.0 release out as quickly after that as possible.
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkeley.edu/
___
NumPy-Discussion mailing list
NumPy-
On Fri, Feb 5, 2010 at 12:32 PM, Christopher Barker
wrote:
> If that's the case, and particularly if it's going to be a while before
> 1.4.1 is ready, I suggest that the 1.4.0 release be pulled from "current
> release" status on the download sites.
+1
_
r the summer as well.
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkeley.edu/
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Tue, Feb 2, 2010 at 12:11 AM, David Cournapeau wrote:
> Both Chuck and myself are in favor of removing the datetime altogether
> for 1.4.x as a solution. At least in my case, it is mostly justified
> by the report from David Huard that the current datetime support is
> still a bit too experimen
First I want to give David Cournapeau a big thank you for all his hard
work as release manager for the last few years. It is a lot of work
and he has done a great job managing the releases (not to mention all
the work he has done as one of the primary developers).
I also want to thank Patrick Mar
On Fri, Jan 15, 2010 at 1:38 AM, Sebastian Haase wrote:
> Apparently this very nice looking icons (4 of the 5 icons or so)
> at http://numpy.scipy.org/ are broken links.
Fixed. Thanks,
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkel
On Tue, Dec 1, 2009 at 4:47 AM, David Cournapeau wrote:
> The first release candidate for 1.4.0 has been released.
Excellent! Thanks for all your effort,
Jarrod
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/
th the remaining diffs. I have to run now, but I will look
at it later today.
Thanks,
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkeley.edu/
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.or
; Unless you object, I'd also like to include the distutils docs. Complete
> docs with some possible minor inaccuracies is better than no docs.
+1
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkeley.edu/
_
f these ideas sounds very interesting. Personally, I would like
to see ideas like these make there way into fully fleshed out NEPs:
http://projects.scipy.org/numpy/browser/trunk/doc/neps
--
Jarrod Millman
Helen Wills Neuroscience Institute
10 Giannini Hall, UC Berkeley
http://cirl.berkeley.ed
OK, I've checked in the scipy doc improvements:
http://projects.scipy.org/scipy/changeset/5954
http://projects.scipy.org/scipy/changeset/5955
Thanks to everyone who contributed! I will merge the numpy docs later today.
Is there anything else I need to do on the SciPy documentation editor
to indi
On Thu, Oct 1, 2009 at 9:19 AM, Ralf Gommers
wrote:
> Sorry to ask again, but it would really be very useful to get those
> docstrings merged for both scipy and numpy.
I will do this now.
Jarrod
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.o
Early Registration ends
* Tuesday-Wednesday, August 18-19: Tutorials
* Thursday-Friday, August 20-21: Conference
* Saturday-Sunday, August 22-23: Sprints
* Friday, September 4: Papers for proceedings due
Executive Committee
---
* Jarrod Millman, UC Berkeley, USA (Conference Chair)
* Gaël Varo
: Sprints
* Friday, September 4: Papers for proceedings due
Executive Committee
---
* Jarrod Millman, UC Berkeley, USA (Conference Chair)
* Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair)
* Stéfan van der Walt, University of Stellenbosch, South Africa
(Program Co-Chair
On Fri, Jul 17, 2009 at 10:37 AM, Gökhan SEVER wrote:
> I think, it would be great to have a similar equipment setup during the
> SciPy09.
Absolutely. It would be *great* to have the tutorials and talks
recorded. If anyone steps up to bring equipment, record the talks,
and post them, everyone wo
---
* Jarrod Millman, UC Berkeley, USA (Conference Chair)
* Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair)
* Stéfan van der Walt, University of Stellenbosch, South Africa
(Program Co-Chair)
* Fernando Pérez, UC Berkeley, USA (Tutorial Chair
gistration ends
* Tuesday-Wednesday, August 18-19: Tutorials
* Thursday-Friday, August 20-21: Conference
* Saturday-Sunday, August 22-23: Sprints
* Friday, September 4: Papers for proceedings due
Executive Committee
---
* Jarrod Millman, UC Berkeley, USA (Conference Chair)
* Gaël
Committee
===
* Jarrod Millman, UC Berkeley, USA (Conference Chair)
* Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair)
* Stéfan van der Walt, University of Stellenbosch, South Africa
(Program Co-Chair)
* Fernando Pérez, UC Berkeley, USA (Tuto
On Fri, Apr 3, 2009 at 8:18 AM, David Cournapeau
wrote:
> I am pleased to announce the release of the rc2 for numpy 1.3.0. I have
> decided to go for a rc2 instead of the release directly because of the
> serious mac os X issue. You can find source tarballs and installers for
> both Mac OS X and W
The subject says it all. Over the next few days, we will be updating
the conference website with additional information. So if you are
interested, please keep an eye on: http://conference.scipy.org/
Jarrod
___
Numpy-discussion mailing list
Numpy-discu
On Fri, Mar 27, 2009 at 3:48 AM, David Cournapeau
wrote:
> To build the numpy .dmg mac os x installer, I use a script from the
> adium project, which uses applescript and some mac os x black magic. The
> script seems to be GPL, as adium itself:
Why do you need to use the adium project? I am j
On Tue, Mar 10, 2009 at 11:32 AM, Christopher Barker
wrote:
> hmmm -- I wonder if that is best -- it would put MPL projects in
> competition with all other python projects.
>
> My first thought is that a SciPy application would be best -- with
> SciPy, numpy, MPL, Sage, Cython, etc, it's plenty bi
On Thu, Feb 19, 2009 at 1:24 PM, Bruce Southey wrote:
> Hi,
> Could someone please update the website to clearly state that numpy 1.2
> requires Python 2.4 or later?
> I know it is in the release notes but that assumes people read them :-)
>
> It would be great to state this on the download and in
https://sourceforge.net/project/shownotes.php?release_id=660191&group_id=27747
You can download the release from here:
https://sourceforge.net/project/showfiles.php?group_id=27747&package_id=19531&release_id=660191
Thank you to everybody who contributed to this release.
Enjoy
On Wed, Jan 28, 2009 at 6:11 PM, David Cournapeau
wrote:
> It is said in the email that this is reserved to the python project, and
> prominent python projects like Twisted and Django. Would it be ok to try
> to be qualified as a prominent python project as well ?
That would be great.
___
On Wed, Jan 21, 2009 at 10:53 AM, Gideon Simpson
wrote:
> ==
> FAIL: test_umath.TestComplexFunctions.test_against_cmath
> --
> Traceback (most recent call last):
On Wed, Jan 14, 2009 at 3:17 AM, Mark Asbach wrote:
> I'm currently extending the Python wrapper for the Open Computer Vision
> Library (opencv) with the goal to interface numerical libraries as seemless
> as possible. Unfortunately, it doesn't seem to be that easy ;-)
This is really great. Than
Due to the fact that I was tired of adding site.cfg to scipy and numpy
when building on Fedora and Ubuntu systems as well as a scipy ticket
(http://scipy.org/scipy/numpy/ticket/985), I decided to try and add
default system paths to numpy.distutils. You can find out more
details on this ticket:
h
On Wed, Dec 31, 2008 at 2:53 AM, Alan McIntyre wrote:
> Unless somebody objects, I'd like to remove from NumPy 1.3 the
> following numpy.testing items that were deprecated in NumPy 1.2 (since
> the warnings promise we'll do so ;):
>
> - ParametricTestCase (also removing the entire file
> numpy/te
On Sun, Dec 21, 2008 at 12:13 AM, David Cournapeau
wrote:
>Just a few words to mention that I've finally managed to build numpy
> with the mingw-w64 project (port of mingw to AMD 64 bits MS OS), and it
> almost run OK.
Thanks for working on this.
Jarrod
___
tion that didn't exist when the moin
documentation was started. Either put new docs in the docstrings or
in the scipy tutorial.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
, how many new developers, etc.)
Just a thought. Figure it won't happen, if I don't ask.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
there has been some recent activity in this area I thought I'd mention
it.
As always--thanks to everyone who is actually putting in hard work!
Sorry I am not offering to actually help out here, but I hope that
someone will be interested and able to pursue some of these issues.
Thanks again,
Jar
izable number of users upgrade.
Moin has a detailed list of Python versions for various OSes and
hosting services:
http://moinmo.in/PollAboutRequiringPython24
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
pho
to do?
Please feel free to update the release notes, which are checked into the trunk:
http://scipy.org/scipy/numpy/browser/trunk/doc/release/1.3.0-notes.rst
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510
table headers."
Is anyone familiar with this package? Would make sense to investigate
including this or adopting some of its interface/features?
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.be
the 1.3 release yet, but the
current plan was to try and get the release out near the end of
December. Once SciPy 0.7 is out, I will turn my attention to the next
NumPy release.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC
On Thu, Dec 4, 2008 at 11:14 AM, Pierre GM <[EMAIL PROTECTED]> wrote:
> Raise a ValueError (even in 2.5, therefore risking to break something)
+1
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.ber
programming resources to
helping out, if someone else volunteers to do the majority of the
work.
Thanks,
-- Forwarded message --
From: Gdeisat, Munther <[EMAIL PROTECTED]>
Date: Fri, Sep 28, 2007 at 1:07 PM
Subject: RE: 3D phase unwrap
To: Jarrod Millman <[EMAIL PROTECTED]
http://sourceforge.net/project/shownotes.php?group_id=27747&release_id=642769
You can download the release from here:
http://sourceforge.net/project/showfiles.php?group_id=27747&package_id=19531&release_id=642769
Thank you to everybody who contributed to this release.
Enjoy,
-
eave the old names in
and just add a deprecation note to the docs. Once we are ready to
release 2.0, we can release a 1.x with deprecation warnings.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643
there anything else that we should get in
before releasing 1.3? Does it seem reasonable that we could release
1.3 during the third week of December? Who will have time to work on
NumPy for the next month?
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall
o be great if you could help
figure out what needs to be back-ported from the trunk to the 1.2.x
branch.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
s to 12x ?
Yes, please backport your fixes to the 1.2.x branch. I would like to
get a 1.2.2 release out at least. I would like to release 1.2.2
before we release 0.7.0 final--in case, we need any bugfixes (and
*possibly* minor changes to NumPy testing) in NumPy 1.2.x for SciPy
0.7.x.
--
Jarro
http://projects.scipy.org/scipy/numpy/browser/trunk/doc/neps/generalized-ufuncs.rst
Please feel free to add to this or improve it as you see fit.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu
On Wed, Nov 12, 2008 at 12:58 PM, David Huard <[EMAIL PROTECTED]> wrote:
> Revision 6020 proceeds with the planned changes to histogram semantics for
> the 1.3 release.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone:
the revised BSD license), but I thought I'd ask
anyway.
Should we note the additional licenses in:
http://projects.scipy.org/scipy/numpy/browser/trunk/LICENSE.txt
I was imagining something like:
http://projects.scipy.org/scipy/scipy/browser/trunk/scipy/weave/LICENSE.txt
Thanks,
--
Jarrod Mi
ortran -O3 ?
>
> You're probably right.
I think it is probably best to take out some of the magic in fcompilers as well.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
_
u can download the release from here:
https://sourceforge.net/project/showfiles.php?group_id=1369
Thank you to everybody who contributed to this release.
Enjoy,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cir
Packages/Sparse removed
and all the content merged into
http://docs.scipy.org/doc/scipy/reference/sparse.html
I have cross-posted my response to the numpy list, but let's have this
discussion on the scipy developer's list going forward.
Thanks,
--
Jarrod Millman
Computational Infrastr
e numpy list, but let's have
this discussion on the scipy developer's list going forward.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
__
2.4 compatible lookfor:
http://projects.scipy.org/scipy/numpy/changeset/5945
Setuptools fix:
http://projects.scipy.org/scipy/numpy/changeset/5956
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu
a script
to upload release files and notes? Can you script making the
announcement?
It looks like they md5 support builtin:
https://code.launchpad.net/numpy.scons.support/+download
Ideas? Comments?
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC B
ht be useful:
Releaseforge:
http://releaseforge.sourceforge.net/
Sourceforge Utilities:
http://sfutils.sourceforge.net/
Has anyone found a good way of scripting sourceforge?
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.6
d somehow embed the checksum in the
URL. Maybe something like this:
https://wiki.mozilla.org/Firefox/Feature_Brainstorming:Downloads#MD5_Checksum
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 51
I would also like to back port revision 5833:
http://projects.scipy.org/scipy/numpy/changeset/5833
Are there any other fixes that should be back ported?
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu
On Sun, Oct 5, 2008 at 7:59 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> I would like to get a 1.2.1 release out ASAP. There are several
> bug-fixes on the trunk that need to be backported. If you have made a
> bug-fix to the trunk that you have been waiting to backport to the
er comments from the
> community, I propose that we merge it.
+1
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Numpy-di
, I would like to freeze the branch for the 1.2.1 release in
about 1 week. Please let me know if you need more time or if there is
something in particular that you would like to see backported.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
ng
> version of numscons is about to be released.
Excellent. Thanks for working on this.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy
On Fri, Oct 3, 2008 at 12:35 AM, Francesc Alted <[EMAIL PROTECTED]> wrote:
> It would be nice if you can update the PYPI package index too. Perhaps
> having a list of places on where to announce NumPy on every release
> would be handy.
Done. Thanks,
--
Jarrod Millma
> And I still got 1.1
I updated the page to point to the sourceforge page. Thanks for catching that.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
__
k you to everybody who contributed to this release.
Enjoy,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Numpy-discuss
o wait until 1.2.1, which we will put out shortly.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Numpy-
not:
http://projects.scipy.org/scipy/numpy/changeset/5862
Either way, I plan to tag later today.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-d
the docstring stating it currently
works for 2.5 and make it raise a more informative exception.
lookfor is in 1.1.x as well.
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
__
in preparation for a 1.2.1 release.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http
Glad to hear it is a "known" issue.
By the way, does anyone know what version of gcc we require? Where is
that documented? The only occurrence of a recommended gcc version is
here: http://scipy.org/Installing_SciPy/BuildingGeneral
And it states "gcc 3.x compilers are recommended.
1 - 100 of 336 matches
Mail list logo
