-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multi-mechanize still doesn't work on Windows #19
Comments
I meet the same problem. This helped https://groups.google.com/forum/?fromgroups=#!topic/multi-mechanize/nweLvopvFOM : |
"modifying run.py line 90:" This worked for me on windows 7 64 bit, python 2.7 |
The real reason it's not working on windows, it's cause multiprocessing couldn't pickle some of the objects on the Process Changing it .start call to .run just run the whole thing sequentially in one process (it seems to work, but in big number of virtual users, you'll run out of file descriptors per process) Moving to use pathos.multiprocessing might solve some of the pickling issues I'll give it a go, to see if I can fix it correctly |
EDIT: It works correctly in the latest development version. To install it, run OP: This is still happening with release version 1.2.0, and in the untouched sample project created by
|
I found that it's working correctly in the latest dev version. Now the question is, when will there be a new release? It's been more than 5 years now. |
Hi,
i can't run multi-mechanize successfully on Windows 7.
When i run the project, i get two issues (after applied the "import sys" to the resultswriter.py):
and
The first problem raises when the program tries to recreate the folder that has already created. I believe that this problem is connected to some thread-problem.
All i get is a result folder with an empty csv.
System:
Windows 7 64-bit
Python 2.6 32-bit
multi-mechanize last master commit (pip install git+)
config
Files are really similar or equal to the docs.
What can the problem be?
I'm not so good at python to work out a solution.
The text was updated successfully, but these errors were encountered: