Скачать или смотреть How to Fix the WinError 10038 Error in Python Socket Server on Windows

Resolve the `WinError 10038` error on your Python 3 socket server with multithreading on Windows. Learn how to adjust your server script for smooth operation.
---
This video is based on the question https://stackoverflow.com/q/64970834/ asked by the user 'John' ( https://stackoverflow.com/u/14692641/ ) and on the answer https://stackoverflow.com/a/64970949/ provided by the user 'Carcigenicate' ( https://stackoverflow.com/u/3000206/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: how to fix "[WinError 10038]" of my python3 socket server script with multithread on windows

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding and Fixing the WinError 10038 in Python Socket Server

Are you running a Python socket server that works seamlessly on Linux but throws a frustrating WinError 10038 when you try it on Windows? You’re not alone! This error can occur due to several reasons, primarily when your server is mismanaging socket operations. In this post, we’ll break down what causes this issue and how to fix it effectively so that your server can handle multiple clients without a hitch.

What is WinError 10038?

The WinError 10038 error message states: “An operation was attempted on something that is not a socket.” This indicates that the Python script is trying to use a socket that has been closed or is not initialized correctly.

In your case, this error appears when you’re accepting clients in a multithreaded environment, and it’s primarily due to how the server socket is handled.

The Problem with Your Socket Server Code

Here's a snippet of how your server script is structured:

[[See Video to Reveal this Text or Code Snippet]]

Identifying the Issue

The main issue lies with the line s.close(), which is closing the server socket s after handling a single client. This leads to further attempts to accept connections throwing the WinError 10038 error because subsequent threads attempt to access a closed socket.

How to Resolve the Error

Here are the steps to fix the error effectively:

1. Remove the s.close() Call

The most straightforward change is to remove the s.close() call from within the work function. The server socket should remain open while other threads are executing.

2. Close the Socket After All Threads Complete

Instead of closing the socket inside the thread, close it after you have joined all threads. Here’s how you can refactor the code:

[[See Video to Reveal this Text or Code Snippet]]

3. Optional: Use a with Block for Socket Management

For even better management and cleaner code, you can use a with statement when creating your socket. This ensures that the socket is automatically closed after use:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By implementing the recommended fixes for your Python socket server, you should be able to avoid the WinError 10038 on Windows. Remember, managing resources correctly is crucial in multithreading environments—what works on one OS may not seamlessly work on another.

Now you can run your Windows socket server with confidence, welcoming multiple clients without encountering the dreaded WinError 10038 again. Happy coding!