| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pyopenssl 0.13 cannot be installed on my Fedora 23. It fails with:
building 'OpenSSL.crypto' extension
(...)
OpenSSL/crypto/crl.c:6:23: erreur: static declaration of ‘X509_REVOKED_dup’ follows non-static declaration
static X509_REVOKED * X509_REVOKED_dup(X509_REVOKED *orig) {
^
In file included from /usr/include/openssl/ssl.h:156:0,
from OpenSSL/crypto/x509.h:17,
from OpenSSL/crypto/crypto.h:30,
from OpenSSL/crypto/crl.c:3:
/usr/include/openssl/x509.h:751:15: note: previous declaration of ‘X509_REVOKED_dup’ was here
X509_REVOKED *X509_REVOKED_dup(X509_REVOKED *rev);
^
error: command 'gcc' failed with exit status 1
The bug is known: https://github.com/pyca/pyopenssl/issues/276
The workaround is simple: use a more recent version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In projects which dynamically determine whether to activate eventlet,
it can be hard not to import a low level module like logging before
eventlet. When logging is imported it initialises a threading.RLock
which it uses to protect the logging configuration. If two
greenthreads attempt to claim this lock, the second one will block the
/native/ thread not just itself. As green systems usually only have
one native thread, this will freeze the whole system.
Search the GC for unsafe RLocks and replace their internal Lock with a
safe one while monkey-patching.
The tests pass, but were they to fail, the test process would never
return. To deal with this, I've added a test dependency on
subprocess32 which is a backport of the stdlib subprocess module from
Python3. This offers a timeout option on Popen#communicate, which I've
arbitrarily set at 30 seconds.
|
|
|
|
|
|
|
|
|
| |
The original commit[1] was not enough because we run tests using tox and
tox by default doesn't pass all environment variables to the
environments in which tests run - this patch whitelists subset of
environment variables set by Travis, including one that we read and use.
[1] 74f418bcf38ac128cadad641d59d7ecd8f127340
|
|
|
|
|
| |
Newest pip versions don't support it anymore and it's been deprecated
for a while.
|
|
|
|
|
| |
The "py{27,34,py}-dns" syntax in envlist is only supported on tox 1.8 or
newer.
|
| |
|
|
|
|
|
|
| |
https://github.com/eventlet/eventlet/issues/203
Also, separate tox environments py{27,34,py}-dns that install and test green DNS.
|
|
|
|
|
|
|
|
|
|
|
|
| |
API:
- write main test body into tests/isolated/filename.py
- it must write 'pass' to stdout or 'skip:[optional reason]'
- write a test with single line: tests.run_isolated('filename.py')
FIXME: autorun all files in tests/isolated
This deprecates tests.run_python and ProcessBase.
TODO: rewrite old multiline string test bodies to isolated files
TODO: add timeout to p.communicate() in run_python()
|
|
|
|
|
|
|
|
| |
using new multi-dimensional support in 1.8
also update travis file
Closes GH #180
|
|
|
|
| |
https://github.com/eventlet/eventlet/issues/177
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes GH #144
|
|
|
|
| |
Tox: PYTHONDONTWRITEBYTECODE = 1
|
|
|
|
|
|
|
| |
- dict.items().pop() in proc
- str/bytes in backdoor, api_test, ssl_test, test__refcount
- import httplib from six
- PEP-8 fixes
|
|
|
|
|
| |
For now, pep8 check is only run for some files known to be clean,
we should clean the rest and enable pep8 check for all files then.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
print() function syntax
|
|
|
|
|
|
|
| |
This helps ensuring everyone uses the code checkers with the same
configuration. Initial values based on earlier discussion. The
max-line-length is currently just based on the screen width I have
on my netbook.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Avoid using property.setter(), use old-style properties instead.
* Avoid using the new pep8-style threading API.
* Use from __future__ import with_statement where it is used.
* Add python 2.5 environments to tox, no epolls since that did not yet
exist.
|
|
|
|
|
|
| |
This is somewhat ugly since tox does not do shell-expansion so we have
to list all files with doctests in. This is fine if new tests are
normally unittests however.
|
| |
|
|
|