Re: [Numpy-discussion] (no subject)

Hi, Welcome! It would be a good exercise to look at the documentation and tutorial for Numpy at http://docs.scipy.org/doc/ Also the lectures at the lectures at www.scipy-lectures.org might be a interesting introduction to scientific python in numpy stack. Hope it helps. Happy learning ! Cheers

[Numpy-discussion] Regarding taking up project ideas and GSoC 2015

Hello everyone, I am a third year computer science undergraduate student, from BITS Pilani, India. First of all, I have cross posted to both the mailing lists, since there is a large overlap among contributors of the organisations. Please do mention if there is any objection to do so. I am writ

Re: [Numpy-discussion] Float view of complex array

Hi Jens, I don't have enough knowledge about the internal memory layout, but the documentation ndarray.view says that: Views that change the dtype size (bytes per entry) should normally be avoided on arrays defined by s

Re: [Numpy-discussion] The future of ndarray.diagonal()

har...@gmail.com> wrote: > > > On Thu, Jan 15, 2015 at 9:44 AM, Maniteja Nandana < > maniteja.modesty...@gmail.com> wrote: > >> Hello everyone, >> >> I just wanted to highlight the point made by Charles, it would be great >> if he would clarify any mistakes

Re: [Numpy-discussion] The future of ndarray.diagonal()

Hello everyone, I just wanted to highlight the point made by Charles, it would be great if he would clarify any mistakes in the points that I put forward. Quoting the documentation, In versions of NumPy prior to 1.7, this function always returned a new,independent array containing a copy of the

Re: [Numpy-discussion] Equality of dtypes does not imply equality of type kinds

Hi, On Tue, Jan 13, 2015 at 12:03 AM, Alexander Belopolsky wrote: > Consider this (on a 64-bit platform): > > >>> numpy.dtype('q') == numpy.dtype('l') > True > > >>> numpy.dtype('q').char == numpy.dtype('l').char > False > > Is that intended? Shouldn't dtype constructor "normalize" 'l' to 'q' (

Re: [Numpy-discussion] edge-cases of ellipsis indexing

Hi Anthony, I am not sure whether the following section in documentation is relevant to the behavior you were referring to. When an ellipsis (...) is present but has no size (i.e. replaces zero :) the result will still always be an array. A view if no advanced index is present, otherwise a copy.

[Numpy-discussion] Regarding np.ma.masked_equal behavior

Hello friends, This is an issue related to the working of *masked_equal* method. I was thinking if anyone related to an old ticket #1851 , regarding the modification of *masked_equal *function effect on *fill_value *could clarify the situation, since rig

Re: [Numpy-discussion] Clarifications in numpy.ma module

On 31-Dec-2014 4:53 am, "Nathaniel Smith" wrote: > > On Tue, Dec 30, 2014 at 10:56 PM, Benjamin Root wrote: > > exception? Did you mean warning? If warning, I recall some discussion > > recently to figure out a way to hide that, but only for masked values (I > > would want to see the warning if I

Re: [Numpy-discussion] Clarifications in numpy.ma module

I was just referring to the exception raised in the case where the length of the array is zero. I have not thought if the example provided by @Alexander. I was also wondering if the automatic masking of NaN should be done or not, which is why I asked about the difference in the operating named arra

Re: [Numpy-discussion] Clarifications in numpy.ma module

S/numpy/numpy/core/_methods.py:69: RuntimeWarning: invalid value encountered in true_divide ret, rcount, out=ret, casting='unsafe', subok=False) masked_array(data = nan, mask = False, fill_value = 1e+20) Thanks , Maniteja. On Tue, Dec 30, 2014 at 4:19 PM, Manit

[Numpy-discussion] Clarifications in numpy.ma module

Hi all, I have recently been trying out various functions in masked array module of numpy. I have got confused at a places in the *core.py *of *ma *module. 1. In the *masked_equal *method, the docstring doesn't suggest that the *fill_value *gets updated by the *value *parameter of the function, b

Re: [Numpy-discussion] Guidance regarding build and testing

Hello guys, I have filed a pull request 5386, which is my first one. It would be great if someone would lookup at the issue, and suggest any further changes. Waiting in anticipation, Maniteja. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org

Re: [Numpy-discussion] Guidance regarding build and testing

Hi everyone, Sorry for the empty message accidently sent before. I have checked the travis build for the pull request. I have no idea what failure on 'USE WHEEL = 1' option means. It would be great if someone could tell whether this result means the correction in the file caused the build to break

Re: [Numpy-discussion] Guidance regarding build and testing

On Mon, Dec 22, 2014 at 11:45 PM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > On Mon, Dec 22, 2014 at 10:43 PM, Chris Barker > wrote: > >> On Mon, Dec 22, 2014 at 8:22 AM, Maniteja Nandana < >> maniteja.modesty...@gmail.com> wrote: >>>

Re: [Numpy-discussion] Guidance regarding build and testing

On Mon, Dec 22, 2014 at 10:43 PM, Chris Barker wrote: > On Mon, Dec 22, 2014 at 8:22 AM, Maniteja Nandana < > maniteja.modesty...@gmail.com> wrote: >> >> I have tried to solve Issue #5354 in a branch. Now if I try to compare my >> branch with numpy master, there wer

Re: [Numpy-discussion] Guidance regarding build and testing

Hello everyone, I have tried to solve Issue #5354 in a branch. Now if I try to compare my branch with numpy master, there were some auto generated files in my branch. I have created a pull request #5385 for this, please do suggest if there needs to be any changes in the pull request and the branch

Re: [Numpy-discussion] Guidance regarding build and testing

Hi Ryan, On Mon, Dec 22, 2014 at 8:30 PM, Ryan Nelson wrote: > Maniteja, > > Ralf's suggestion for Numpy works very well. In a more general case, > though, you might want to play around with conda, the package manager for > Anaconda's Python distribution (http://continuum.io/downloads). > > I us

Re: [Numpy-discussion] Guidance regarding build and testing

Hello Ralf, Thanks for the help. Now I am able to see the modifications in the interpreter. As I was going through broadcasting and slicing, I was eager to try out different modifications to understand the working. On Sun, Dec 21, 2014 at 10:57 PM, Ralf Gommers wrote: > > Almost. test_xxx.py con

Re: [Numpy-discussion] Guidance regarding build and testing

Hello Ralf, On Sun, Dec 21, 2014 at 9:17 PM, Ralf Gommers wrote: > Hi Maniteja, > > On Sun, Dec 21, 2014 at 4:04 PM, Maniteja Nanda > You don't need a virtualenv. If you want to only run the tests and make > sure your changes pass the test suite, the easiest option is ``python > runtests.py`` in

[Numpy-discussion] Guidance regarding build and testing

Hello everyone, I am a novice in open source. I needed a small guidance in creating a local build of a repository. I was trying to make simple changes in a cloned copy of numpy ( here it was numpy/numoy/ma/core.py ). If I need to see the effect of these changes in actual working, are there any bui

Re: [Numpy-discussion] Guidance to start contribution to Numpy

n/listinfo/numpy-discussion>numpy <http://mail.scipy.org/mailman/listinfo/numpy-discussion>-discussion <http://mail.scipy.org/mailman/listinfo/numpy-discussion> Hi Maniteja, On Sun, Nov 2, 2014 at 11:21 AM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > Hi

[Numpy-discussion] Guidance to start contribution to Numpy

Hi everyone, I'm a third year undergraduate student in Computer Science. I have worked in Python libraries for past two years and am interested in getting some open source experience in Numpy and it would be great if anyone could suggest some bugs or issues that are suitable for a beginner to try w