You can tackle this error by finding the right method of executing the function through the prescribed way of performing the function in accordance with the file descriptor. One common thing that you can notice while handling errors in Python in relevance to files and file descriptors is that many of us fail to follow and implement the proper functions of the file descriptors defined in the code to perform the operations.
In addition to the above-discussed problems, this issue occurs while executing simple print statements too. You should focus on knowing if your specific file descriptors are available in the console that you are running. This might seem simple when phrased but can cause a huge trauma to the programmer who has invested hours in writing the code.
First, make sure that the specifies file descriptors are available in the console in which you run your program. One way of handling this error is to calmly ignore the print statements and use alternative segments of code that serve a similar purpose. This error is caused when you specify a function to get executed when it has already completed doing the job. For instance, you order your code to close a file through your long lines of code.
It shows an error like:. It means that the file defined in the program is already closed automatically while running the code. Shutdown the secure socket. Close the secure socket. Used cipher:. Shared ciphers:. Compression used:. Learn more. Asked 11 years, 9 months ago. Active 7 years, 8 months ago. Viewed 11k times. Are we having fun yet?!? Improve this question. Community Bot 1 1 1 silver badge. Add a comment. Active Oldest Votes. Improve this answer. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for. Search instead for. Did you mean:. Sign In. Bad file descriptor.
0コメント