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
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
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
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
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
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
