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	1.9.4	1.10.1
coverage	4.0.3	4.2
lxml	3.6.0	3.6.3
django-braces	1.8.1	1.9.0
django-mailgun	0.8.0	0.9.1
uwsgi	2.0.12	2.0.13.1
pinax-stripe	3.0.0	3.2.1
PyJWT	1.4.0	1.4.2
raven	5.11.1	5.27.1
psycopg2	2.6.1	2.6.2
certifi	2016.2.28	2016.8.31
setuptools	20.3.1	27.3.0
requests-mock	0.7.0	1.1.0
django-model-utils	2.4	2.6
pytz	2016.2	2016.6.1
django-extensions	1.6.1	1.7.4
factory-boy	2.6.1	2.7.0
ipdb	0.9.0	0.10.1
python-dateutil	2.5.1	2.5.3
requests	2.8.1	2.11.1
django-allauth	0.25.2	0.27.0
flake8	2.5.4	3.0.4
django-debug-toolbar	1.4	1.5
django-floppyforms	1.6.0	1.7.0
django-test-plus	1.0.12	1.0.15
django-redis	4.3.0	4.4.4
flower	0.9.0	0.9.1

Changelogs

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

lxml 3.6.0 -> 3.6.3

3.6.3

• release without source changes to provide cleanly built Linux wheels

3.6.2

• release without source changes to provide cleanly built Linux wheels

3.6.1

Features added

• GH180: Separate option inline_style for Cleaner that only removes style
  attributes instead of all styles. Patch by Christian Pedersen.
• GH196: Windows build support for Python 3.5. Contribution by Maximilian Hils.

Bugs fixed

• GH199: Exclude file fields from FormElement.form_values (as browsers do).
  Patch by Tomas Divis.
• GH198, LP1568167: Try to provide base URL from Resolver.resolve_string().
  Patch by Michael van Tellingen.
• GH191: More accurate float serialisation in objectify.FloatElement.
  Patch by Holger Joukl.
• LP1551797: Repair XSLT error logging. Patch by Marcus Brinkmann.

PyJWT 1.4.0 -> 1.4.2

1.4.2

1.4.1

raven 5.11.1 -> 5.27.1

5.27.0

---

• Updated CA bundle.
• Added transaction-based culprits for Celery, Django, and Flask.
• Fixed an issue where ignore_exceptions wasn't respected.

5.26.0

---

• Fixed potential concurrency issue with event IDs in the Flask integration.
• Added a workaround for leakage when broken WSGI middlware or servers are
  used that do not call close() on the iterat.r

5.25.0

---

• Added various improvements for the WSGI and Django support.
• Prevent chained exception recursion
• In environments which look like AWS Lambda or Google App Engine utilize the
  synchronous transport.
• Added Celery config option to ignore expected exceptions
• Improved DSN handling in Flask client.

5.24.0

---

• Added support for Django 1.10.
• Added support for chained exceptions in Python 3.
• Fixed various behavior with handling template errors in Django 1.8+.

5.23.0

---

• Sentry failures now no longer log the failure data in the error
  message.

5.22.0

---

• Fixed template reporting not working for certain versions of Django.

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.

setuptools 20.3.1 -> 27.3.0

27.3.0

---

• 794: In test command, add installed eggs to PYTHONPATH
  when invoking tests so that subprocesses will also have the
  dependencies available. Fixes tox 330 <https://github.com/tox-dev/tox/issues/330>_.
• 795: Update vendored pyparsing 2.1.9.

27.2.0

---

• 520 and 513: Suppress ValueErrors in fixup_namespace_packages
  when lookup fails.
• Nicer, more consistent interfaces for msvc monkeypatching.

27.1.2

---

• 779 via 781: Fix circular import.

27.1.1

---

• 778: Fix MSVC monkeypatching.

27.1.0

---

• Introduce the (private) monkey module to encapsulate
  the distutils monkeypatching behavior.

27.0.0

---

• Now use Warehouse by default for
  upload, patching distutils.config.PyPIRCCommand to
  affect default behavior.

  Any config in .pypirc should be updated to replace

  https://pypi.python.org/pypi/

  with

  https://upload.pypi.org/legacy/

  Similarly, any passwords stored in the keyring should be
  updated to use this new value for "system".

  The upload_docs command will continue to use the python.org
  site, but the command is now deprecated. Users are urged to use
  Read The Docs instead.

• 776: Use EXT_SUFFIX for py_limited_api renaming.

• 774 and 775: Use LegacyVersion from packaging when
  detecting numpy versions.

26.1.1

---

• Re-release of 26.1.0 with pytest pinned to allow for automated
  deployement and thus proper packaging environment variables,
  fixing issues with missing executable launchers.

26.1.0

---

• 763: pkg_resources.get_default_cache now defers to the
  appdirs project <https://pypi.org/project/appdirs>_ to
  resolve the cache directory. Adds a vendored dependency on
  appdirs to pkg_resources.

26.0.0

---

• 748: By default, sdists are now produced in gzipped tarfile
  format by default on all platforms, adding forward compatibility
  for the same behavior in Python 3.6 (See Python 27819).
• 459 via 736: On Windows with script launchers,
  sys.argv[0] now reflects
  the name of the entry point, consistent with the behavior in
  distlib and pip wrappers.
• 752 via 753: When indicating py_limited_api to Extension,
  it must be passed as a keyword argument.

25.4.0

---

• Add Extension(py_limited_api=True). When set to a truthy value,
  that extension gets a filename apropriate for code using Py_LIMITED_API.
  When used correctly this allows a single compiled extension to work on
  all future versions of CPython 3.
  The py_limited_api argument only controls the filename. To be
  compatible with multiple versions of Python 3, the C extension
  will also need to set -DPy_LIMITED_API=... and be modified to use
  only the functions in the limited API.

25.3.0

---

• 739 Fix unquoted libpaths by fixing compatibility between numpy.distutils and distutils._msvccompiler for numpy < 1.11.2 (Fix issue 728, error also fixed in Numpy).
• 731: Bump certifi.
• Style updates. See 740, 741, 743, 744, 742, 747.
• 735: include license file.

25.2.0

---

• 612 via 730: Add a LICENSE file which needs to be provided by the terms of
  the MIT license.

25.1.6

---

• 725: revert library_dir_option patch (Error is related to numpy.distutils and make errors on non Numpy users).

25.1.5

---

• 720
• 723: Improve patch for library_dir_option.

25.1.4

---

• 717
• 713
• 707: Fix Python 2 compatibility for MSVC by catching errors properly.
• 715: Fix unquoted libpaths by patching library_dir_option.

25.1.3

---

• 714 and 704: Revert fix as it breaks other components
  downstream that can't handle unicode. See 709, 710,
  and 712.

25.1.2

---

• 704: Fix errors when installing a zip sdist that contained
  files named with non-ascii characters on Windows would
  crash the install when it attempted to clean up the build.
• 646: MSVC compatibility - catch errors properly in
  RegistryInfo.lookup.
• 702: Prevent UnboundLocalError when initial working_set
  is empty.

25.1.1

---

• 686: Fix issue in sys.path ordering by pkg_resources when
  rewrite technique is "raw".
• 699: Fix typo in msvc support.

25.1.0

---

• 609: Setuptools will now try to download a distribution from
  the next possible download location if the first download fails.
  This means you can now specify multiple links as dependency_links
  and all links will be tried until a working download link is encountered.

25.0.2

---

• 688: Fix AttributeError in setup.py when invoked not from
  the current directory.

25.0.1

---

• Cleanup of setup.py script.
• Fixed documentation builders by allowing setup.py
  to be imported without having bootstrapped the
  metadata.
• More style cleanup. See 677, 678, 679, 681, 685.

25.0.0

---

• 674: Default sys.path manipulation by easy-install.pth
  is now "raw", meaning that when writing easy-install.pth
  during any install operation, the sys.path will not be
  rewritten and will no longer give preference to easy_installed
  packages.

  To retain the old behavior when using any easy_install
  operation (including setup.py install when setuptools is
  present), set the environment variable:

  SETUPTOOLS_SYS_PATH_TECHNIQUE=rewrite

  This project hopes that that few if any environments find it
  necessary to retain the old behavior, and intends to drop
  support for it altogether in a future release. Please report
  any relevant concerns in the ticket for this change.

24.3.1

---

• 398: Fix shebang handling on Windows in script
  headers where spaces in sys.executable would
  produce an improperly-formatted shebang header,
  introduced in 12.0 with the fix for 188.
• 663, 670: More style updates.

24.3.0

---

• 516: Disable os.link to avoid hard linking
  in sdist.make_distribution, avoiding errors on
  systems that support hard links but not on the
  file system in which the build is occurring.

24.2.1

---

• 667: Update Metadata-Version to 1.2 when
  python_requires is supplied.

24.2.0

---

• 631: Add support for python_requires keyword.

24.1.1

---

• More style updates. See 660, 661, 641.

24.1.0

---

• 659: setup.py now will fail fast and with a helpful
  error message when the necessary metadata is missing.
• More style updates. See 656, 635, 640,
  644, 650, 652, and 655.

24.0.3

---

• Updated style in much of the codebase to match
  community expectations. See 632, 633, 634,
  637, 639, 638, 642, 648.

24.0.2

---

• If MSVC++14 is needed setuptools.msvc now redirect
  user to Visual C++ Build Tools web page.

24.0.1

---

• 625 and 626: Fixes on setuptools.msvc mainly
  for Python 2 and Linux.

24.0.0

---

• Pull Request 174: Add more aggressive support for
  standalone Microsoft Visual C++ compilers in
  msvc9compiler patch.
  Particularly : Windows SDK 6.1 and 7.0
  (MSVC++ 9.0), Windows SDK 7.1 (MSVC++ 10.0),
  Visual C++ Build Tools 2015 (MSVC++14)
• Renamed setuptools.msvc9_support to
  setuptools.msvc.

23.2.1

---

Re-release of v23.2.0, which was missing the intended
commits.

• 623: Remove used of deprecated 'U' flag when reading
  manifests.

23.1.0

---

• 619: Deprecated tag_svn_revision distribution
  option.

23.0.0

---

• 611: Removed ARM executables for CLI and GUI script
  launchers on Windows. If this was a feature you cared
  about, please comment in the ticket.
• 604: Removed docs building support. The project
  now relies on documentation hosted at
  https://setuptools.readthedocs.io/.

22.0.5

---

• 604: Restore repository for upload_docs command
  to restore publishing of docs during release.

22.0.4

---

• 589: Upload releases to pypi.io using the upload
  hostname and legacy path.

22.0.3

---

• 589: Releases are now uploaded to pypi.io (Warehouse)
  even when releases are made on Twine via Travis.

22.0.2

---

• 589: Releases are now uploaded to pypi.io (Warehouse).

22.0.1

---

• 190: On Python 2, if unicode is passed for packages to
  build_py command, it will be handled just as with
  text on Python 3.

22.0.0

---

Intended to be v21.3.0, but jaraco accidentally released as
a major bump.

• 598: Setuptools now lists itself first in the User-Agent
  for web requests, better following the guidelines in
  RFC 7231 <https://tools.ietf.org/html/rfc7231section-5.5.3>_.

21.2.2

---

• Minor fixes to changelog and docs.

21.2.1

---

• 261: Exclude directories when resolving globs in
  package_data.

21.2.0

---

• 539: In the easy_install get_site_dirs, honor all
  paths found in site.getsitepackages.

21.1.0

---

• 572: In build_ext, now always import _CONFIG_VARS
  from distutils rather than from sysconfig
  to allow distutils.sysconfig.customize_compiler
  configure the OS X compiler for -dynamiclib.

21.0.0

---

• Removed ez_setup.py from Setuptools sdist. The
  bootstrap script will be maintained in its own
  branch and should be generally be retrieved from
  its canonical location at
  https://bootstrap.pypa.io/ez_setup.py.

20.10.0

---

• 553: egg_info section is now generated in a
  deterministic order, matching the order generated
  by earlier versions of Python. Except on Python 2.6,
  order is preserved when existing settings are present.
• 556: Update to Packaging 16.7, restoring support
  for deprecated python_implmentation marker.
• 555: Upload command now prompts for a password
  when uploading to PyPI (or other repository) if no
  password is present in .pypirc or in the keyring.

20.9.0

---

• 548: Update certify version to 2016.2.28
• 545: Safely handle deletion of non-zip eggs in rotate
  command.

20.8.1

---

• Issue 544: Fix issue with extra environment marker
  processing in WorkingSet due to refactor in v20.7.0.

20.8.0

---

• Issue 543: Re-release so that latest release doesn't
  cause déjà vu with distribute and setuptools 0.7 in
  older environments.

20.7.0

---

• Refactored extra environment marker processing
  in WorkingSet.
• Issue 533: Fixed intermittent test failures.
• Issue 536: In msvc9_support, trap additional exceptions
  that might occur when importing
  distutils.msvc9compiler in mingw environments.
• Issue 537: Provide better context when package
  metadata fails to decode in UTF-8.

20.6.8

---

• Issue 523: Restored support for environment markers,
  now honoring 'extra' environment markers.

20.6.7

---

• Issue 523: Disabled support for environment markers
  introduced in v20.5.

20.6.6

---

• Issue 503: Restore support for PEP 345 environment
  markers by updating to Packaging 16.6.

20.6.0

---

• New release process that relies on
  bumpversion <https://github.com/peritus/bumpversion>_
  and Travis CI for continuous deployment.
• Project versioning semantics now follow
  semver <https://semver.org>_ precisely.
  The 'v' prefix on version numbers now also allows
  version numbers to be referenced in the changelog,
  e.g. https://pythonhosted.org/setuptools/history.htmlv20-6-0.

20.5

---

• BB Pull Request 185, 470: Add support for environment markers
  in requirements in install_requires, setup_requires,
  tests_require as well as adding a test for the existing
  extra_requires machinery.

20.4

---

• Issue 422: Moved hosting to
  Github <https://github.com/pypa/setuptools>_
  from Bitbucket <https://bitbucket.org/pypa/setuptools>_.
  Issues have been migrated, though all issues and comments
  are attributed to bb-migration. So if you have a particular
  issue or issues to which you've been subscribed, you will
  want to "watch" the equivalent issue in Github.
  The Bitbucket project will be retained for the indefinite
  future, but Github now hosts the canonical project repository.

django-model-utils 2.4 -> 2.6

2.5.2

---

• Include runtests.py in sdist.

2.5.1

---

• Fix InheritanceQuerySet raising an AttributeError exception
  under Django 1.9.
• Django 1.10 support regressed with changes between pre-alpha and final
  release; 1.10 currently not supported.

django-extensions 1.6.1 -> 1.7.4

1.7.3

---

Changes:

• Fix: ForeignKeySearchInput, fix bug with constructing search_path urls
• Docs: runscript, fix runscript example
• Deprecation: JSONField, Django now includes JSONField our field is now deprecated

1.7.2

---

Changes:

• Fix: passwd, Update passwd command up to Django>=1.8
• Improvement: shell_plus, add settings.SHELL_PLUS_PRINT_SQL config option
• Improvement: shell_plus, allow to specifies the connection file to use if using the --kernel option

1.7.1

---

Changes:

• Fix: sqldiff, fix optional app_label arguments
• Fix: runscript, remove args from command class
• Doc: runscript, remove = from --script-args example

1.7.0

---

The "Letting go of the past" release.

From this moment on Django Extensions requires version 1.8 or higher.
A lot of work has been done to remove old backwards compatibility code and
make sure that Django Extensions uses the current Django API's. This should
result in better and easier to maintain code (and hopefully less bugs :).

This release touches a lot of code if you have any issues please report them
at https://github.com/django-extensions/django-extensions/issues

We still need more tests to make sure we don't break people's projects when
refactoring. If you have some spare time please contribute tests !

Changes:

• Cleanup: removing backwards compatibility hacks for (now) unsupported versions of Django
• Cleanup: use six instead of home grown functions
• Fix: AutoSlugField, allow_duplicates didn't set slug value to model instance
• Fix: MongoDB fields, verbose_name on mongoengine fields does not seem to be supported
• Fix: MongoDB fields, fix relative import problem with json.py
• Improvement: Start using pre-commit
• Improvement: syncdata, Replace custom transaction logic with transaction.atomic
• Improvement: Django 1.10, use from_db_value instead of models.SubfieldBase
• Improvement: print_user_session, support for non standard user model
• Improvement: widont, tests to work with py2 and py3
• Improvement: runserver_plus, prevent 2nd reload of debugger on runserver_plus
• Improvement: runserver_plus, prevent killing the server when request.META values are evaluated
• Improvement: reset_db, add argument to make closing sessions optional
• Improvement: print_settings, Fix positional arguments
• Improvement: runscript, migrate to argparse and add_arguments
• Improvement: graph_models, do not rely on .models_module for inclusion in output
• Improvement: jsonfield, fix issues with mutable default
• Docs: Convert readthedocs links for their .org -> .io migration

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

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]

python-dateutil 2.5.1 -> 2.5.3

2.5.2

---

• Updated zoneinfo to 2016c
• Fixed parser bug where yearfirst and dayfirst parameters were not being
  respected when no separator was present. (gh issue 81 and 217, pr 229)

requests 2.8.1 -> 2.11.1

2.11.1

+++++++++++++++++++

Bugfixes

• Fixed a bug when using iter_content with decode_unicode=True for
  streamed bodies would raise AttributeError. This bug was introduced in
  2.11.
• Strip Content-Type and Transfer-Encoding headers from the header block when
  following a redirect that transforms the verb from POST/PUT to GET.

2.11.0

+++++++++++++++++++

Improvements

• Added support for the ALL_PROXY environment variable.
• Reject header values that contain leading whitespace or newline characters to
  reduce risk of header smuggling.

Bugfixes

• Fixed occasional TypeError when attempting to decode a JSON response that
  occurred in an error case. Now correctly returns a ValueError.
• Requests would incorrectly ignore a non-CIDR IP address in the NO_PROXY
  environment variables: Requests now treats it as a specific IP.
• Fixed a bug when sending JSON data that could cause us to encounter obscure
  OpenSSL errors in certain network conditions (yes, really).
• Added type checks to ensure that iter_content only accepts integers and
  None for chunk sizes.
• Fixed issue where responses whose body had not been fully consumed would have
  the underlying connection closed but not returned to the connection pool,
  which could cause Requests to hang in situations where the HTTPAdapter
  had been configured to use a blocking connection pool.

Miscellaneous

• Updated bundled urllib3 to 1.16.
• Some previous releases accidentally accepted non-strings as acceptable header values. This release does not.

2.10.0

+++++++++++++++++++

New Features

• SOCKS Proxy Support! (requires PySocks; $ pip install requests[socks])

Miscellaneous

• Updated bundled urllib3 to 1.15.1.

2.9.2

++++++++++++++++++

Improvements

• Change built-in CaseInsensitiveDict (used for headers) to use OrderedDict
  as its underlying datastore.

Bugfixes

• Don't use redirect_cache if allow_redirects=False
• When passed objects that throw exceptions from tell(), send them via
  chunked transfer encoding instead of failing.
• Raise a ProxyError for proxy related connection issues.

2.9.1

++++++++++++++++++

Bugfixes

• Resolve regression introduced in 2.9.0 that made it impossible to send binary
  strings as bodies in Python 3.
• Fixed errors when calculating cookie expiration dates in certain locales.

Miscellaneous

• Updated bundled urllib3 to 1.13.1.

2.9.0

++++++++++++++++++

Minor Improvements (Backwards compatible)

• The verify keyword argument now supports being passed a path to a
  directory of CA certificates, not just a single-file bundle.
• Warnings are now emitted when sending files opened in text mode.
• Added the 511 Network Authentication Required status code to the status code
  registry.

Bugfixes

• For file-like objects that are not seeked to the very beginning, we now
  send the content length for the number of bytes we will actually read, rather
  than the total size of the file, allowing partial file uploads.
• When uploading file-like objects, if they are empty or have no obvious
  content length we set Transfer-Encoding: chunked rather than
  Content-Length: 0.
• We correctly receive the response in buffered mode when uploading chunked
  bodies.
• We now handle being passed a query string as a bytestring on Python 3, by
  decoding it as UTF-8.
• Sessions are now closed in all cases (exceptional and not) when using the
  functional API rather than leaking and waiting for the garbage collector to
  clean them up.
• Correctly handle digest auth headers with a malformed qop directive that
  contains no token, by treating it the same as if no qop directive was
  provided at all.
• Minor performance improvements when removing specific cookies by name.

Miscellaneous

• Updated urllib3 to 1.13.

django-allauth 0.25.2 -> 0.27.0

0.27.0

---

Note worthy changes

• Django 1.10 compatibility.
• The Twitter and GitHub providers now support querying of the email address.

Backwards incompatible changes

• When ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was turned on, the e-mail field key
  changed from email to email1, which could introduce subtle bugs. This
  has now been changed: there always is an email field, and optionally an
  email2 field.
• The "You must type the same password each time" form validation error that can
  be triggered during signup is now added to the password2 field instead of
  being added to the non field errors.
• The email_confirmation_sent signal is now passed request,
  confirmation and signup instead of only the confirmation.
• ACCOUNT_PASSWORD_MIN_LENGTH was already deprecated, but is now completely
  ignored if AUTH_PASSWORD_VALIDATORS is not empty.

0.26.1

---

Note worthy changes

• Locale files wrongly packaged, fixed.
• Fixed bug (KeyError) when ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was set to
  True.

0.26.0

---

Note worthy changes

• New providers: Weixin, Battle.net, Asana, Eve Online, 23andMe, Slack
• Django's password validation mechanism (see AUTH_PASSWORD_VALIDATORS) is now
  used to validate passwords.
• By default, email confirmations are no longer stored in the
  database. Instead, the email confirmation mail contains an HMAC
  based key identifying the email address to confirm. The verification
  lookup includes a fallback to the previous strategy so that there is
  no negative impact on pending verification emails.
• A new setting ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was added, requiring users to
  input their email address twice. The setting
  ACCOUNT_SIGNUP_PASSWORD_VERIFICATION has been renamed to
  ACCOUNT_SIGNUP_PASSWORD_ENTER_TWICE.
• New translations: Latvian, Kyrgyz.

Backwards incompatible changes

• Dropped support for Django 1.6
• In order to accomodate for Django's password validation, the
  clean_password method of the adapter now takes an (optional)
  user parameter as its second argument.
• The new HMAC based keys may contain colons. If you have forked
  account/urls.py, be sure to sync the account_confirm_email
  pattern.

django-debug-toolbar 1.4 -> 1.5

1.5

---

This version is compatible with Django 1.10 and requires Django 1.8 or later.

Support for Python 3.2 is dropped.

Bugfixes

* Restore compatibility with sqlparse ≥ 0.2.0.
* Add compatibility with Bootstrap 4, Pure CSS, MDL, etc.
* Improve compatibility with RequireJS / AMD.
* Improve the UI slightly.
* Fix invalid (X)HTML.

django-floppyforms 1.6.0 -> 1.7.0

1.7.0

* `171`_: Fix path to GIS widget images in ``openlayers.html`` template. The
 files coming with Django admin where used, but the naming changed in 1.9. We
 vendor these know to have better control over it.
* `174`_: Support for setting your own Google Maps key in the
 ``BaseGMapWidget``. `See the documentation
 <http://django-floppyforms.readthedocs.io/en/latest/geodjango.html>`_ for
 details

.. _171: https://github.com/gregmuellegger/django-floppyforms/issues/171
.. _174: https://github.com/gregmuellegger/django-floppyforms/pull/174



### 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's behaviour.

.. _169: jazzband/django-floppyforms#169

1.6.1

* `167`_: Fix django-floppyforms' ``CheckboxInput.value_from_datadict`` which
 was inconsistent with Django's behaviour.

.. _167: https://github.com/gregmuellegger/django-floppyforms/issues/167

django-test-plus 1.0.12 -> 1.0.15

1.0.15

---

• Added helper methods for more HTTP methods like put, patch, and trace
• Added assertResponseContains and assertResponseNotContains

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

4.4.4

---

Date: 2016-07-25

• Fix possible race condition on incr implementation using
  lua script (thanks to prokaktus).

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