-
Notifications
You must be signed in to change notification settings - Fork 1
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
cannot pickle '_thread.RLock' object
error
#14
Comments
I have tried removing the .venv an go with python3.11, but seems the same trouble..:
|
Thank you for reporting this. That isn't crashing in my code - it looks like just having a threading.RLock in a multiprocessing object causes things to explode? It's definitely platform specific, I'm on Python 3.10.12 on Ubuntu and I am not seeing this issue. It's possible you could work around this by moving the creation of the RLock out of the constructor and into moggie.workers.base.run() , so doesn't have to cross the process boundary. If that works for you, let me know! |
Running into this on macOS as well. I can test moving the lock, however there are now several locks...
Which one are you referring to and where should it go? |
I am pretty sure the underlying issue here is that I am using multiprocessing to spawn workers, and the default multiprocessing on MacOS uses pickling to transfer state across process boundaries. I probably need to rethink this a bit. |
Hi, I was eager to try it out and hack on it, got everything installed via
. .venv/bin/activate && python3 -m pip install -r requirements.txt
but when running
python3 -m moggie -y
I get:Most likely problem with the miniforge distro of Python, not sure...
The text was updated successfully, but these errors were encountered: