| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
* expunge python 2.6
* how did THAT happen
* remove another unsupported python from the tox envlist
* hypothesis can now be unconditionally imported
|
|
|
|
|
|
| |
* Declare that 2.1 is the last version to support Python 2.6
* It's the Final Countdown!
|
|
|
|
|
|
| |
* remove python 3.3 from CI
* remove 3.3 everywhere, not just from CI
|
|
|
|
|
|
|
|
| |
next release (#3566)
* Deprecate Python 3.3 support, with the intention of being removed in the next release
* whoops
|
| |
|
| |
|
|
|
|
| |
Fixes #1209
|
|
Due to differences in how py.test determines which module to ``import``
the test suite actually runs against the cryptography which is in the
*current* directory instead of the cryptography which is installed. The
problem essentially boils down to when there is a tests/__init__.py then
py.test adds the current directory to the front of the sys.path, causing
it to take precedence over the installed location.
This means that running the tests relies on the implicit compile
that CFFI does instead of testing against what people will actually
be runnning, which is the module compiled by setup.py.
|