TypeError: 'module' object is not callable
File "C:\Users\Administrator\Documents\Mibot\oops\blinkserv.py", line 82, in __init__ self.serv = socket(AF_INET,SOCK_STREAM) TypeError: 'module' object is not callable
Why am I getting this error? I'm confused.
What do you need to know to answer my question?
socket is a module, containing the class
You need to do
from socket import socket:
>>> import socket >>> socket <module 'socket' from 'C:\Python27\lib\socket.pyc'> >>> socket.socket <class 'socket._socketobject'> >>> >>> from socket import socket >>> socket <class 'socket._socketobject'>
This is what the error message means:
module object is not callable, because your code is calling a module object. A module object is the type of thing you get when you import a module. What you were trying to do is to call a class object within the module object that happens to have the same name as the module that contains it.
Here is a way to logically break down this sort of error:
module object is not callable. Python is telling me my code trying to call something that cannot be called. What is my code trying to call?"
- "The code is trying to call on
socket. That should be callable! Is the variable
socketis what I think it is?`
- I should print out what socket is and check
Read more… Read less…
Assume that the content of YourClass.py is:
class YourClass: # ......
If you use:
from YourClassParentDir import YourClass # means YourClass.py
In this way, I got TypeError: 'module' object is not callable if you then tried to use
But, if you use:
from YourClassParentDir.YourClass import YourClass # means Class YourClass
YourClass.YourClass(), it works for me.
Add to the main
__init__.py in YourClassParentDir, e.g.:
from .YourClass import YourClass
Then, you will have an instance of your class ready when you import it into another script:
from YourClassParentDir import YourClass
Here is another gotcha, that took me awhile to see even after reading these posts. I was setting up a script to call my python bin scripts. I was getting the module not callable too.
My zig was that I was doing the following:
from mypackage.bin import myscript ... myscript(...)
when my zag needed to do the following:
from mypackage.bin.myscript import myscript ... myscript(...)
In summary, double check your package and module nesting.
What I am trying to do is have a scripts directory that does not have the *.py extension, and still have the 'bin' modules to be in mypackage/bin and these have my *.py extension. I am new to packaging, and trying to follow the standards as I am interpreting them. So, I have at the setup root:
setup.py scripts/ script1 mypackage/ bin/ script1.py subpackage1/ subpackage_etc/
If this is not compliant with standard, please let me know.
It seems like what you've done is imported the
socket module as
import socket. Therefore
socket is the module. You either need to change that line to
self.serv = socket.socket(socket.AF_INET, socket.SOCK_STREAM), as well as every other use of the
socket module, or change the import statement to
from socket import socket.
Or you've got an
import socket after your
from socket import *:
>>> from socket import * >>> serv = socket(AF_INET,SOCK_STREAM) >>> import socket >>> serv = socket(AF_INET,SOCK_STREAM) Traceback (most recent call last): File "<input>", line 1, in <module> TypeError: 'module' object is not callable
I know this thread is a year old, but the real problem is in your working directory.
I believe that the working directory is
C:\Users\Administrator\Documents\Mibot\oops\. Please check for the file named
socket.py in this directory. Once you find it, rename or move it. When you import socket,
socket.py from the current directory is used instead of the
socket.py from Python's directory. Hope this helped. :)
Note: Never use the file names from Python's directory to save your program's file name; it will conflict with your program(s).