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

2014-12-27 Thread Maniteja Nandana
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

2014-12-22 Thread Chris Barker
On Mon, Dec 22, 2014 at 10:15 AM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > As of now, I have now deleted that branch and created a new branch, > taking care of the git add option. But I couldn't find a way to make the > previous pull request use this branch. So, it was closed an

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

2014-12-22 Thread Maniteja Nandana
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

2014-12-22 Thread Maniteja Nandana
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: >>> >>> I have tried to solve Issue #5354 in a bra

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

2014-12-22 Thread Maniteja Nandana
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 were some auto generated files in

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

2014-12-22 Thread Chris Barker
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 were some auto generated files in my branch. > no time to take a look right now -- but you don't

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

2014-12-22 Thread Chris Barker
On Mon, Dec 22, 2014 at 7:40 AM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > > Thank you for the suggestion. I will remember this as a viable option. As > of now, I have a virtual machine of ubuntu running on Windows. So, I wanted > to have least overhead while running the VM. > As

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

2014-12-22 Thread Maniteja Nandana
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

2014-12-22 Thread Maniteja Nandana
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

2014-12-22 Thread Ryan Nelson
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 use the Miniconda package, which is pretty much just conda, to create new "env

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

2014-12-21 Thread Ralf Gommers
On Sun, Dec 21, 2014 at 7:17 PM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > 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 understan

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

2014-12-21 Thread Maniteja Nandana
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

2014-12-21 Thread Ralf Gommers
On Sun, Dec 21, 2014 at 5:37 PM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > 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 te

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

2014-12-21 Thread Maniteja Nandana
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

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

2014-12-21 Thread Ralf Gommers
Hi Maniteja, On Sun, Dec 21, 2014 at 4:04 PM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > 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

[Numpy-discussion] Guidance regarding build and testing

2014-12-21 Thread Maniteja Nandana
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