so may i know the links for mentor ,so that i can talk with them more ??
can you provide me the links please ???
On Wed, Mar 25, 2015 at 12:26 PM, Ralf Gommers
wrote:
>
>
> On Wed, Mar 25, 2015 at 6:50 AM, Stephan Hoyer wrote:
>
>> The most recent discussion about datetime64 was back in March a
On Wed, Mar 25, 2015 at 12:17 PM, SMRUTI RANJAN SAHOO
wrote:
> so may i know the links for mentor ,so that i can talk with them more ??
> can you provide me the links please ???
>
Hi Smruti, there are no links. I am one of the mentors, the other mentors
are all reading this list. You'll get the
>>> import numpy as np
>>> a = np.arange(10)
>>> flags = a.flags
>>> flags
C_CONTIGUOUS : True
F_CONTIGUOUS : True
OWNDATA : True
WRITEABLE : True
ALIGNED : True
UPDATEIFCOPY : False
>>> flags.writeable = False
>>> a.flags
C_CONTIGUOUS : True
F_CONTIGUOUS : True
OWNDATA : True
W
I fail to see the wtf.
flags = a.flags
So, "flags" at this point is just an alias to "a.flags", just like any
other variable in python
"flags.writeable = False" would then be equivalent to "a.flags.writeable =
False". There is nothing numpy-specific here. a.flags is mutable object.
This is how P
On Wed, Mar 25, 2015 at 1:45 PM, Benjamin Root wrote:
> I fail to see the wtf.
>
> flags = a.flags
>
> So, "flags" at this point is just an alias to "a.flags", just like any
> other variable in python
>
> "flags.writeable = False" would then be equivalent to "a.flags.writeable =
> False". There
Ah, *that* example is surprising to me. Regardless of whether it is a C int
of the PyArrayObject struct or not, the way it is presented at the python
code level should make sense. From my perspective, a.flags is a mutable
object of some sort. Updating it should act like a mutable object, not some
o
