You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SimpleQueue class in multiprocessing was moved from multiprocessing.queues.SimpleQueue to multiprocessing.SimpleQueue in Python 3.3. However, this move is missing from future.moves and future.standard_library.install_aliases. While not something that occurred in the move from 2 to 3, could this move be added in python-future?
The text was updated successfully, but these errors were encountered:
Thanks for the info and the request, @fergofrog. I wasn't aware of this. Yes, this would make sense.
Would you like to prepare a patch as a pull request? If not, I'll get to it as soon as I can, but it may take a bit longer. We could aim to include this in the next release.
I've added pull request #228 with an attempt at a fix. However, I couldn't figure out how to add the change into futurize. I tried updating the mapping in fix_future_standard_library to include it, but it didn't seem to take.
The SimpleQueue class in multiprocessing was moved from multiprocessing.queues.SimpleQueue to multiprocessing.SimpleQueue in Python 3.3. However, this move is missing from
future.moves
andfuture.standard_library.install_aliases
. While not something that occurred in the move from 2 to 3, could this move be added in python-future?The text was updated successfully, but these errors were encountered: