Initial Update

[pyup-bot]

This is my first visit to this fine repo so I have bundled all updates in a single pull request to make things easier for you to merge.

Close this pull request and delete the branch if you want me to start with single pull requests right away

Here's the executive summary:

Updates

Name	used	latest	pypi
django-nose	1.4.3	1.4.4
coverage	4.0.3	4.2
ipython	4.1.2	5.0.0
django-storages-redux	1.2.3	1.3.2
newrelic	2.50.0.39	2.68.0.50
django-versatileimagefield	1.3	1.6
pytz	2016.3	2016.6.1
mock	1.3.0	2.0.0
whitenoise	3.0	3.2
flake8	2.5.4	3.0.3
ipdb	0.9.0	0.10.1
boto	2.39.0	2.42.0
Django	1.9.7	1.9.8
django-model-utils	2.4	2.5
dj-database-url	0.4.0	0.4.1
django-rq	0.9.0	0.9.1
Fabric	1.10.2	1.12.0
factory-boy	2.6.1	2.7.0
gunicorn	19.3.0	19.6.0
psycopg2	2.6.1	2.6.2
gevent	1.0.2	1.1.2
django-configurations	1.0	2.0

Changelogs

django-nose 1.4.3 -> 1.4.4

1.4.4

* Add Django 1.10 support
* Drop Django 1.4, 1.7, and Python 2.6 support
* Drop South support

coverage 4.0.3 -> 4.2

4.2

---

• Since concurrency=multiprocessing uses subprocesses, options specified on
  the coverage.py command line will not be communicated down to them. Only
  options in the configuration file will apply to the subprocesses.
  Previously, the options didn't apply to the subprocesses, but there was no
  indication. Now it is an error to use --concurrency=multiprocessing and
  other run-affecting options on the command line. This prevents
  failures like those reported in issue 495_.
• Filtering the HTML report is now faster, thanks to Ville Skyttä.

.. _issue 495: https://bitbucket.org/ned/coveragepy/issues/495/branch-and-concurrency-are-conflicting

4.2b1

---

Work from the PyCon 2016 Sprints!

• BACKWARD INCOMPATIBILITY: the coverage combine command now ignores an
  existing .coverage data file. It used to include that file in its
  combining. This caused confusing results, and extra tox "clean" steps. If
  you want the old behavior, use the new coverage combine --append option.
• The concurrency option can now take multiple values, to support programs
  using multiprocessing and another library such as eventlet. This is only
  possible in the configuration file, not from the command line. The
  configuration file is the only way for sub-processes to all run with the same
  options. Fixes issue 484_. Thanks to Josh Williams for prototyping.
• Using a concurrency setting of multiprocessing now implies
  --parallel so that the main program is measured similarly to the
  sub-processes.
• When using automatic subprocess measurement, running coverage commands
  would create spurious data files. This is now fixed, thanks to diagnosis and
  testing by Dan Riti. Closes issue 492.
• A new configuration option, report:sort, controls what column of the
  text report is used to sort the rows. Thanks to Dan Wandschneider, this
  closes issue 199_.
• The HTML report has a more-visible indicator for which column is being
  sorted. Closes issue 298_, thanks to Josh Williams.
• If the HTML report cannot find the source for a file, the message now
  suggests using the -i flag to allow the report to continue. Closes
  issue 231_, thanks, Nathan Land.
• When reports are ignoring errors, there's now a warning if a file cannot be
  parsed, rather than being silently ignored. Closes issue 396_. Thanks,
  Matthew Boehm.
• A new option for coverage debug is available: coverage debug config
  shows the current configuration. Closes issue 454_, thanks to Matthew
  Boehm.
• Running coverage as a module (python -m coverage) no longer shows the
  program name as __main__.py. Fixes issue 478_. Thanks, Scott Belden.
• The test_helpers module has been moved into a separate pip-installable
  package: unittest-mixins_.

.. _automatic subprocess measurement: http://coverage.readthedocs.io/en/latest/subprocess.html
.. _issue 199: https://bitbucket.org/ned/coveragepy/issues/199/add-a-way-to-sort-the-text-report
.. _issue 231: https://bitbucket.org/ned/coveragepy/issues/231/various-default-behavior-in-report-phase
.. _issue 298: https://bitbucket.org/ned/coveragepy/issues/298/show-in-html-report-that-the-columns-are
.. _issue 396: https://bitbucket.org/ned/coveragepy/issues/396/coverage-xml-shouldnt-bail-out-on-parse
.. _issue 454: https://bitbucket.org/ned/coveragepy/issues/454/coverage-debug-config-should-be
.. _issue 478: https://bitbucket.org/ned/coveragepy/issues/478/help-shows-silly-program-name-when-running
.. _issue 484: https://bitbucket.org/ned/coveragepy/issues/484/multiprocessing-greenlet-concurrency
.. _issue 492: https://bitbucket.org/ned/coveragepy/issues/492/subprocess-coverage-strange-detection-of
.. _unittest-mixins: https://pypi.python.org/pypi/unittest-mixins

4.1

---

• The internal attribute Reporter.file_reporters was removed in 4.1b3. It
  should have come has no surprise that there were third-party tools out there
  using that attribute. It has been restored, but with a deprecation warning.

4.1b3

---

• When running your program, execution can jump from an except X: line to
  some other line when an exception other than X happens. This jump is no
  longer considered a branch when measuring branch coverage.
• When measuring branch coverage, yield statements that were never resumed
  were incorrectly marked as missing, as reported in issue 440_. This is now
  fixed.
• During branch coverage of single-line callables like lambdas and generator
  expressions, coverage.py can now distinguish between them never being called,
  or being called but not completed. Fixes issue 90, issue 460 and
  issue 475_.
• The HTML report now has a map of the file along the rightmost edge of the
  page, giving an overview of where the missed lines are. Thanks, Dmitry
  Shishov.
• The HTML report now uses different monospaced fonts, favoring Consolas over
  Courier. Along the way, issue 472_ about not properly handling one-space
  indents was fixed. The index page also has slightly different styling, to
  try to make the clickable detail pages more apparent.
• Missing branches reported with coverage report -m will now say ->exit
  for missed branches to the exit of a function, rather than a negative number.
  Fixes issue 469_.
• coverage --help and coverage --version now mention which tracer is
  installed, to help diagnose problems. The docs mention which features need
  the C extension. (issue 479_)
• Officially support PyPy 5.1, which required no changes, just updates to the
  docs.
• The Coverage.report function had two parameters with non-None defaults,
  which have been changed. show_missing used to default to True, but now
  defaults to None. If you had been calling Coverage.report without
  specifying show_missing, you'll need to explicitly set it to True to keep
  the same behavior. skip_covered used to default to False. It is now None,
  which doesn't change the behavior. This fixes issue 485_.
• It's never been possible to pass a namespace module to one of the analysis
  functions, but now at least we raise a more specific error message, rather
  than getting confused. (issue 456_)
• The coverage.process_startup function now returns the Coverage instance
  it creates, as suggested in issue 481_.
• Make a small tweak to how we compare threads, to avoid buggy custom
  comparison code in thread classes. (issue 245_)

.. _issue 90: https://bitbucket.org/ned/coveragepy/issues/90/lambda-expression-confuses-branch
.. _issue 245: https://bitbucket.org/ned/coveragepy/issues/245/change-solution-for-issue-164
.. _issue 440: https://bitbucket.org/ned/coveragepy/issues/440/yielded-twisted-failure-marked-as-missed
.. _issue 456: https://bitbucket.org/ned/coveragepy/issues/456/coverage-breaks-with-implicit-namespaces
.. _issue 460: https://bitbucket.org/ned/coveragepy/issues/460/confusing-html-report-for-certain-partial
.. _issue 469: https://bitbucket.org/ned/coveragepy/issues/469/strange-1-line-number-in-branch-coverage
.. _issue 472: https://bitbucket.org/ned/coveragepy/issues/472/html-report-indents-incorrectly-for-one
.. _issue 475: https://bitbucket.org/ned/coveragepy/issues/475/generator-expression-is-marked-as-not
.. _issue 479: https://bitbucket.org/ned/coveragepy/issues/479/clarify-the-need-for-the-c-extension
.. _issue 481: https://bitbucket.org/ned/coveragepy/issues/481/asyncioprocesspoolexecutor-tracing-not
.. _issue 485: https://bitbucket.org/ned/coveragepy/issues/485/coveragereport-ignores-show_missing-and

4.1b2

---

• Problems with the new branch measurement in 4.1 beta 1 were fixed:
  • Class docstrings were considered executable. Now they no longer are.
  • yield from and await were considered returns from functions, since
    they could tranfer control to the caller. This produced unhelpful "missing
    branch" reports in a number of circumstances. Now they no longer are
    considered returns.
  • In unusual situations, a missing branch to a negative number was reported.
    This has been fixed, closing issue 466_.
• The XML report now produces correct package names for modules found in
  directories specified with source=. Fixes issue 465_.
• coverage report won't produce trailing whitespace.

.. _issue 465: https://bitbucket.org/ned/coveragepy/issues/465/coveragexml-produces-package-names-with-an
.. _issue 466: https://bitbucket.org/ned/coveragepy/issues/466/impossible-missed-branch-to-a-negative

4.1b1

---

• Branch analysis has been rewritten: it used to be based on bytecode, but now
  uses AST analysis. This has changed a number of things:
  • More code paths are now considered runnable, especially in
    try/except structures. This may mean that coverage.py will
    identify more code paths as uncovered. This could either raise or lower
    your overall coverage number.
  • Python 3.5's async and await keywords are properly supported,
    fixing issue 434_.
  • Some long-standing branch coverage bugs were fixed:
    • issue 129_: functions with only a docstring for a body would
      incorrectly report a missing branch on the def line.
  • issue 212_: code in an except block could be incorrectly marked as
    a missing branch.
  • issue 146_: context managers (with statements) in a loop or try
    block could confuse the branch measurement, reporting incorrect partial
    branches.
  • issue 422_: in Python 3.5, an actual partial branch could be marked as
    complete.
• Pragmas to disable coverage measurement can now be used on decorator lines,
  and they will apply to the entire function or class being decorated. This
  implements the feature requested in issue 131_.
• Multiprocessing support is now available on Windows. Thanks, Rodrigue
  Cloutier.
• Files with two encoding declarations are properly supported, fixing
  issue 453_. Thanks, Max Linke.
• Non-ascii characters in regexes in the configuration file worked in 3.7, but
  stopped working in 4.0. Now they work again, closing issue 455_.
• Form-feed characters would prevent accurate determination of the beginning of
  statements in the rest of the file. This is now fixed, closing issue 461_.

.. _issue 129: https://bitbucket.org/ned/coveragepy/issues/129/misleading-branch-coverage-of-empty
.. _issue 131: https://bitbucket.org/ned/coveragepy/issues/131/pragma-on-a-decorator-line-should-affect
.. _issue 146: https://bitbucket.org/ned/coveragepy/issues/146/context-managers-confuse-branch-coverage
.. _issue 212: https://bitbucket.org/ned/coveragepy/issues/212/coverage-erroneously-reports-partial
.. _issue 422: https://bitbucket.org/ned/coveragepy/issues/422/python35-partial-branch-marked-as-fully
.. _issue 434: https://bitbucket.org/ned/coveragepy/issues/434/indexerror-in-python-35
.. _issue 453: https://bitbucket.org/ned/coveragepy/issues/453/source-code-encoding-can-only-be-specified
.. _issue 455: https://bitbucket.org/ned/coveragepy/issues/455/unusual-exclusions-stopped-working-in
.. _issue 461: https://bitbucket.org/ned/coveragepy/issues/461/multiline-asserts-need-too-many-pragma

django-storages-redux 1.2.3 -> 1.3.2

1.3.2

---

• Fix memory leak from not closing underlying temp file in s3boto backend (106_) thanks kmmbvnr
• Allow easily specifying a custom expiry time when generating a url for S3BotoStorage (96_) thanks mattbriancon
• Check for bucket existence when the empty path ('') is passed to storage.exists in S3BotoStorage -
  this prevents a crash when running collecstatic -c on Django 1.9.1 (112) fixed in 116 thanks xblitz

.. _106: jschneier/django-storages#106
.. _96: jschneier/django-storages#96
.. _112: jschneier/django-storages#112
.. _116: jschneier/django-storages#116

1.3.1

---

• A few Azure Storage fixes pass the content-type to Azure, handle chunked content, fix url thanks erlingbo
• Add support for a Dropbox (dropbox) storage backend, thanks ZuluPro (76_)
• Various fixes to the apache_libcloud backend [return the number of bytes asked for by .read, make .name non-private, don't
  initialize to an empty BytesIO object] thanks kaedroho (55_)
• Fix multi-part uploads in s3boto backend not respecting AWS_S3_ENCRYPTION (94_) thanks andersontep
• Automatically gzip svg files thanks comandrei (100_)

.. __: jschneier/django-storages#45
.. _76: jschneier/django-storages#76
.. _55: jschneier/django-storages#55
.. _94: jschneier/django-storages#94
.. _100: jschneier/django-storages#100

1.3

---

• Drop Support for Django 1.5 and Python2.6
• Remove previously deprecated mongodb backend
• Remove previously deprecated parse_ts_extended from s3boto storage
• Add support for Django 1.8+ (36__)
• Add AWS_S3_PROXY_HOST and AWS_S3_PROXY_PORT settings for s3boto backend (41_)
• Fix Python3K compat issue in apache_libcloud (52_)
• Fix Google Storage backend not respecting GS_IS_GZIPPED setting (51__, 60_) thanks stmos
• Rename FTP _name attribute to name which is what the Django File api is expecting (70_)
• Put StorageMixin first in inheritance to maintain backwards compat with older versions of Django (63_)

.. __: jschneier/django-storages#36
.. _41: jschneier/django-storages#41
.. _52: jschneier/django-storages#52
.. __: jschneier/django-storages#51
.. _60: jschneier/django-storages#60
.. _70: jschneier/django-storages#70
.. _63: jschneier/django-storages#63

whitenoise 3.0 -> 3.2

3.2

---

• Add support for the new-style middleware classes introduced in Django 1.10.
  The same WhiteNoiseMiddleware class can now be used in either the old
  MIDDLEWARE_CLASSES list or the new MIDDLEWARE list.
• Fixed a bug where incorrect Content-Type headers were being sent on 304 Not
  Modified responses (thanks oppianmatt <https://github.com/oppianmatt>_).
• Return Vary and Cache-Control headers on 304 responses, as specified by the
  RFC <http://tools.ietf.org/html/rfc7232section-4.1>_.

3.1

---

• Add new :any:WHITENOISE_STATIC_PREFIX setting to give flexibility in
  supporting non-standard deployment configurations e.g. serving the
  application somewhere other than the domain root.
• Fix bytes/unicode bug when running with Django 1.10 on Python 2.7

ipdb 0.9.0 -> 0.10.1

0.10.1

---

• Support IPython 5.0.
  [ngoldbaum]

0.10.0

---

• Stop trying to magically guess when stdout needs to be captured.
  Like needed by nose.
  Rather, provide a set of function that can be called explicitely when needed.
  [gotcha]
• drop support of IPython before 0.10.2

0.9.4

---

• Fix Restart error when using python -m ipdb
  Closes Using set_trace in 0.9.1 raises an error gotcha/ipdb#93.
  [gotcha]

0.9.3

---

• Don't require users to pass a traceback to post_mortem.
  [Wilfred]

0.9.2

---

• Closes Using set_trace in 0.9.1 raises an error gotcha/ipdb#93.
  [gotcha]

0.9.1

---

• Reset sys.modules['__main__'] to original value.
  Closes ipdb.set_trace() breaks inspect gotcha/ipdb#85
  [gotcha]
• Fix support of IPython versions 0.x
  [asivokon]

django-model-utils 2.4 -> 2.5

2.5

---

• Drop support for Python 3.2.
• Add support for Django 1.10.
• Track foreign keys on parent models properly when a tracker
  is defined on a child model. Fixes Update djangorestframework to 3.4.3 #214.

gevent 1.0.2 -> 1.1.2

1.1.1

• Nested callbacks that set and clear an Event no longer cause
  wait to return prematurely. Reported in :issue:771 by Sergey
  Vasilyev.
• Fix build on Solaris 10. Reported in :issue:777 by wiggin15.
• The ref parameter to :func:gevent.os.fork_and_watch was being ignored.
• Python 3: :class:gevent.queue.Channel is now correctly iterable, instead of
  raising a :exc:TypeError.
• Python 3: Add support for :meth:socket.socket.sendmsg,
  :meth:socket.socket.recvmsg and :meth:socket.socket.recvmsg_into
  on platforms where they are defined. Initial :pr:773 by Jakub
  Klama.

1.1.0

• Python 3: A monkey-patched :class:threading.RLock now properly
  blocks (or deadlocks) in acquire if the default value for
  timeout of -1 is used (which differs from gevent's default of
  None). The acquire method also raises the same :exc:ValueError
  exceptions that the standard library does for invalid parameters.
  Reported in :issue:750 by Joy Zheng.
• Fix a race condition in :class:~gevent.event.Event that made it
  return False when the event was set and cleared by the same
  greenlet before allowing a switch to already waiting greenlets. (Found
  by the 3.4 and 3.5 standard library test suites; the same as Python
  bug 13502_. Note that the Python 2 standard library still has this
  race condition.)
• :class:~gevent.event.Event and :class:~.AsyncResult now wake
  waiting greenlets in the same (unspecified) order. Previously,
  AsyncResult tended to use a FIFO order, but this was never
  guaranteed. Both classes also use less per-instance memory.
• Using a :class:~logging.Logger as a :mod:pywsgi error or request
  log stream no longer produces extra newlines. Reported in
  :issue:756 by ael-code.
• Windows: Installing from an sdist (.tar.gz) on PyPI no longer
  requires having Cython installed first. (Note that the binary installation
  formats (wheels, exes, msis) are preferred on Windows.) Reported in
  :issue:757 by Ned Batchelder.
• Issue a warning when :func:~gevent.monkey.patch_all is called with
  os set to False (not the default) but signal is still True
  (the default). This combination of parameters will cause signal
  handlers for SIGCHLD to not get called. In the future this might
  raise an error. Reported by Josh Zuech.
• Issue a warning when :func:~gevent.monkey.patch_all is called more
  than once with different arguments. That causes the cumulative set of all True
  arguments to be patched, which may cause unexpected results.
• Fix returning the original values of certain threading
  attributes from :func:gevent.monkey.get_original.

.. _bug 13502: http://bugs.python.org/issue13502

1.1rc5

• SSL: Attempting to send empty data using the
  :meth:~socket.socket.sendall method of a gevent SSL socket that has
  a timeout now returns immediately (like the standard library does),
  instead of incorrectly raising :exc:ssl.SSLEOFError. (Note that
  sending empty data with the :meth:~socket.socket.send
  method does raise SSLEOFError in
  both gevent and the standard library.) Reported in :issue:719 by
  Mustafa Atik and Tymur Maryokhin, with a reproducible test case
  provided by Timo Savola.

1.1rc4

• Python 2: Using the blocking API at import time when multiple
  greenlets are also importing should not lead to LoopExit.
  Reported in :issue:728 by Garrett Heel.
• Python 2: Don't raise :exc:OverflowError when using the readline
  method of the WSGI input stream without a size hint or with a large
  size hint when the client is uploading a large amount of data. (This
  only impacted CPython 2; PyPy and Python 3 already handled this.)
  Reported in :issue:289 by ggjjlldd, with contributions by Nathan
  Hoad.
• :class:~gevent.baseserver.BaseServer and its subclasses like
  :class:~gevent.pywsgi.WSGIServer avoid allocating a new closure for
  each request, reducing overhead.
• Python 2: Under 2.7.9 and above (or when the PEP 466 SSL interfaces
  are available), perform the same hostname validation that the
  standard library does; previously this was skipped. Also,
  reading, writing, or handshaking a closed
  :class:~ssl.SSLSocket now raises the same :exc:ValueError
  the standard library does, instead of an :exc:AttributeError.
  Found by updating gevent's copy of the standard library test cases.
  Initially reported in :issue:735 by Dmitrij D. Czarkoff.
• Python 3: Fix :meth:~ssl.SSLSocket.unwrap and SNI callbacks.
  Also raise the correct exceptions for unconnected SSL sockets and
  properly validate SSL hostnames. Found via updated standard library
  tests.
• Python 3: Add missing support for :meth:socket.socket.sendfile. Found via updated
  standard library tests.
• Python 3.4+: Add missing support for
  :meth:socket.socket.get_inheritable and
  :meth:~socket.socket.set_inheritable. Found via updated standard
  library tests.

1.1rc3

• Python 2: Support the new PEP 466 :mod:ssl interfaces on any Python 2
  version that supplies them, not just on the versions it officially
  shipped with. Some Linux distributions, including RedHat/CentOS and
  Amazon have backported the changes to older versions. Reported in
  :issue:702.
• PyPy: An interaction between Cython compiled code and the garbage
  collector caused PyPy to crash when a previously-allocated Semaphore
  was used in a __del__ method, something done in the popular
  libraries requests and urllib3. Due to this and other Cython
  related issues, the Semaphore class is no longer compiled by Cython
  on PyPy. This means that it is now traceable and not exactly as
  atomic as the Cython version, though the overall semantics should
  remain the same. Reported in :issue:704 by Shaun Crampton.
• PyPy: Optimize the CFFI backend to use less memory (two pointers per
  watcher).
• Python 3: The WSGI PATH_INFO entry is decoded from URL escapes
  using latin-1, not UTF-8. This improves compliance with PEP 3333 and
  compatibility with some frameworks like Django. Fixed in :pr:712
  by Ruben De Visscher.

1.1rc2

• Exceptions raised by gevent's SSL sockets are more consistent with
  the standard library (e.g., gevent's Python 3 SSL sockets raise
  :exc:socket.timeout instead of :exc:ssl.SSLError, a change
  introduced in Python 3.2).
• Python 2: gevent's socket's sendall method could completely ignore timeouts
  in some cases. The timeout now refers to the total time taken by
  sendall.
• gevent's SSL socket's sendall method should no longer raise SSL3_WRITE_PENDING
  in rare cases when sending large buffers. Reported in :issue:317.
• :func:gevent.signal.signal now allows resetting (SIG_DFL) and ignoring (SIG_IGN) the
  SIGCHLD signal at the process level (although this may allow race
  conditions with libev child watchers). Reported in :issue:696 by
  Adam Ning.
• :func:gevent.spawn_raw now accepts keyword arguments, as
  previously (incorrectly) documented. Reported in :issue:680 by Ron
  Rothman.
• PyPy: PyPy 2.6.1 or later is now required (4.0.1 or later is
  recommended).
• The CFFI backend is now built and usable on CPython implementations
  (except on Windows) if cffi is installed before gevent is
  installed. To use the CFFI backend, set the environment variable
  GEVENT_CORE_CFFI_ONLY before starting Python. This can aid
  debugging in some cases and helps ensure parity across all
  combinations of supported platforms.
• The CFFI backend now calls the callback of a watcher whose args attribute is
  set to None, just like the Cython backend does. It also only
  allows args to be a tuple or None, again matching the Cython backend.
• PyPy/CFFI: Fix a potential crash when using stat watchers.
• PyPy/CFFI: Encode unicode paths for stat watchers using
  :meth:sys.getfilesystemencoding like the Cython backend.
• The internal implementation modules gevent._fileobject2,
  gevent._fileobject3, and gevent._util were removed. These
  haven't been used or tested since 1.1b1.

1.1rc1

• Windows/Python 3: Finish porting the :mod:gevent.subprocess module, fixing a
  large number of failing tests. Examples of failures are in
  :issue:668 and :issue:669 reported by srossross.

• Python 3: The SSLSocket class should return an empty bytes
  object on an EOF instead of a str. Fixed in :pr:674 by Dahoon
  Kim.

• Python 2: Workaround a buffering bug in the stdlib io module
  that caused FileObjectPosix to be slower than necessary in some
  cases. Reported in :issue:675 by WGH-.

• PyPy: Fix a crash. Reported in :issue:676 by Jay Oster.

  .. caution:: There are some remaining, relatively rare, PyPy
  crashes, but their ultimate cause is unknown (gevent,
  CFFI, greenlet, the PyPy GC?). PyPy users can
  contribute to :issue:677 to help track them down.

• PyPy: Exceptions raised while handling an error raised by a loop
  callback function behave like the CPython implementation: the
  exception is printed, and the rest of the callbacks continue
  processing.

• If a Hub object with active watchers was destroyed and then another
  one created for the same thread, which itself was then destroyed with
  destroy_loop=True, the process could crash. Documented in
  :issue:237 and fix based on :pr:238, both by Jan-Philip Gehrcke.

• Python 3: Initializing gevent's hub for the first time
  simultaneously in multiple native background threads could fail with
  AttributeError and ImportError. Reported in :issue:687 by
  Gregory Petukhov.

1.1b6

• PyPy: Fix a memory leak for code that allocated and disposed of many
  :class:gevent.lock.Semaphore subclasses. If monkey-patched, this could
  also apply to :class:threading.Semaphore objects. Reported in
  :issue:660 by Jay Oster.
• PyPy: Cython version 0.23.4 or later must be used to avoid a memory
  leak (details_). Thanks to Jay Oster.
• Allow subclasses of :class:~.WSGIHandler to handle invalid HTTP client
  requests. Reported by not-bob.
• :class:~.WSGIServer more robustly supports :class:~logging.Logger-like parameters for
  log and error_log (as introduced in 1.1b1, this could cause
  integration issues with gunicorn). Reported in :issue:663 by Jay
  Oster.
• :class:~gevent.threading._DummyThread objects, created in a
  monkey-patched system when :func:threading.current_thread is
  called in a new greenlet (which often happens implicitly, such as
  when logging) are much lighter weight. For example, they no longer
  allocate and then delete a :class:~gevent.lock.Semaphore, which is
  especially important for PyPy.
• Request logging by :mod:gevent.pywsgi formats the status code
  correctly on Python 3. Reported in :issue:664 by Kevin Chen.
• Restore the ability to take a weak reference to instances of exactly
  :class:gevent.lock.Semaphore, which was unintentionally removed
  as part of making Semaphore atomic on PyPy on 1.1b1. Reported in
  :issue:666 by Ivan-Zhu.
• Build Windows wheels for Python 3.5. Reported in :pr:665 by Hexchain Tong.

.. _details: https://mail.python.org/pipermail/cython-devel/2015-October/004571.html

1.1b5

• :mod:gevent.subprocess works under Python 3.5. In general, Python 3.5
  has preliminary support. Reported in :issue:653 by Squeaky.
• :func:Popen.communicate <gevent.subprocess.Popen.communicate> honors a timeout
  argument even if there is no way to communicate with the child
  process (none of stdin, stdout and stderr were set to PIPE).
  Noticed as part of the Python 3.5 test suite for the new function
  subprocess.run but impacts all versions (timeout is an
  official argument under Python 3 and a gevent extension with
  slightly different semantics under Python 2).
• Fix a possible ValueError from :meth:Queue.peek <gevent.queue.Queue.peek>.
  Reported in :issue:647 by Kevin Chen.
• Restore backwards compatibility for using gevent.signal as a
  callable, which, depending on the order of imports, could be broken
  after the addition of the gevent.signal module. Reported in
  :issue:648 by Sylvain Zimmer.
• gevent blocking operations performed at the top-level of a module
  after the system was monkey-patched under Python 2 could result in
  raising a :exc:~gevent.hub.LoopExit instead of completing the expected blocking
  operation. Note that performing gevent blocking operations in the
  top-level of a module is typically not recommended, but this
  situation can arise when monkey-patching existing scripts. Reported
  in :issue:651 and :issue:652 by Mike Kaplinskiy.
• SIGCHLD and waitpid now work for the pids returned by the
  (monkey-patched) os.forkpty and pty.fork functions in the
  same way they do for the os.fork function. Reported in
  :issue:650 by Erich Heine.
• :class:~gevent.pywsgi.WSGIServer and
  :class:~gevent.pywsgi.WSGIHandler do a better job detecting and
  reporting potential encoding errors for headers and the status line
  during :meth:~gevent.pywsgi.WSGIHandler.start_response as recommended by the WSGI specification_. In addition, under Python 2, unnecessary encodings
  and decodings (often a trip through the ASCII encoding) are avoided
  for conforming applications. This is an enhancement of an already
  documented and partially enforced constraint: beginning in 1.1a1,
  under Python 2, u'abc' would typically previously have been
  allowed, but u'\u1f4a3' would not; now, neither will be allowed,
  more closely matching the specification, improving debugability and
  performance and allowing for better error handling both by the
  application and by gevent (previously, certain encoding errors could
  result in gevent writing invalid/malformed HTTP responses). Reported
  by Greg Higgins and Carlos Sanchez.
• Code coverage by tests is now reported on coveralls.io_.

.. _WSGI specification: https://www.python.org/dev/peps/pep-3333/the-start-response-callable
.. _coveralls.io: https://coveralls.io/github/gevent/gevent

1.1b4

• Detect and raise an error for several important types of
  programming errors even if Python interpreter optimizations are
  enabled with -O or PYTHONOPTIMIZE. Previously these would go
  undetected if optimizations were enabled, potentially leading to
  erratic, difficult to debug behaviour.
• Fix an AttributeError from gevent.queue.Queue when peek
  was called on an empty Queue. Reported in :issue:643 by michaelvol.
• Make SIGCHLD handlers specified to :func:gevent.signal.signal work with
  the child watchers that are used by default. Also make
  :func:gevent.os.waitpid work with a first argument of -1. (Also
  applies to the corresponding monkey-patched stdlib functions.)
  Noted by users of gunicorn.
• Under Python 2, any timeout set on a socket would be ignored when
  using the results of socket.makefile. Reported in :issue:644
  by Karan Lyons.

1.1b3

• Fix an AttributeError from gevent.monkey.patch_builtins on
  Python 2 when the future_ library is also installed. Reported by
  Carlos Sanchez.
• PyPy: Fix a DistutilsModuleError or ImportError if the CFFI
  module backing gevent.core needs to be compiled when the hub is
  initialized (due to a missing or invalid __pycache__ directory).
  Now, the module will be automtically compiled when gevent is
  imported (this may produce compiler output on stdout). Reported in
  :issue:619 by Thinh Nguyen and :issue:631 by Andy Freeland, with
  contributions by Jay Oster and Matt Dupre.
• PyPy: Improve the performance of gevent.socket.socket:sendall
  with large inputs. bench_sendall.py_ now performs about as well on
  PyPy as it does on CPython, an improvement of 10x (from ~60MB/s to
  ~630MB/s). See this pypy bug_ for details.
• Fix a possible TypeError when calling gevent.socket.wait.
  Reported in 635 by lanstin.
• gevent.socket.socket:sendto properly respects the socket's
  blocking status (meaning it can raise EWOULDBLOCK now in cases it
  wouldn't have before). Reported in :pr:634 by Mike Kaplinskiy.
• Common lookup errors using the :mod:threaded resolver <gevent.resolver_thread> are no longer always printed to stderr
  since they are usually out of the programmer's control and caught
  explicitly. (Programming errors like TypeError are still
  printed.) Reported in :issue:617 by Jay Oster and Carlos Sanchez.
• PyPy: Fix a TypeError from gevent.idle(). Reported in
  :issue:639 by chilun2008.
• The :func:~gevent.pool.Pool.imap_unordered methods of a pool-like
  object support a maxsize parameter to limit the number of
  results buffered waiting for the consumer. Reported in :issue:638
  by Sylvain Zimmer.
• The class :class:gevent.queue.Queue now consistently orders multiple
  blocked waiting put and get callers in the order they
  arrived. Previously, due to an implementation quirk this was often
  roughly the case under CPython, but not under PyPy. Now they both
  behave the same.
• The class :class:gevent.queue.Queue now supports the :func:len function.

.. _future: http://python-future.org
.. _bench_sendall.py: https://raw.githubusercontent.com/gevent/gevent/master/greentest/bench_sendall.py
.. _pypy bug: https://bitbucket.org/pypy/pypy/issues/2091/non-blocking-socketsend-slow-gevent

1.1b2

• Enable using the :mod:c-ares resolver <gevent.resolver_ares> under
  PyPy. Note that its performance characteristics are probably
  sub-optimal.
• On some versions of PyPy on some platforms (notably 2.6.0 on 64-bit
  Linux), enabling gevent.monkey.patch_builtins could cause PyPy
  to crash. Reported in :issue:618 by Jay Oster.
• :func:gevent.kill raises the correct exception in the target greenlet.
  Reported in :issue:623 by Jonathan Kamens.
• Various fixes on Windows. Reported in :issue:625, :issue:627,
  and :issue:628 by jacekt and Yuanteng (Jeff) Pei. Fixed in :pr:624.
• Add :meth:~gevent.fileobject.FileObjectPosix.readable and
  :meth:~gevent.fileobject.FileObjectPosix.writable methods to
  :class:~gevent.fileobject.FileObjectPosix; this fixes e.g., help() on Python 3 when
  monkey-patched.

1.1b1

• setup.py can be run from a directory containing spaces. Reported
  in :issue:319 by Ivan Smirnov.
• setup.py can build with newer versions of clang on OS X. They
  enforce the distinction between CFLAGS and CPPFLAGS.
• gevent.lock.Semaphore is atomic on PyPy, just like it is on
  CPython. This comes at a small performance cost on PyPy.
• Fixed regression that failed to set the successful value to
  False when killing a greenlet before it ran with a non-default
  exception. Fixed in :pr:608 by Heungsub Lee.
• libev's child watchers caused :func:os.waitpid to become unreliable
  due to the use of signals on POSIX platforms. This was especially
  noticeable when using :mod:gevent.subprocess in combination with
  multiprocessing. Now, the monkey-patched os module provides
  a :func:~gevent.os.waitpid function that seeks to ameliorate this. Reported in
  :issue:600 by champax and :issue:452 by Łukasz Kawczyński.
• On platforms that implement :class:select.poll, provide a
  gevent-friendly :class:gevent.select.poll and corresponding
  monkey-patch. Implemented in :pr:604 by Eddi Linder.
• Allow passing of events to the io callback under PyPy. Reported in
  :issue:531 by M. Nunberg and implemented in :pr:604.
• :func:gevent.thread.allocate_lock (and so a monkey-patched standard
  library :func:~thread.allocate_lock) more closely matches the behaviour of the
  builtin: an unlocked lock cannot be released, and attempting to do
  so throws the correct exception (thread.error on Python 2,
  RuntimeError on Python 3). Previously, over-releasing a lock was
  silently ignored. Reported in :issue:308 by Jędrzej Nowak.
• :class:gevent.fileobject.FileObjectThread uses the threadpool to close
  the underling file-like object. Reported in :issue:201 by
  vitaly-krugl.
• Malicious or malformed HTTP chunked transfer encoding data sent to
  the :class:pywsgi handler <gevent.pywsgi.WSGIHandler> is handled more robustly, resulting in
  "HTTP 400 bad request" responses instead of a 500 error or, in the
  worst case, a server-side hang. Reported in :issue:229 by Björn
  Lindqvist.
• Importing the standard library threading module before using
  gevent.monkey.patch_all() no longer causes Python 3.4 to fail to
  get the repr of the main thread, and other CPython platforms to
  return an unjoinable DummyThread. (Note that this is not
  recommended.) Reported in :issue:153.
• Under Python 2, use the io package to implement
  :class:~gevent.fileobject.FileObjectPosix. This unifies the code with the Python 3
  implementation, and fixes problems with using seek(). See
  :issue:151.
• Under Python 2, importing a module that uses gevent blocking
  functions at its top level from multiple greenlets no longer
  produces import errors (Python 3 handles this case natively).
  Reported in :issue:108 by shaun and initial fix based on code by
  Sylvain Zimmer.
• :func:gevent.spawn, :func:spawn_raw and :func:spawn_later, as well as the
  :class:~gevent.Greenlet constructor, immediately produce useful TypeErrors
  if asked to run something that cannot be run. Previously, the
  spawned greenlet would die with an uncaught TypeError the first
  time it was switched to. Reported in :issue:119 by stephan.
• Recursive use of :meth:ThreadPool.apply <gevent.threadpool.ThreadPool.apply> no longer raises a
  LoopExit error (using ThreadPool.spawn and then get on
  the result still could; you must be careful to use the correct hub).
  Reported in :issue:131 by 8mayday.
• When the :mod:threading module is :func:monkey-patched <gevent.monkey.patch_thread>, the module-level lock in the
  :mod:logging module is made greenlet-aware, as are the instance
  locks of any configured handlers. This makes it safer to import
  modules that use the standard pattern of creating a module-level
  :class:~logging.Logger instance before monkey-patching.
  Configuring logging with a basic configuration and then
  monkey-patching is also safer (but not configurations that involve
  such things as the SocketHandler).
• Fix monkey-patching of :class:threading.RLock under Python 3.
• Under Python 3, monkey-patching at the top-level of a module that
  was imported by another module could result in a :exc:RuntimeError
  from :mod:importlib. Reported in :issue:615 by Daniel Mizyrycki.
  (The same thing could happen under Python 2 if a threading.RLock
  was held around the monkey-patching call; this is less likely but
  not impossible with import hooks.)
• Fix configuring c-ares for a 32-bit Python when running on a 64-bit
  platform. Reported in :issue:381 and fixed in :pr:616 by Chris
  Lane. Additional fix in :pr:626 by Kevin Chen.
• (Experimental) Let the :class:pywsgi.WSGIServer accept a
  :class:logging.Logger instance for its log and (new) error_log
  parameters. Take care that the system is fully monkey-patched very
  early in the process's lifetime if attempting this, and note that
  non-file handlers have not been tested. Fixes :issue:106.

1.1a2

• gevent.threadpool.ThreadPool.imap and imap_unordered now
  accept multiple iterables.
• (Experimental) Exceptions raised from iterating using the
  ThreadPool or Group mapping/application functions should now
  have the original traceback.
• :meth:gevent.threadpool.ThreadPool.apply now raises any exception
  raised by the called function, the same as
  :class:~gevent.pool.Group/:class:~gevent.pool.Pool and the
  builtin :func:apply function. This obsoletes the undocumented
  apply_e function. Original PR :issue:556 by Robert Estelle.
• Monkey-patch the selectors module from patch_all and
  patch_select on Python 3.4. See :issue:591.
• Additional query functions for the :mod:gevent.monkey module
  allow knowing what was patched. Discussed in :issue:135 and
  implemented in :pr:325 by Nathan Hoad.
• In non-monkey-patched environments under Python 2.7.9 or above or
  Python 3, using a gevent SSL socket could cause the greenlet to
  block. See :issue:597 by David Ford.
• :meth:gevent.socket.socket.sendall supports arbitrary objects that
  implement the buffer protocol (such as ctypes structures), just like
  native sockets. Reported in :issue:466 by tzickel.
• Added support for the onerror attribute present in CFFI 1.2.0
  for better signal handling under PyPy. Thanks to Armin Rigo and Omer
  Katz. (See https://bitbucket.org/cffi/cffi/issue/152/handling-errors-from-signal-handlers-in)
• The :mod:gevent.subprocess module is closer in behaviour to the
  standard library under Python 3, at least on POSIX. The
  pass_fds, restore_signals, and start_new_session
  arguments are now implemented, as are the timeout parameters
  to various functions. Under Python 2, the previously undocumented
  timeout parameter to :meth:Popen.communicate <gevent.subprocess.Popen.communicate> raises an exception like its
  Python 3 counterpart.
• An exception starting a child process with the :mod:gevent.subprocess
  module no longer leaks file descriptors. Reported in :pr:374 by 陈小玉.
• The example echoserver.py no longer binds to the standard X11
  TCP port. Reported in :issue:485 by minusf.
• :func:gevent.iwait no longer throws :exc:~gevent.hub.LoopExit if the caller
  switches greenlets between return values. Reported and initial patch
  in :issue:467 by Alexey Borzenkov.
• The default threadpool and default threaded resolver work in a
  forked child process, such as with :class:multiprocessing.Process.
  Previously the child process would hang indefinitely. Reported in
  :issue:230 by Lx Yu.
• Fork watchers are more likely to (eventually) get called in a
  multi-threaded program (except on Windows). See :issue:154.
• :func:gevent.killall accepts an arbitrary iterable for the greenlets
  to kill. Reported in :issue:404 by Martin Bachwerk; seen in
  combination with older versions of simple-requests.
• :class:gevent.local.local objects are now eligible for garbage
  collection as soon as the greenlet finishes running, matching the
  behaviour of the built-in :class:threading.local (when implemented
  natively). Reported in :issue:387 by AusIV.
• Killing a greenlet (with :func:gevent.kill or
  :meth:gevent.Greenlet.kill) before it is actually started and
  switched to now prevents the greenlet from ever running, instead of
  raising an exception when it is later switched to. See :issue:330
  reported by Jonathan Kamens.

1.1a1

• Add support for Python 3.3 and 3.4. Many people have contributed to
  this effort, including but not limited to Fantix King, hashstat,
  Elizabeth Myers, jander, Luke Woydziak, and others. See :issue:38.

• Add support for PyPy. See :issue:248. Note that for best results,
  you'll need a very recent PyPy build including CFFI 1.2.0.

• Drop support for Python 2.5. Python 2.5 users can continue to use
  gevent 1.0.x.

• Fix :func:gevent.joinall to not ignore count when
  raise_error is False. See :pr:512 by Ivan Diao.

• Fix :class:gevent.subprocess.Popen to not ignore the bufsize argument. Note
  that this changes the (platform dependent) default, typically from
  buffered to unbuffered. See :pr:542 by Romuald Brunet.

• Upgraded c-ares to 1.10.0. See :pr:579 by Omer Katz.

  .. caution:: The c-ares configure script is now more strict about the
  contents of environment variables such as CFLAGS and LDFLAGS
  and they may have to be modified (for example, CFLAGS is no
  longer allowed to include -I directives, which must instead be
  placed in CPPFLAGS).

• Add a count argument to :func:gevent.iwait. See :pr:482 by
  wiggin15.

• Add a timeout argument to :meth:gevent.queue.JoinableQueue.join
  which now returns whether all items were waited for or not.

• gevent.queue.JoinableQueue treats items passed to
  __init__ as unfinished tasks, the same as if they were put.
  Initial :pr:554 by DuLLSoN.

• gevent.pywsgi no longer prints debugging information for the
  normal conditions of a premature client disconnect. See :issue:136,
  fixed in :pr:377 by Paul Collier.

• (Experimental.) Waiting on or getting results from greenlets that
  raised exceptions now usually raises the original traceback. This
  should assist things like Sentry to track the original problem. See
  :issue:450 and :issue:528 by Rodolfo and Eddi Linder and
  :issue:240 by Erik Allik.

• Upgrade to libev 4.20. See :pr:590 by Peter Renström.

• Fix gevent.baseserver.BaseServer to be printable when its
  handle function is an instancemethod of itself. See :pr:501 by Joe
  Jevnik.

• Make the acquire method of gevent.lock.DummySemaphore always
  return True, supporting its use-case as an "infinite" or unbounded
  semaphore providing no exclusion, and allowing the idiom if sem.acquire(): .... See :pr:544 by Mouad Benchchaoui.

• Patch subprocess by default in gevent.monkey.patch_all. See
  :issue:446.

• gevent.pool.Group.imap and imap_unordered now accept
  multiple iterables like itertools.imap. :issue:565 reported by
  Thomas Steinacher.

• Compatibility note: gevent.baseserver.BaseServer and
  its subclass gevent.server.StreamServer now deterministically
  close the client socket when the request handler returns.
  Previously, the socket was left at the mercies of the garbage
  collector; under CPython 2.x this meant when the last reference went
  away, which was usually, but not necessarily, when the request
  handler returned, but under PyPy it was some arbitrary point in the
  future and under CPython 3.x a ResourceWarning could be generated.
  This was undocumented behaviour, and the client socket could be kept
  open after the request handler returned either accidentally or intentionally.

• Compatibility note: pywsgi now ensures that headers can be
  encoded in latin-1 (ISO-8859-1). This improves adherence to the HTTP
  standard (and is necessary under Python 3). Under certain
  conditions, previous versions could have allowed non-ISO-8859-1
  headers to be sent, but their interpretation by a conforming
  recipient is unknown; now, a UnicodeError will be raised. See :issue:614.

Once you have closed this pull request, I'll create seperate pull requests for every update as soon as I find them.

That's it for now!

Happy merging! 🤖