Requirements - Initial Update #47

pyup-bot · 2016-07-05T14:08:23Z

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
django-mailgun	0.8.0	0.9.1
ipdb	0.9.0	0.10.1
gevent	1.1rc5	1.1.1
Pillow	3.1.1	3.3.0
django	1.9.4	1.9.7
django-floppyforms	1.6.1	1.6.2
django-test-plus	1.0.12	1.0.14
django-test-plus	1.0.12	1.0.14
GitPython	1.0.2	2.0.6
flake8	2.5.4	2.6.2
pytz	2015.7	2016.4
whitenoise	2.0.6	3.2
colorlog	2.6.3	2.7.0
django-model-utils	2.4	2.5
gunicorn	19.4.5	19.6.0
django-extensions	1.6.1	1.6.7
boto	2.39.0	2.41.0
celery	3.1.21	3.1.23
django-braces	1.8.1	1.9.0
pytest-sugar	0.5.1	0.7.1
pytest-sugar	0.5.1	0.7.1
Werkzeug	0.11.4	0.11.9
django-coverage-plugin	1.2.2	1.3.1
django-coverage-plugin	1.2.2	1.3.1
django-allauth	0.24.1	0.25.2
factory-boy	2.6.1	2.7.0
factory-boy	2.6.1	2.7.0
coverage	4.0.3	4.1
coverage	4.0.3	4.1
django-redis	4.3.0	4.4.3

Pins

Name	Pinned to	pypi
Sphinx	1.4.4
raven	5.21.0
opbeat	3.3.4

Changelogs

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]

gevent 1.1rc5 -> 1.1.1

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

Pillow 3.1.1 -> 3.3.0

3.3.0

Fixed enums for Resolution Unit and Predictor in TiffTags.py 1998
[wiredfool]

Fix issue converting P mode to LA 1986
[didrix]

Moved test_j2k_overflow to check_j2k_overflow, prevent DOS of our 32bit testing machines 1995
[wiredfool]

Skip CRC checks in PNG files when LOAD_TRUNCATED_IMAGES is enabled 1991
[kkopachev]

Added CMYK mode for opening EPS files 1826
[radarhere]

Docs: OSX build instruction clarification 1994
[wiredfool]

Docs: Filter comparison table 1993
[homm]

Removal of pthread based Incremental.c, new interface for file decoders/encoders to access the python file. Fixes assorted J2k Hangs. 1934
[wiredfool]

Skip unnecessary passes when resizing 1954
[homm]

Removed duplicate code in ImagePalette 1832
[radarhere]

test_imagecms: Reduce precision of extended info due to 32 bit machine precision 1990
[AbdealiJK]

Binary Tiff Metadata/ICC profile. 1988
[wiredfool]

Ignore large text blocks in PNG if LOAD_TRUNCATED_IMAGES is enabled 1970
[homm]

Replace index = index+1 in docs with +=1
[cclauss]

Skip extra 0xff00 in jpeg 1977
[kkopachev]

Use bytearray for palette mutable storage 1985
[radarhere, wiredfool]

Added additional uint modes for Image.fromarray, more extensive tests of fromarray 1984
[mairsbw, wiredfool]

Fix for program importing PyQt4 when PyQt5 also installed 1942
[hugovk]

Changed depends/install_*.sh urls to point to github pillow-depends repo 1983
[wiredfool]

Allow ICC profile from encoderinfo while saving PNGs 1909
[homm]

Fix integer overflow on ILP32 systems (32-bit Linux). 1975
[lambdafu]

Change function declaration to match Tcl_CmdProc type 1966
[homm]

Integer overflow checks on all calls to *alloc 1781
[wiredfool]

Change equals method on Image so it short circuits 1967
[mattBoros]

Runtime loading of TCL/TK libraries, eliminating build time dependency. 1932
[matthew-brett]

Cleanup of transform methods 1941
[homm]

Fix "Fatal Python error: UNREF invalid object" in debug builds 1936
[wiredfool]

Setup fixes for Alpine linux 1937
[wiredfool]

Split resample into horizontal + vertical passes 1933
[homm]

Box blur with premultiplied alpha 1914
[homm]

Add libimagequant support in quantize() 1889
[rr-]

Added internal Premultiplied luminosity (La) mode 1912
[homm]

Fixed point integer resample 1881
[homm]

Removed docs/BUILDME script 1924
[radarhere]

Moved comments to docstrings 1926
[hugovk]

Include Python.h before wchar.h so _GNU_SOURCE is set consistently 1906
[hugovk]

Updated example decoder in documentation 1899
[radarhere]

Added support for GIF comment extension 1896
[radarhere]

Removed support for pre- 1.5.2 list form of Image info in Image.new 1897
[radarhere]

Fix typos in TIFF tags 1918
[radarhere]

Skip tests that require libtiff if it is not installed, fixes 1866
[wiredfool]

Skip test when icc profile is not available, fixes 1887
[doko42]

Make deprecated functions raise NotImplementedError instead of Exception. 1862, 1890
[daniel-leicht, radarhere]

Replaced os.system with subprocess.call in setup.py 1879
[radarhere]

Corrected Image show documentation 1886
[radarhere]

Added check for executable permissions to ImageShow 1880
[radarhere]

Fixed tutorial code and added explanation 1877
[radarhere]

Added OS X support for ImageGrab grabclipboard 1837
[radarhere]

Combined duplicate code in ImageTk 1856
[radarhere]

Added --disable-platform-guessing option to setup.py build extension, 1861
[angeloc]

Fixed loading Transparent PNGs with a transparent black color 1840
[olt]

Add support for LA mode in Image.fromarray 1865
[pierriko]

Make ImageFile load images in read-only mode 1864
[hdante]

Added _accept hook for XVThumbImagePlugin 1853
[radarhere]

Test TIFF with LZW compression 1855, TGA RLE file 1854
[hugovk]

Improved SpiderImagePlugin help text 1863
[radarhere]

Updated Sphinx project description 1870
[radarhere]

Remove support for Python 3.0 from _imaging.c 1851
[radarhere]

Jpeg qtables are unsigned chars 1814, 1921
[thebostik]

Added additional EXIF tags 1841, TIFF Tags 1821
[radarhere]

Changed documentation to refer to ImageSequence Iterator 1833
[radarhere]

Fix Fedora prerequisites in installation docs, depends script 1842
[living180]

Added _accept hook for PixarImagePlugin 1843
[radarhere]

Removed outdated scanner classifier 1823
[radarhere]

Combined identical error messages in _imaging 1825
[radarhere]

Added debug option for setup.py to trace header and library finding 1790
[wiredfool]

Fix doc building on travis 1820, 1844
[wiredfool]

Fix for DIB/BMP images 1813, 1847
[wiredfool]

Add PixarImagePlugin file extension 1809
[radarhere]

Catch struct.errors when verifying png files 1805
[wiredfool]

SpiderImagePlugin: raise an error when seeking in a non-stack file 1794
[radarhere, jmichalon]

Added Support for 2/4 bpp Tiff Grayscale Images 1789
[zwhfly]

Removed unused variable from selftest 1788
[radarhere]

Added warning for as_dict method (deprecated in 3.0.0) 1799
[radarhere]

Removed powf support for older Python versions 1784
[radarhere]

Health fixes 1625 1903
[radarhere]

3.2.0

Added install docs for Fedora 23 and FreeBSD 1729, 1739, 1792
[koobs, zandermartin, wiredfool]

Fixed TIFF multiframe load when the frames have different compression types 1782
[radarhere, geka000]

Added copy method to Image 1772
[radarhere]

Updated dates in PIL license in OleFileIO README 1787
[radarhere]

Corrected Tiff tag names 1786
[radarhere]

Fixed documented name of JPEG property 1783
[radarhere]

Fixed UnboundLocalError when loading a corrupt jpeg2k file 1780
[wiredfool]

Fixed integer overflow in path.c 1773
[wiredfool, nedwill]

Added debug to command line help text for pilprint 1766
[radarhere]

Expose many more fields in ICC Profiles 1756
[lambdafu]

Documentation changes, URL update, transpose, release checklist
[radarhere]

Fixed saving to nonexistant files specified by pathlib.Path objects, fixes 1747
[radarhere]

Round Image.crop arguments to the nearest integer, fixes 1744
[hugovk]

Fix uninitialized variable warning in _imaging.c:getink, fixes 486
[wiredfool]

Disable multiprocessing install on cygwin, fixes 1690
[wiredfool]

Fix the error reported when libz is not found 1764
[wiredfool]

More general error check to avoid Symbol not found: _PyUnicodeUCS2_AsLatin1String on OS X 1761
[wiredfool]

Added py35 to tox envlist 1724
[radarhere]

Fix EXIF tag name typos 1736
[zarlant, radarhere]

Updated freetype to 2.6.3, Tk/Tcl to 8.6.5 and 8.5.19
[radarhere]

Add a loader for the FTEX format from Independence War 2: Edge of Chaos 1688
[jleclanche]

Improved alpha_composite documentation 1698
[radarhere]

Extend ImageDraw.text method to pass on multiline_text method specific arguments 1647
[radarhere]

Allow ImageSequence to seek to zero 1686
[radarhere]

ImageSequence Iterator is now an iterator 1649
[radarhere]

Updated windows test builds to jpeg9b
[radarhere]

Fixed support for .gbr version 1 images, added support for version 2 in GbrImagePlugin 1653
[wiredfool]

Clarified which YCbCr format is used 1677
[radarhere]

Added TiffTags documentation, Moved windows build documentation to winbuild/ 1667
[wiredfool]

Add tests for OLE file based formats 1678
[radarhere]

Add TIFF IFD test 1671
[radarhere]

Add a basic DDS image plugin with more tests 1654
[jleclanche, hugovk, wiredfool]

Fix incorrect conditional in encode.c 1638
[manisandro]

3.1.2

Fixed an integer overflow in Jpeg2KEncode.c causing a buffer overflow. CVE-2016-3076
[wiredfool]

django-floppyforms 1.6.1 -> 1.6.2

1.6.2


* `169`_: Use the attributes ``ClearableFileInput.initial_text``,
 ``ClearableFileInput.input_text``,
 ``ClearableFileInput.clear_checkbox_label`` to determine the used text in the
 template. This was inconsistent so far with Django&#39;s behaviour.

.. _169: https://github.com/gregmuellegger/django-floppyforms/issues/169

django-test-plus 1.0.12 -> 1.0.14

1.0.14

Fixed documentation typo

Added response_400() test

Added Guinslym and David Arcos to AUTHORS.txt

1.0.13

Added response_401() test

Fixed situation where User models without a 'username' field could not be
used as easily. Now credential field is automatically determined.

Fixed assertLoginRequired when settings.LOGIN_URL is a named URL pattern

Removed support for Django 1.4.x as it is well beyond it's end of life and causes a headache for supporting newer releases

django-test-plus 1.0.12 -> 1.0.14

1.0.14

Fixed documentation typo

Added response_400() test

Added Guinslym and David Arcos to AUTHORS.txt

1.0.13

Added response_401() test

Fixed situation where User models without a 'username' field could not be
used as easily. Now credential field is automatically determined.

Fixed assertLoginRequired when settings.LOGIN_URL is a named URL pattern

Removed support for Django 1.4.x as it is well beyond it's end of life and causes a headache for supporting newer releases

whitenoise 2.0.6 -> 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

3.0

.. note:: The latest version of WhiteNoise contains some small breaking changes.
Most users will be able to upgrade without any problems, but some
less-used APIs have been modified:

The setting WHITENOISE_GZIP_EXCLUDE_EXTENSIONS has been renamed to
WHITENOISE_SKIP_COMPRESS_EXTENSIONS.

The CLI :ref:compression utility <cli-utility> has moved from python -m whitenoise.gzip
to python -m whitenoise.compress.

The now redundant gzipstatic management command has been removed.

WhiteNoise no longer uses the system mimetypes files, so if you are serving
particularly obscure filetypes you may need to add their mimetypes explicitly
using the new :any:mimetypes <WHITENOISE_MIMETYPES> setting.

Older versions of Django (1.4-1.7) and Python (2.6) are no longer supported.
If you need support for these platforms you can continue to use WhiteNoise 2.x_.

The whitenoise.django.GzipManifestStaticFilesStorage storage backend
has been moved to
whitenoise.storage.CompressedManifestStaticFilesStorage. The old
import path will continue to work for now, but users are encouraged
to update their code to use the new path.

.. _WhiteNoise 2.x: http://whitenoise.evans.io/en/legacy-2.x/

Simpler, cleaner Django middleware integration
++++++++++++++++++++++++++++++++++++++++++++++

WhiteNoise can now integrate with Django by adding a single line to
MIDDLEWARE_CLASSES without any need to edit wsgi.py. This also means
that WhiteNoise plays nicely with other middleware classes such as
SecurityMiddleware, and that it is fully compatible with the new Channels_
system. See the :ref:updated documentation <django-middleware> for details.

.. _Channels: https://channels.readthedocs.org/en/latest/

Brotli compression support
++++++++++++++++++++++++++

Brotli_ is the modern, more efficient
alternative to gzip for HTTP compression. To benefit from smaller files and
faster page loads, just add the brotlipy_ library to your
requirements.txt and WhiteNoise will take care of the rest. See the
:ref:documentation <brotli-compression> for details.

.. _brotli: https://en.wikipedia.org/wiki/Brotli
.. _brotlipy: http://brotlipy.readthedocs.org/en/latest/

Simpler customisation
+++++++++++++++++++++

It's now possibe to add custom headers to WhiteNoise without needing to create
a subclass, using the new :any:add_headers_function <WHITENOISE_ADD_HEADERS_FUNCTION> setting.

Use WhiteNoise in development with Django
+++++++++++++++++++++++++++++++++++++++++

There's now an option to force Django to use WhiteNoise in development, rather
than its own static file handling. This results in more consistent behaviour
between development and production environments and fewer opportunities for
bugs and surprises. See the :ref:documentation <runserver-nostatic> for
details.

Improved mimetype handling
++++++++++++++++++++++++++

WhiteNoise now ships with its own mimetype definitions (based on those shipped
with nginx) instead of relying on the system ones, which can vary between
environments. There is a new :any:mimetypes <WHITENOISE_MIMETYPES>
configuration option which makes it easy to add additional type definitions if
needed.

Thanks
++++++

A big thank-you to Ed Morley <https://github.com/edmorley>_ and Tim Graham <https://github.com/timgraham>_ for their contributions to this release.

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 GH-214.

raven -> 5.21.0

5.21.0

Add formatted attribute to message events

Fill in empty filename if django fails to give one for
template information on newer Django versions with disabled
debug mode.

5.20.0

fixed an error that could cause certain SQL queries to fail to
record as breadcrumbs if no parameters were supplied.

5.19.0

remove duration from SQL query breadcrumbs. This was not rendered
in the UI and will come back in future versions of Sentry with a
different interface.

resolved a bug that caused crumbs to be recorded incorrectly.

5.18.0

Breadcrumbs are now attempted to be deduplicated to catch some common
cases where log messages just spam up the breadcrumbs.

Improvements to the public breadcrumbs API and stabilized some.

Automatically activate the context on calls to merge

5.17.0

if breadcrumbs fail to process due to an error they are now skipped.

5.16.0

exc_info is no longer included in logger based breadcrumbs.

log the entire logger name as category.

added a enable_breadcrumbs flag to the client to allow the enabling or
disabling of breadcrumbs quickly.

corrected an issue where python interpreters with bytecode writing enabled
would report incorrect logging locations when breadcrumb patching for
logging was enabled.

5.15.0

Improve thread binding for the context. This makes the main thread never
deactivate the client automatically on clear which means that more code
should automatically support breadcrumbs without changes.

5.14.0

Added support for reading git sha's from packed references.

Detect disabled thread support for uwsgi.

Added preliminary support for breadcrumbs.

Note: this version adds breadcrumbs to events. This means that if you run a
Sentry version older than 8.5 you will see some warnings in the UI. Consider
using an older version of the client if you do not want to see it.

5.13.0

Resolved an issue where Raven would fail with an exception if the
package name did not match the setuptools name in some isolated
cases.

5.12.0

Empty and otherwise falsy (None, False, 0) DSN values are now assumed
to be equivalent to no DSN being provided.

5.11.2

Added a workaround for back traceback objects passed to raven. In these
cases we now wobble further along to at least log something.

5.11.1

The raven client supports the stacktrace to be absent. This improves support
with celery and multiprocessing.

5.11.0

Client.configure_logging has been removed, and handlers will not automatically
be added to 'sentry' and 'raven' namespaces.

Improved double error check

Restored support for exc_info is True.

5.10.2

Remember exceptions in flight until the context is cleared so that two
reports with the same exception data do not result in two errors
being logged.

Allow logging exclusions.

5.10.1

Fixed a problem where bytes as keys in dictionaries caused problems
on data sanitization if those bytes were outside of the ASCII range.

Django client no longer requires the user object to be a subclass
of the base model.

Corrected an issue with the Django log handler which would cause a recursive import.

5.10.0

Restore template debug support for Django 1.9 and newer.

Correctly handle SSL verification disabling for newer Python versions.

5.9.2

Correct behavior introduced for Django 1.9.

5.9.1

Support for isolated apps in Django 1.9.

5.9.0

The threaded worker will now correctly handle forking.

The 'environment' parameter is now supported (requires a Sentry 8.0 server ).

'tags' can now be specified as part of a LoggingHandler's constructor.

5.8.0

Added support for detecting release on Heroku.

pkg_resources is now prioritized for default version detection.

Updated in_app support to include exception frames.

Fixed support for SENTRY_USER_ATTRS in Flask.

Handle DSNs which are sent as unicode values in Python 2.

5.7.2

Handle passing fingerprint through logging handler.

5.7.1

Correctly handle SHAs in .git/HEAD.

Fixed several cases of invalid Python3 syntax.

5.7.0

Reverted changes to Celery which incorrectly caused some configurations
to log unwanted messages.

Improved behavior in fetch_git_sha.

Removed is_authenticated property from most integrations.

Better error handling for errors within Flask context.

Support for new versions of Flask-Login.

Update Tornado support for modern versions.

Update stacktrace truncation code to match current versions of Sentry server.

5.6.0

Content is no longer base64-encoded.

fingerprint is now correctly supported.

Django: 1.9 compatibility.

Celery: Filter celery.redirect logger.

5.5.0

Added sys.excepthook handler (installed by default).

Fixed an issue where wrap_wsgi wasn't being respected.

Various deprecated code removed.

5.4.4

Enforce string-type imports.

5.4.3

Python 3 compatibility fixes.

5.4.2

Remove scheme checking on transports.

Added SENTRY_TRANSPORT to Flask and Django configurations.

5.4.1

Fixed packaging of 5.4.0 which erronously kept the aiohttp.py file in the wheel only.

5.4.0

Binding transports via a scheme prefix on DSNs is now deprecated.

raven.conf.load has been removed.

Upstream-related configuration (such as url, project_id, and keys) is now contained in RemoteConfig
attached to Client.remote

The aiohttp transport has been moved to raven-aiohttp package.

5.3.1

Restored support for patching Django's BaseCommand.execute.

5.3.0

The UDP transport has been removed.

The integrated Sentry+Django client has been removed. This is now part of Sentry core.

Server configuration must now be specified with a DSN.

Upstream errors now have increased verbosity in logs.

Unsent events now log to 'sentry.errors.uncaught'.

Django management commands should now effectively autopatch (when run from the CLI).

Flask wrapper now includes user_context, tags_context, and extra_context helpers.

Python version is now reported with modules.

5.2.0

Protocol version is now 6 (requires Sentry 7.0 or newer).

Added release option to Client.

Added fetch_git_sha helper.

Added fetch_package_version helper.

Added cookie string sanitizing.

Added threaded request transport: "threaded+requests+http(s)".

5.1.0

Added aiohttp transport.

Corrected behavior with auto_log_stacks and exceptions.

Add support for certifi.

Expanded Flask support.

Expanded Django support.

Corrected an issue where processors were not correctly applying.

5.0.0

Sentry client protocol is now version 5.

Various improvements to threaded transport.

4.2.0

SSL verification is now on by default.

Rate limits and other valid API errors are now handled more gracefully.

Added last_event_id and X-Sentry-ID header to Flask.

4.1.0

Added verify_ssl option to HTTP transport (defaults to False).

Added capture_locals option (defaults to True).

message can now be passed to capture* functions.

Django <1.4 is no longer supported.

Function object serialization has been improved.

SanitizePasswordsProcessor removes API keys.

4.0.0

Sentry client protocol is now version 4.

3.6.0

This changelog does not attempt to account for all changes between 3.6.0 and 3.0.0, but
rather focuses on recent important changes

Transport modules paths have been refactored.

The threaded transport is now the default.

Client.context has changed. Please see documentation for new API.

Client.user_context was added.

Client.http_context was added.

Client.extra_context was added.

Client.tags_context was added.

Flask support has been greatly improved.

raven.contrib.celery.Client has been removed as it was invalid.

3.0.0

3.0

version 3 of the protocol.

Support includes:

Sending 'python' as the platform.

The 'tags' option (on all constructors that support options).

Updated authentication header.

Additionally, the following has changed:

Configuring the client with an empty DSN value will disable sending of messages.

All clients should now check Client.is_enabled() to verify if they should send data.

Client.create_from_text and Client.create_from_exception have been removed.

Client.message and Client.exception have been removed.

The key setting has been removed.

The DEBUG setting in Django no longer disables Raven.

The register_signals option in RAVEN_CONFIG (Django) is no longer used.

A new helper, Client.context() is now available for scoping options.

Client.captureExceptions is now deprecated in favor of Client.context.

Credit card values will now be sanitized with the default processors.

A new eventlet+http transport exists.

A new threaded+http transport exists.

PyPy is now supported.

Django 1.5 should now be supported (experimental).

Gevent 1.0 should now be supported (experimental).

Python 2.5 is no longer supported.

[Django] The skip_sentry attribute is no longer supported. A new option config option has replaced this: SENTRY_IGNORE_EXCEPTIONS.

2.0.0

New serializers exist (and can be registered) against Raven. See raven.utils.serializer for more information.

You can now pass tags to the capture method. This will require a Sentry server compatible with the new
tags protocol.

A new gevent+http transport exists.

A new tornado+http transport exists.

A new twisted+http transport exists.

Zope integration has been added. See docs for more information.

PasteDeploy integration has been added. See docs for more information.

A Django endpoint now exists for proxying requests to Sentry. See raven.contrib.django.views for more information.

1.9.0

Signatures are no longer sent with messages. This requires the server version to be at least 4.4.6.

Several fixes and additions were added to the Django report view.

long types are now handled in transform().

Improved integration with Celery (and django-celery) for capturing errors.

1.8.0

There is now a builtin view as part of the Django integration for sending events server-side
(from the client) to Sentry. The view is currently undocumented, but is available as {% url raven-report %}
and will use your server side credentials. To use this view you'd simply swap out the servers configuration in
raven-js and point it to the given URL.

A new middleware for ZeroRPC now exists.

A new protocol for registering transports now exists.

Corrected some behavior in the UDP transport.

Celery signals are now connected by default within the Django integration.

1.7.0

The password sanitizer will now attempt to sanitize key=value pairs within strings (such as the querystring).

Two new santiziers were added: RemoveStackLocalsProcessor and RemovePostDataProcessor

1.6.0

Stacks must now be passed as a list of tuples (frame, lineno) rather than a list of frames. This
includes calls to logging (extra={'stack': []}), as well as explicit client calls (capture(stack=[])).

This corrects some issues (mostly in tracebacks) with the wrong lineno being reported for a frame.

1.4.0

Raven now tracks the state of the Sentry server. If it receives an error, it will slow down
requests to the server (by passing them into a named logger, sentry.errors), and increasingly
delay the next try with repeated failures, up to about a minute.

1.3.6

gunicorn is now disabled in default logging configuration

1.3.5

Moved exception and message methods to capture{Exception,Message}.

Added captureQuery method.

1.3.4

Corrected duplicate DSN behavior in Django client.

1.3.3

Django can now be configured by setting SENTRY_DSN.

Improve logging for send_remote failures (and correct issue created when
send_encoded was introduced).

Renamed SantizePassworsProcessor to SanitizePassworsProcessor.

1.3.2

Support sending the culprit with logging messages as part of extra.

1.3.1

Added client.exception and client.message shortcuts.

1.3.0

Refactored client send API to be more easily extensible.

MOAR TESTS!

1.2.2

Gracefully handle exceptions in Django client when using integrated
setup.

Added Client.error_logger as a new logger instance that points to
sentry.errors.

1.2.1

Corrected behavior with raven logging errors to send_remote
which could potentially cause a very large backlog to Sentry
when it should just log to sentry.errors.

Ensure the site argument is sent to the server.

1.2.0

Made DSN a first-class citizen throughout Raven.

Added a Pylons-specific WSGI middleware.

Improved the generic WSGI middleware to capture HTTP information.

Improved logging and logbook handlers.

1.1.6

Corrected logging stack behavior so that it doesnt capture raven+logging
extensions are part of the frames.

1.1.5

Remove logging attr magic.

1.1.4

Correct encoding behavior on bool and float types.

1.1.3

Fix 'request' attribute on Django logging.

1.1.2

Corrected logging behavior with extra data to match pre 1.x behavior.

1.1.1

Handle frames that are missing f_globals and f_locals.

Stricter conversion of int and boolean values.

Handle invalid sources for templates in Django.

1.1.0

varmap was refactored to send keys back to callbacks.

SanitizePasswordProcessor now handles http data.

1.0.5

Renaming raven2 to raven as it causes too many issues.

1.0.4

Corrected a bug in setup_logging.

Raven now sends "sentry_version" header which is the expected
server version.

1.0.3

Handle more edge cases on stack iteration.

1.0.2

Gracefully handle invalid f_locals.

1.0.1

All datetimes are assumed to be utcnow() as of Sentry 2.0.0-RC5

1.0.0

Now only works with Sentry>=2.0.0 server.

Raven is now listed as raven2 on PyPi.

0.8.0

raven.contrib.celery is now useable.

raven.contrib.django.celery is now useable.

Fixed a bug with request.raw_post_data buffering in Django.

0.7.1

Servers would stop iterating after the first successful post which was not the
intended behavior.

0.7.0

You can now explicitly pass a list of frame objects to the process method.

0.6.1

The default logging handler (SentryHandler) will now accept a set of kwargs to instantiate
a new client with (set server_name #10).

Fixed a bug with checksum generation when module or function were missing (Cleanning redundant files generated by cookiecutter-django #9).

0.6.0

Added a Django-specific WSGI middleware.

0.5.1

Two minor fixes for the Django client:

Ensure the sentry key exists in data in (Fix for dockerhub automated builds #8).

properly set kwargs['data'] to an empty list when its a NoneType (Added travis and gitter badges #6).

0.5.0

Require servers on base Client.

Added support for the site option in Client.

Moved raven.contrib.django.logging to raven.contrib.django.handlers.

0.4.0

Fixed an infinite loop in iter_tb.

0.3.0

Removed the thrashed key in request.sentry for the Django integration.

Changed the logging handler to correctly inherit old-style classes (Add a Gitter chat badge to README.md #1).

Added a client argument to raven.contrib.django.models.get_client().

0.2.0

auto_log_stacks now works with create_from_text

added Client.get_ident

0.1.0

Initial version of Raven (extracted from django-sentry 1.12.1).

opbeat -> 3.3.4

3.3.4

Introduce transactions ignore patterns.

3.3.3

fixed an issue where Opbeat for Flask would listen for all signals, instead
of just signals from the app it has been initialized with. Thanks tomlinton
for the fix.

fixed an encoding issue when loading the README.rst in setup.py. Thanks
apuyou for the fix.

3.3.2

removed suprious print statement that made it into 3.3.1. Thanks coagulant for
the heads up!

updated README

3.3.1

setting PROCESSORS to an empty list now skips processing completely instead
of using the default processors

setting _opbeat_transaction_name on the request object from a view or
middleware allows code to override the name used for the transaction

experimental support for manylinux1 binary wheels. Note that the wheels will
not be uploaded to PyPI for now, but will be available on the
release page
on GitHub.

3.3

added an asyncio transport (for Python 3.5 and up), thanks ticosax!

fixed a bug with uWSGI master mode which would stop the module from sending
errors to Opbeat if it was used before uWSGI forked the worker processes.
Thanks dsanders11 for finding the bug and initial patch!

3.2.2

fixed bug in MySQL instrumentation: SQL instrumentation can break queries with no arguments in certain edgecases opbeat/opbeat_python#94

fixed bug in requests instrumentation: The requests instrumentation swallows exceptions opbeat/opbeat_python#95

3.2.1

added a FILTER_EXCEPTION_TYPES attribute in the OPBEAT dict in Django / Flask settings
that allows the user to filter out specific exception types

3.2

prefixed Django and Flask transaction names with HTTP methods names

Note: This means views in the "Views" list on the Opbeat performance tab will
change their name and you will have both non-prefixed names and http method
prefixed names in the list until the old names fall out of the selected timeframe

3.1.4

added possibility to override the transport class used by the client

fixed a regression in our frame walker for Django templates in Django 1.9+

3.1.3

fixed an issue where SSL connections would not get closed on the client

added support for OPBEAT_WRAPT_EXTENSIONS to override building of the
wrapt C extension module during installation.

3.1.2

preliminary support for Django 1.9

support for Python 3.5

added OPBEAT_DISABLE_SEND environment variable to completely stop sending
data to Opbeat

improved test suite

3.1.1

Fixed bug in Redis instrumentation introduced in 3.1 refactor.

3.1

Flask APM support. Install as opbeat[flask] to ensure flask deps are installed.

Introduce opbeat.trace decorator for better insights into custom code

Internal refactoring to support the decorator.

Stop instrumenting pipelined Redis operations.

3.0.4

Only log one line per module we failed to instrument

3.0.3

Fix a problem that occurs when end_transaction gets called twice in a row

Silently ignore DatabaseError when collecting user info for Django.

Better error logging with async=True

Renamed async keyword in anticipation of Python 3.5+

Instruments Django middleware by default to give better insights in APM

Better sanitation of http body

A bit of cleanups and refactoring

3.0.2

Fix a bug in trace reporting that occurred if the traced code would raise

Introduce a management command to test out local Opbeat configuration and
send a test exception.

Include templates in stackframes in traces.

Various bug fixes related to stackframes in traces.

3.0.1

instrument python-memcached

Make sure only one of urllib3 and requests will show up on traces

3.0

introduced instrumentation to enable in-depth performance monitoring

began deprecation of camelCase style capture methods on `Client.
Full deprecation in 4.0.

2.1.1

refactored AyncWorker, should now be better behaved when shutting down

fixed bug with django-configurations

2.1

fixed issue with template debug in Django 1.9 (unreleased)

added experimental support for instrumenting Django middleware for
better metrics data

2.0.4

fixed bug with Django and DEBUG = True

2.0.3

fixed bug in collecting Django POST data

2.0.2

start using the new intake URL

Flask: module now adheres to the Flask.debug option and does not log to
Opbeat unless it is False

2.0.1

Fixed a bug when __name__ does not exist for view_func given to
OpbeatAPMMiddleware

2.0

Async support was refactored, removed old AsyncClient classes

OpbeatAPMMiddleware was added to time requests

APP_ID now configurable from environment

Lots of cleanups

1.9.0

Signatures are no longer sent with messages. This requires the server version to be at least 4.4.6.

Several fixes and additions were added to the Django report view.

long types are now handled in transform().

Improved integration with Celery (and django-celery) for capturing errors.

1.8.0

There is now a builtin view as part of the Django integration for sending events server-side
(from the client) to Sentry. The view is currently undocumented, but is available as {% url raven-report %}
and will use your server side credentials. To use this view you'd simply swap out the servers configuration in
raven-js and point it to the given URL.

A new middleware for ZeroRPC now exists.

A new protocol for registering transports now exists.

Corrected some behavior in the UDP transport.

Celery signals are now connected by default within the Django integration.

1.7.0

The password sanitizer will now attempt to sanitize key=value pairs within strings (such as the querystring).

Two new santiziers were added: RemoveStackLocalsProcessor and RemovePostDataProcessor

1.6.0

Stacks must now be passed as a list of tuples (frame, lineno) rather than a list of frames. This
includes calls to logging (extra={'stack': []}), as well as explicit client calls (capture(stack=[])).

This corrects some issues (mostly in tracebacks) with the wrong lineno being reported for a frame.

1.4

added preliminary support for Django 1.8

dropped support for Django 1.3

When using Django, only try to submit user data if django.contrib.auth is
installed. Thanks nickbruun for the report and fix!

1.4.0

raven now tracks the state of the Sentry server. If it receives an error, it will slow down
requests to the server (by passing them into a named logger, sentry.errors), and increasingly
delay the next try with repeated failures, up to about a minute.

1.3.6

gunicorn is now disabled in default logging configuration

1.3.5

Moved exception and message methods to capture{Exception,Message}.

Added captureQuery method.

1.3.4

Corrected duplicate DSN behavior in Django client.

1.3.3

Django can now be configured by setting SENTRY_DSN.

Improve logging for send_remote failures (and correct issue created when
send_encoded was introduced).

Renamed SantizePassworsProcessor to SanitizePassworsProcessor.

1.3.2

Support sending the culprit with logging messages as part of extra.

1.3.1

Added client.exception and client.message shortcuts.

1.3

added support for Django 1.7

dropped support for Django 1.2

switched from nosetests to py.test

1.3.0

Refactored client send API to be more easily extensible.

MOAR TESTS!

1.2.2

Gracefully handle exceptions in Django client when using integrated
setup.

Added Client.error_logger as a new logger instance that points to
sentry.errors.

1.2.1

Corrected behavior with raven logging errors to send_remote
which could potentially cause a very large backlog to Sentry
when it should just log to sentry.errors.

Ensure the site argument is sent to the server.

1.2.0

Made DSN a first-class citizen throughout raven.

Added a Pylons-specific WSGI middleware.

Improved the generic WSGI middleware to capture HTTP information.

Improved logging and logbook handlers.

1.2

support for Python 3

1.1.6

Corrected logging stack behavior so that it doesnt capture raven+logging
extensions are part of the frames.

1.1.5

Remove logging attr magic.

1.1.4

Correct encoding behavior on bool and float types.

1.1.3

Fix 'request' attribute on Django logging.

1.1.2

Corrected logging behavior with extra data to match pre 1.x behavior.

1.1.1

Handle frames that are missing f_globals and f_locals.

Stricter conversion of int and boolean values.

Handle invalid sources for templates in Django.

1.1

Renamed from opbeat_python to opbeat.

Simplified configuration

Conform to the updated Opbeat API.

1.1.0

varmap was refactored to send keys back to callbacks.

SanitizePasswordProcessor now handles http data.

1.0.5

Renaming raven2 to raven as it causes too many issues.

1.0.4

Corrected a bug in setup_logging.

raven now sends "sentry_version" header which is the expected
server version.

1.0.3

Handle more edge cases on stack iteration.

1.0.2

Gracefully handle invalid f_locals.

1.0.1

All datetimes are assumed to be utcnow() as of Sentry 2.0.0-RC5

1.0.0

Now only works with Sentry>=2.0.0 server.

raven is now listed as raven2 on PyPi.

1.0

Changes to conform to the Opbeat API.

Forked from Raven 1.9.0

0.8.0

raven.contrib.celery is now useable.

raven.contrib.django.celery is now useable.

Fixed a bug with request.raw_post_data buffering in Django.

0.7.1

Servers would stop iterating after the first successful post which was not the
intended behavior.

0.7.0

You can now explicitly pass a list of frame objects to the process method.

0.6.1

The default logging handler (SentryHandler) will now accept a set of kwargs to instantiate
a new client with (set server_name #10).

Fixed a bug with checksum generation when module or function were missing (Cleanning redundant files generated by cookiecutter-django #9).

0.6

Added a Django-specific WSGI middleware.

0.5.1

Two minor fixes for the Django client:

Ensure the sentry key exists in data in (Fix for dockerhub automated builds #8).

properly set kwargs['data'] to an empty list when its a NoneType (Added travis and gitter badges #6).

0.5

Require servers on base Client.

Added support for the site option in Client.

Moved raven.contrib.django.logging to raven.contrib.django.handlers.

0.4

Fixed an infinite loop in iter_tb.

0.3

Removed the thrashed key in request.sentry for the Django integration.

Changed the logging handler to correctly inherit old-style classes (Add a Gitter chat badge to README.md #1).

Added a client argument to raven.contrib.django.models.get_client().

0.2

auto_log_stacks now works with create_from_text

added Client.get_ident

0.1

Initial version of raven (extracted from django-sentry 1.12.1).

django-extensions 1.6.1 -> 1.6.7

1.6.7

Changes:

Fix: describe_form, fix No module named 'django.db.models.loading' error

Improvement: shell_plus, Add a setting to prefix all models in an application 887

Improvement: pipchecker, check for requirements-{dev,prod}.txt as well

Docs: pipchecker, update documentation

1.6.6

Changes:

Fix: admin_generator, fix for using all apps in Django <1.7

Fix: dump_script, fix for using all apps in Django <1.7

Fix: UniqueFieldMixin, resolve get_fields_with_model deprecation Django 1.10

Fix: runprofileserver, Fix call grind format to enable source code navigation in qcachegrind.

Docs: runserver_plus, add a little note about the debugger PIN.

1.6.5

Bumped version number since PyPi returns 500 errors while uploading packages :(

1.6.4

Changes:

Fix: jobs cache_cleanup, use caches instead of deprecated get_cache

Fix: ModificationDateTimeField, missing default value for update_modified

Fix: modelviz, use get_model_compat and look up missing app_label

Fix: modelviz, use get_models_for_app instead of get_models_compat

Fix: dumpscript, use list_app_labels instead of get_apps when no app_labels are given

Improvement: compat.py, move code from try to else block for Django 1.7+

Docstring: get_models_for_app, clearify argument

1.6.3

Bumped version number for incomplete PyPi uplaod

1.6.2

The long over due release :-)

Changes:

Fix: JsonFields, do not parse floats as decimals. This fixes bugs that causes
them to be returned as strings after multiple saves. Note that this can
be backwards incompatible !

Fix: use add_arguments() instead of option_list (Django 1.10)

Fix: create_command, Django 1.9 fixes

Fix: create_jobs, Django 1.9 fixes

Fix: RandomCharField, when not unique get the first value from the generator

Fix: graph_models, render() must be called with a dict

Fix: graph_models, use force_bytes fixes command for Python 3

Fix: graph_models, fix django 1.6 compatibility for strings defined relation

Fix: graph_models, fix settings.GRAPH_MODELS breaking the command

Fix: graph_models, add support for lazy relationships

Fix: ForeignKeyAutocompleteAdmin, url_patterns is just a list (Django 1.9+)

Fix: ForeignKeySearchInput, use url reversing instead of hardcoded paths

Fix: find_template, Fix for Django 1.8+

Fix: admin_generator, incompatible "default" identifier raising TypeError

Improvement: show_urls, add json and pretty-json formatting

Improvement: runserver_plus, add support for whitenoise

Improvement: ModificationDateTimeField, add parameter to preserve timestamps on save

Improvement: runprofileserver, raise command error when hotspot is not available

Improvement: reset_db, better parsing of mysql cnf file

Improvement: restored coverage for Python 3.2

Improvement: pep8 fixes, remove unused shims & imports & commented code

Improvement: graph_models, JSON output

Improvement: graph_models, add wildcard filters

Docs: removed text on donations, the hope was that we could generate some
funds to have more consistent development and outreach.

Docs: runserver_plus, added some documentation about LOGGING

Docs: runscript, update documentation to match Django tutorial for Django 1.8+

Docs: runprofileserver, add documentation on profiler choices

Docs: update_permissions, add basic documentation for command

pytest-sugar 0.5.1 -> 0.7.1

0.7.1

^^^^^^^^^^^^^^^^^^^

Fix issue with deselected tests

0.7.0

^^^^^^^^^^^^^^^^^^^

Show skipped tests

Changed failed test summary (try --new-summary option to test it out)

Show teardown errors

Add support for pytest-rerunfailedtests

Make test symbols customizable

Remove deprecated --nosugar.

0.6.0

^^^^^^^^^^^^^^^^^^^

pytest-xdist support

Turn off progress meter when progressbar_length=0

pytest-sugar 0.5.1 -> 0.7.1

0.7.1

^^^^^^^^^^^^^^^^^^^

Fix issue with deselected tests

0.7.0

^^^^^^^^^^^^^^^^^^^

Show skipped tests

Changed failed test summary (try --new-summary option to test it out)

Show teardown errors

Add support for pytest-rerunfailedtests

Make test symbols customizable

Remove deprecated --nosugar.

0.6.0

^^^^^^^^^^^^^^^^^^^

pytest-xdist support

Turn off progress meter when progressbar_length=0

django-allauth 0.24.1 -> 0.25.2

0.25.2

Note worthy changes

Bug fix release (MemcachedKeyCharacterError: "Control characters not allowed")

0.25.1

Note worthy changes

Bug fix release (AttributeError in password reset view).

0.25.0

Note worthy changes

Many providers were added: Reddit, Untappd, GitLab, Stripe,
Pinterest, Shopify, Draugiem, DigitalOcean, Robinhood,
Bitbucket(OAuth2).

The account connections view is now AJAX aware.

You can now customize the template extension that is being used to
render all HTML templates (ACCOUNT_TEMPLATE_EXTENSION)

In order to be secure by default, users are now blocked from logging
in after exceeding a maximum number of failed login attempts (see
ACCOUNT_LOGIN_ATTEMPTS_LIMIT,
ACCOUNT_LOGIN_ATTEMPTS_TIMEOUT). Set
ACCOUNT_LOGIN_ATTEMPTS_LIMIT to None to disable this
functionality. Important: while this protects the allauth login view, it
does not protect Django's admin login from being brute forced.

New translations: Arabic, Lithuanian

Backwards incompatible changes

None

coverage 4.0.3 -> 4.1

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

coverage 4.0.3 -> 4.1

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-redis 4.3.0 -> 4.4.3

4.4.3

Date: 2016-05-17

Fix minor ttl inconsistencies.

4.4.2

Date: 2016-04-21

Fix timeout bug (thanks to skorokithakis)

4.4.1

Date: 2016-04-13

Add additional check for avoid wrong exception on get_redis_connection.

4.4.0

Date: 2016-04-12

Make redis client pluggable (thanks to arnuschky)

Add version number inside python module (thanks to BertrandBordage)

Fix clear method (thanks to ostcar)

Add the ability to specify key prefix on delete and delete_pattern.

BREAKING CHANGE: improved compression support (make it more plugable).

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! 🤖

jayfk · 2016-07-06T18:52:01Z

Renaming the issue caused the bot to create pull requests for each update. This isn't in the docs, so sorry for the noise!

perduta · 2016-07-06T19:35:39Z

I'm sure noise is on side of this project. :)

śr., 6 lip 2016, 20:52 użytkownik Jannis Gebauer notifications@github.com
napisał:

Renaming the issue caused the bot to create pull requests for each update.
This isn't in the docs, so sorry for the noise!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SpisTresci/SpisTresci/pull/47#issuecomment-230868906,
or mute the thread
https://github.com/notifications/unsubscribe/ARgtu698syd526KvptX9Dsa8EfbJL6Hmks5qS_lTgaJpZM4JFJ-N
.

noisy · 2016-07-06T19:50:24Z

@jayfk are you the author of @pyup-bot? :) I didn't know that :) I have noticed this bot on django-cookiecutter project ;)

BTW. If repository on github blocks possibility of merging not rebased branches (as this repository), @pyup-bot should automatically rebase a branch when it is necessary.

jayfk · 2016-07-07T09:25:58Z

@jayfk are you the author of @pyup-bot? :) I didn't know that :) I have noticed this bot on django-cookiecutter project ;)

Yes, I've created the bot a while ago :)

BTW. If repository on github blocks possibility of merging not rebased branches (as this repository), @pyup-bot should automatically rebase a branch when it is necessary.

I agree, that'd be a great feature. In the meantime you can just close the PR and delete the branch, the bot will create a new PR for you (this won't work for the inital PR though).

Update ipdb from 0.9.0 to 0.10.1 Update gevent from 1.1rc5 to 1.1.1 Update pillow from 3.1.1 to 3.3.0 Update django from 1.9.4 to 1.9.7 Update django-floppyforms from 1.6.1 to 1.6.2 Pin sphinx to latest version 1.4.4 Update django-test-plus from 1.0.12 to 1.0.14 Update django-test-plus from 1.0.12 to 1.0.14 Update gitpython from 1.0.2 to 2.0.6 Update whitenoise from 2.0.6 to 3.2 Update colorlog from 2.6.3 to 2.7.0 Update django-model-utils from 2.4 to 2.5 Update gunicorn from 19.4.5 to 19.6.0 Pin raven to latest version 5.21.0 Pin opbeat to latest version 3.3.4 Update django-extensions from 1.6.1 to 1.6.7 Update boto from 2.39.0 to 2.41.0 Update celery from 3.1.21 to 3.1.23 Update django-braces from 1.8.1 to 1.9.0 Update pytest-sugar from 0.5.1 to 0.7.1 Update pytest-sugar from 0.5.1 to 0.7.1 Update werkzeug from 0.11.4 to 0.11.9 Update django-coverage-plugin from 1.2.2 to 1.3.1 Update django-coverage-plugin from 1.2.2 to 1.3.1 Update django-allauth from 0.24.1 to 0.25.2 Update factory-boy from 2.6.1 to 2.7.0 Update factory-boy from 2.6.1 to 2.7.0 Update coverage from 4.0.3 to 4.1 Update coverage from 4.0.3 to 4.1 Update django-redis from 4.3.0 to 4.4.3

noisy changed the title ~~Initial Update~~ Requirements - Initial Update Jul 5, 2016

noisy closed this Jul 8, 2016

noisy deleted the pyup-initial-update branch July 8, 2016 17:36

noisy restored the pyup-initial-update branch July 8, 2016 17:40

noisy reopened this Jul 8, 2016

noisy force-pushed the pyup-initial-update branch from ecbcdc1 to c46b78b Compare July 8, 2016 17:41

noisy force-pushed the pyup-initial-update branch from c46b78b to af4fdf5 Compare July 8, 2016 17:44

noisy closed this Oct 19, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Requirements - Initial Update #47

Requirements - Initial Update #47

pyup-bot commented Jul 5, 2016

jayfk commented Jul 6, 2016

perduta commented Jul 6, 2016

noisy commented Jul 6, 2016 •

edited

Loading

jayfk commented Jul 7, 2016

Requirements - Initial Update #47

Requirements - Initial Update #47

Conversation

pyup-bot commented Jul 5, 2016

Updates

Pins

Changelogs

ipdb 0.9.0 -> 0.10.1

0.10.1

0.10.0

0.9.4

0.9.3

0.9.2

0.9.1

gevent 1.1rc5 -> 1.1.1

1.1.1

1.1.0

Pillow 3.1.1 -> 3.3.0

3.3.0

3.2.0

3.1.2

django-floppyforms 1.6.1 -> 1.6.2

1.6.2

django-test-plus 1.0.12 -> 1.0.14

1.0.14

1.0.13

django-test-plus 1.0.12 -> 1.0.14

1.0.14

1.0.13

whitenoise 2.0.6 -> 3.2

3.2

3.1

3.0

A big thank-you to Ed Morley &lt;https://github.com/edmorley&gt;_ and Tim Graham &lt;https://github.com/timgraham&gt;_ for their contributions to this release.

django-model-utils 2.4 -> 2.5

2.5

raven -> 5.21.0

5.21.0

5.20.0

5.19.0

5.18.0

5.17.0

5.16.0

5.15.0

5.14.0

5.13.0

5.12.0

5.11.2

5.11.1

5.11.0

5.10.2

5.10.1

5.10.0

5.9.2

5.9.1

5.9.0

5.8.0

5.7.2

5.7.1

5.7.0

5.6.0

5.5.0

5.4.4

5.4.3

5.4.2

5.4.1

5.4.0

5.3.1

5.3.0

5.2.0

5.1.0

5.0.0

4.2.0

4.1.0

4.0.0

3.6.0

3.0.0

3.0

2.0.0

1.9.0

A big thank-you to `Ed Morley <https://github.com/edmorley>`_ and `Tim Graham <https://github.com/timgraham>`_ for their contributions to this release.