np.random() is getting treated as module [closed]

Question

Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.

This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.

Closed 6 months ago.

Improve this question

I am trying to create a random numpy array using np.random() but for some reason, instead of taking it as a function, google collab is taking it as a module, I checked the documentation, but I would prefer not to have a default_rng since as to my understanding, I will always get the same array with the same default_rng. I am very confused and help will be appreciated!

Oh, .random() is from np.random. Silly me, I didn't read the first line where it said, "the module np.random". — Aadvik
– Aadvik, Commented Jul 1 at 16:17

Doğa Yağcızeybek · Accepted Answer · 2025-07-01 16:24:10Z

1

NumPy doesn't have a function named `random` directly; instead, it has a module called `random`, and within that module, there's a function also named `random`.

If you're using VSCode and you `Cmd+Click` on `random` after writing

import random from numpy

it will take you to the source code. There, you can find all available functions and notes left by the developers for your reference.

You can perform the desired operation as shown below:

import numpy as np

np.random.rand(3, 4)

source code screenshot

edited Jul 1 at 16:24

answered Jul 1 at 16:23

Doğa Yağcızeybek

663 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

np.random() is getting treated as module [closed]

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related