delta/python-packages/cryptography.git/src/cryptography/fernet.py, branch 2.0.3 github.com: pyca/cryptography.git fernet fix: ignore the timestamp entirely when no ttl is set 2016-01-21T14:54:59+00:00 Paul Kehrer paul.l.kehrer@gmail.com 2016-01-21T14:54:59+00:00 a418e96e08537e77b86c7eff8975e0c76b251797 Previously if the token claimed to have been generated more than 60 seconds in the future we would raise InvalidToken even if ttl was set to None. 
Previously if the token claimed to have been generated more than 60
seconds in the future we would raise InvalidToken even if ttl was set
to None.
Update the license header for every source file, as well as the documentation. 2014-11-16T17:08:42+00:00 Alex Gaynor alex.gaynor@gmail.com 2014-11-16T17:08:42+00:00 5951f46be60095a74546b318432417e51bfe0aab Fixes #1209 
Fixes #1209
Move the cryptography package into a src/ subdirectory 2014-11-13T12:56:31+00:00 Donald Stufft donald@stufft.io 2014-11-08T00:17:08+00:00 c62a78c015cf7aeb0c05bce82ef14cd86fe0b0fc 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. 
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.