Re: [Numpy-discussion] Implementing a find first style function
On Tue, Mar 26, 2013 at 9:20 AM, Phil Elson pelson@gmail.com wrote: Bump. I'd be interested to know if this is a desirable feature for numpy? (specifically the 1D find functionality rather than the any/all also discussed) If so, I'd be more than happy to submit a PR, but I don't want to put in the effort if the principle isn't desirable in the core of numpy. I don't think anyone has a strong opinion either way :-). It seems like a fairly general interface that people might find useful, so I don't see an immediate objection to including it in principle. It would help to see the actual numbers from a tuned version though to know how much benefit there is to get... -n ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: matplotlib 1.2.1 release
I'm pleased to announce the release of matplotlib 1.2.1. This is a bug release and improves stability and quality over the 1.2.0 release from four months ago. All users on 1.2.0 are encouraged to upgrade. Since github no longer provides download hosting, our tarballs and binaries are back on SourceForge, and we have a master index of downloads here: http://matplotlib.org/downloads http://matplotlib.org/downloads.html Highlights include: - Usage of deprecated APIs in matplotlib are now displayed by default on all Python versions - Agg backend: Cleaner rendering of rectilinear lines when snapping to pixel boundaries, and fixes rendering bugs when using clip paths - Python 3: Fixes a number of missed Python 3 compatibility problems - Histograms and stacked histograms have a number of important bugfixes - Compatibility with more 3rd-party TrueType fonts - SVG backend: Image support in SVG output is consistent with other backends - Qt backend: Fixes leaking of window objects in Qt backend - hexbin with a log scale now works correctly - autoscaling works better on 3D plots - ...and numerous others. Enjoy! As always, there are number of good ways to get help with matplotlib listed on the homepage at http://matplotlib.org/ and I thank everyone for their continued support of this project. Mike Droettboom ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Growing the contributor base of Numpy
Not sure if this is really relevant to the original message, but here is my opinion. I think that the numpy/scipy community would greatly benefit from a platform enabling easy sharing of code written by users. This would provide a database of solved problems, where people could dig without having to ask. I think that something like this exists for matlab, but I have no experience with it. If it exists for python, then it must be seriously under-advertised. The web provides many answers, but they are scattered in all sorts of places, and it is often impossible to contribute improvements to code found online. If such a database could enable some sort of collaborative development it would be a great added value for numpy, and would provide a natural source of new features or improvements for scipy and numpy. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Growing the contributor base of Numpy
On Wed, Mar 27, 2013 at 2:41 PM, Andrea Cimatoribus andrea.cimatori...@nioz.nl wrote: Not sure if this is really relevant to the original message, but here is my opinion. I think that the numpy/scipy community would greatly benefit from a platform enabling easy sharing of code written by users. This would provide a database of solved problems, where people could dig without having to ask. I think that something like this exists for matlab, but I have no experience with it. If it exists for python, then it must be seriously under-advertised. The web provides many answers, but they are scattered in all sorts of places, and it is often impossible to contribute improvements to code found online. If such a database could enable some sort of collaborative development it would be a great added value for numpy, and would provide a natural source of new features or improvements for scipy and numpy. Supposedly that's what scipy-central is for, but it's somehow not yet reached critical mass and become a household name; I haven't looked hard enough to have any hypotheses about why not. Surya Kasturi is working on spiffing it up (see discussion on scipy-dev); I bet they could use some help if you want to scratch this itch. -n ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Growing the contributor base of Numpy
Oh, I didn't even know it existed! Not sure if this is really relevant to the original message, but here is my opinion. I think that the numpy/scipy community would greatly benefit from a platform enabling easy sharing of code written by users. This would provide a database of solved problems, where people could dig without having to ask. I think that something like this exists for matlab, but I have no experience with it. If it exists for python, then it must be seriously under-advertised. The web provides many answers, but they are scattered in all sorts of places, and it is often impossible to contribute improvements to code found online. If such a database could enable some sort of collaborative development it would be a great added value for numpy, and would provide a natural source of new features or improvements for scipy and numpy. Supposedly that's what scipy-central is for, but it's somehow not yet reached critical mass and become a household name; I haven't looked hard enough to have any hypotheses about why not. Surya Kasturi is working on spiffing it up (see discussion on scipy-dev); I bet they could use some help if you want to scratch this itch. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] [numfocus] Growing the contributor base of Numpy
Awesome Ralf! And thanks David C. for being available for the US one. When you say you would like to be part of it, did you mean an advanced tutorial or a sprint? Other people available to contribute to this or coordinate this? Thanks, Jonathan On Wed, Mar 27, 2013 at 3:09 PM, Ralf Gommers ralf.gomm...@gmail.comwrote: On Tue, Mar 26, 2013 at 8:16 AM, Ralf Gommers ralf.gomm...@gmail.comwrote: On Mon, Mar 25, 2013 at 7:56 PM, Jonathan Rocher jroc...@enthought.comwrote: Dear all, One recurring question is how to *grow the contributor base* to NumPy and provide help and relief to core developers and maintainers. One way to do this would be to *leverage the upcoming SciPy conference*in 2 ways: 1. Provide an intermediate or advanced level tutorial on NumPy focusing on teaching the C-API and the architecture of the package to help people navigate the source code, and find answers to precise deep questions. I think that many users would be interested in being better able to understand the underlayers to become powerful users (and contributors if they want to). 2. Organize a Numpy sprint to leverage all this freshly graduated students apply what they learned to tackle some of the work under the guidance of core developers. This would be a great occasion to share and grow knowledge that is fundamental to our community. And the fact that the underlayers are in C is fine IMHO: SciPy is about scientific programming in Python and that is done with a lot of C. *Thoughts? Anyone interested in leading a tutorial (can be a team of people)? Anyone willing to coordinate the sprint? Who would be willing to be present and help during the sprint? * First thought: excellent initiative. I'm not going to be at SciPy, but I'm happy to coordinate a numpy/scipy sprint at EuroScipy. Going to email the organizers right now. The EuroScipy organizers have accepted our sprint, so we'll have a room available. If you're going to the conference, think about reserving Sun 25 Aug to attend this sprint. I've put up a page where people can add topics and more details: http://projects.scipy.org/scipy/wiki/EuroSciPy2013Sprint Ralf Ralf Note that there is less than 1 week left until the tutorial submission deadline. I am happy to help brainstorm on this to make it happen. Thanks, Jonathan and Andy, for the SciPy2013 organizers -- Jonathan Rocher, PhD Scientific software developer SciPy2013 conference co-chair Enthought, Inc. jroc...@enthought.com 1-512-536-1057 http://www.enthought.com -- You received this message because you are subscribed to the Google Groups NumFOCUS group. To unsubscribe from this group and stop receiving emails from it, send an email to numfocus+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Jonathan Rocher, PhD Scientific software developer SciPy2013 conference co-chair Enthought, Inc. jroc...@enthought.com 1-512-536-1057 http://www.enthought.com ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] variables not defined in numpy.random__init.py__ ?
On Tue, Mar 26, 2013 at 9:46 AM, Dinesh B Vadhia dineshbvad...@hotmail.comwrote: ** @ Ralf. I missed info.py at the top and it is a valid statement. @ Brad. My project is using Numpy and Scipy and falls over at this point when using PyInstaller. One of the project source files has an import random from the Standard Library. As you say, at this point in tempfile.py, it is attempting to import random from the Standard Library but instead is importing the one from Numpy (numpy.random). How can this be fixed? Or, is it something for PyInstaller to fix? Thx. Probably the latter. Check your PYTHONPATH is not set and you're not doing anything to sys.path somehow. Then probably best to ask on the PyInstaller mailing list. Ralf *From:* Bradley M. Froehle brad.froe...@gmail.com *Sent:* Monday, March 25, 2013 1:26 PM *To:* Discussion of Numerical Python numpy-discussion@scipy.org *Subject:* Re: [Numpy-discussion] variables not defined in numpy.random__init.py__ ? On Mon, Mar 25, 2013 at 12:51 PM, Ralf Gommers ralf.gomm...@gmail.comwrote: On Mon, Mar 25, 2013 at 4:23 PM, Dinesh B Vadhia dineshbvad...@hotmail.com wrote: ** Using PyInstaller, the following error occurs: Traceback (most recent call last): File string, line 9, in module File //usr/lib/python2.7/dist-packages/PIL/Image.py, line 355, in init __import__(f, globals(), locals(), []) File //usr/lib/python2.7/dist-packages/PIL/IptcImagePlugin.py, line 23, in module import os, tempfile File /usr/lib/python2.7/tempfile.py, line 34, in module from random import Random as _Random File //usr/lib/python2.7/dist-packages/numpy/random/__init__.py, line 90, in module ranf = random = sample = random_sample NameError: name 'random_sample' is not defined Is line 90 in __init.py__ valid? It is. In my reading of this the main problem is that `tempfile` is trying to import `random` from the Python standard library but instead is importing the one from within NumPy (i.e., `numpy.random`). I suspect that somehow `sys.path` is being set incorrectly --- perhaps because of the `PYTHONPATH` environment variable. -Brad ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
