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
Requires python 3.3+ because of back-compatibility support there.
Many potential issues were fixed for 1.6 release (especially around modules and removed features) and tests will at least run mostly.
Here's what's left:
The text was updated successfully, but these errors were encountered:
Completed by parsing refactors, culminating with ae0ef7f
Sorry, something went wrong.
No branches or pull requests
Requires python 3.3+ because of back-compatibility support there.
Many potential issues were fixed for 1.6 release (especially around modules and removed features) and tests will at least run mostly.
Here's what's left:
Many ugly dependencies on unicode type (encoding/decoding to it aggressively, sigh).- solvedMostly in parsing/config handling logic, so the refactoring in 1.7.x will reduce this.- it didmock.assert_any_call broken for some reason- *Subtle issues with use of map/lambda in the math sections of benchmark (Python 3 map function now returns an iterable, not a concrete list).- solvedThe text was updated successfully, but these errors were encountered: