We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
six.py has an alias for it, making me wonder why future.utils doesn't.
https://pythonhosted.org/six/#six.assertCountEqual
The text was updated successfully, but these errors were encountered:
These two methods only would create more incompatibilities.
This problem is adequately solved by using unittest2. Perhaps python-future could do the patchwork necessary to add unittest2 when it is needed?
Sorry, something went wrong.
Also would like to see this in future.
It's a pain that Py3 basically broke this, seemingly by accident if you read the history. Seems like the perfect pain point for future to patch over.
Needing unittest2 for this seems overkill.
No branches or pull requests
six.py has an alias for it, making me wonder why future.utils doesn't.
https://pythonhosted.org/six/#six.assertCountEqual
The text was updated successfully, but these errors were encountered: