Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Update #60

Closed
wants to merge 13 commits into from
Closed

Initial Update #60

wants to merge 13 commits into from

Conversation

pyup-bot
Copy link
Collaborator

@pyup-bot pyup-bot commented Aug 3, 2017

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

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

codecov 2.0.9 » 2.0.9 PyPI | Changelog | Repo
mock 1.0.0 » 2.0.0 PyPI | Repo
coverage 4.0.3 » 4.4.1 PyPI | Changelog | Docs
hiro 0.5 » 0.5 PyPI | Docs
termcolor 1.1.0 » 1.1.0 PyPI | Homepage
six 1.10.0 » 1.10.0 PyPI | Changelog | Homepage | Docs
ordereddict 1.1 » 1.1 PyPI | Homepage
jira 1.0.10 » 1.0.10 PyPI | Changelog | Repo | Docs
requests 2.18.3 » 2.18.3 PyPI | Changelog | Homepage
argparse 1.4.0 » 1.4.0 PyPI | Changelog | Repo
suds-jurko 0.6 » 0.6 PyPI | Repo
keyring 10.4.0 » 10.4.0 PyPI | Changelog | Repo
keyrings.alt 2.2 » 2.2 PyPI | Changelog | Repo

Changelogs

codecov -> 2.0.9

2.0.7

  • Add --name/-n to cli
  • Add support for Jenkins Blue
  • Fix environment variable joining
  • Add Greenhouse CI detection
  • Fix GitLab detection
  • Add default VCS_* environment
  • Auto-merge py-coverage
  • Remove Xcode processing support, please use bash uploader.
  • Support yaml:token and yaml:slug

2.0.5

2.0.4

  • fix detecting merge commits on all CI, not just Travis

2.0.3

  • add -F to flagging uploads [new feature]
  • fixed some reports ascii chars
  • added --pr flag for manually specifing pulls
  • added --tag flag for manually git tags
  • added env detection for Travis
  • added buildkite detection
  • added teamcity detection
  • added more snapci detection
  • detect codecov.yml file detection
  • depreciating xcode support, use bash uploader
  • hide token from stdout

1.6.4

  • fix gitlab project directory
  • fallback on git branch/commit
  • fix using gcov_exec

1.6.0

  • depreciate --no-fail now a default
  • add --required to fail the build if Codecov fails
  • added --cacerts for enterprise customers
  • added fix reports http://bit.ly/1O4eBpt

1.5.0

  • fix retreiving mercurial commit
  • add support for swift/xcode7 profdata
  • now uploading direct-to-s3 to improve product performance
  • not require branch, will default to master (the default branch)
  • fix drone.io commit number, which is not a full 40 sha.

1.4.1

  • added --no-fail to prevent failing builds when missing configuration or Codecov errors

1.4.0

  • Ignore other known bad files/paths
  • Added test suite to test against example repositories
  • Using coverage xml -i to ignore No source for code errors
  • Cleaned up command output with help and colors
  • Added gcov processing, see codecov --help for more info.

1.3.1

  • Ignore other known bad files/paths
  • Fix issue with decoding files in py3+

1.3.0

  • Refactor project to be a global uploader for more reports

1.2.3

  • Remove test-results.xml, not a coverage file
  • Add CircleCI container numbers

1.2.2

  • bring back client-side pre-processing for jacoco (they can crush)

1.2.1

  • accept any file ending in coverge.xml

1.2.0

  • accept nosetests.xml and test-results.xml files
  • no longer do client side pre-processing, upload raw
  • capture SEMAPHORE_CURRENT_THREAD

1.1.13

  • added --build arg for advanced usage

1.1.10

  • fix package for 2.6 on windows
  • fix showing --help when called in non-git backed repo
  • fix AppVeyor public repos

1.1.8

  • support GitLab CI Runner
  • added rollbar to help bugs if presented
  • added more filepath matching
  • pep8 cleanup
  • added Shippable ci

1.1.7

  • support for D lang added, special thanks to ColdenCullen
  • Wercker CI supported by Robpol86
  • fixed Drone build number

1.1.6

  • fix semaphore commit revision number
  • preprocess reports from xml

1.1.5

  • search for all lcov|gcov files
  • depreciate --min-coverage, use Github Status Update feature
  • pre-process xml => json

1.1.4

  • added support for pyhton 2.6 by Robpol86
  • added AppVeyor support by Robpol86

1.1.3

  • added more ignore paths

1.1.2

  • search for lcov.info files
  • pause for .1 before checking for min-coverage
  • accept --env variables which are stored in front-end for build specs

1.1.1

  • build python coverage xml only when no reports found to fix overriding reports
  • now defaulting output to plain text. Use --json to return json results
  • added jacocoTestReport.xml to search list
  • changed --min-coverage waiting methods to, 5 tries 15s each
  • added Sites/www/bower and node_modules to ignored table of contents

coverage 4.0.3 -> 4.4.1

4.4.1


  • No code changes: just corrected packaging for Python 2.7 Linux wheels.

.. _changes_44:

4.4


  • Reports could produce the wrong file names for packages, reporting pkg.py
    instead of the correct pkg/__init__.py. This is now fixed. Thanks, Dirk
    Thomas.
  • XML reports could produce <source> and <class> lines that together
    didn't specify a valid source file path. This is now fixed. (issue 526_)
  • Namespace packages are no longer warned as having no code. (issue 572_)
  • Code that uses sys.settrace(sys.gettrace()) in a file that wasn't being
    coverage-measured would prevent correct coverage measurement in following
    code. An example of this was running doctests programmatically. This is now
    fixed. (issue 575_)
  • Errors printed by the coverage command now go to stderr instead of
    stdout.
  • Running coverage xml in a directory named with non-ASCII characters would
    fail under Python 2. This is now fixed. (issue 573_)

.. _issue 526: https://bitbucket.org/ned/coveragepy/issues/526/generated-xml-invalid-paths-for-cobertura
.. _issue 572: https://bitbucket.org/ned/coveragepy/issues/572/no-python-source-warning-for-namespace
.. _issue 573: https://bitbucket.org/ned/coveragepy/issues/573/cant-generate-xml-report-if-some-source
.. _issue 575: https://bitbucket.org/ned/coveragepy/issues/575/running-doctest-prevents-complete-coverage

4.4b1


  • Some warnings can now be individually disabled. Warnings that can be
    disabled have a short name appended. The [run] disable_warnings setting
    takes a list of these warning names to disable. Closes both issue 96_ and
    issue 355_.
  • The XML report now includes attributes from version 4 of the Cobertura XML
    format, fixing issue 570_.
  • In previous versions, calling a method that used collected data would prevent
    further collection. For example, save(), report(), html_report(), and
    others would all stop collection. An explicit start() was needed to get it
    going again. This is no longer true. Now you can use the collected data and
    also continue measurement. Both issue 79_ and issue 448_ described this
    problem, and have been fixed.
  • Plugins can now find unexecuted files if they choose, by implementing the
    find_executable_files method. Thanks, Emil Madsen.
  • Minimal IronPython support. You should be able to run IronPython programs
    under coverage run, though you will still have to do the reporting phase
    with CPython.
  • Coverage.py has long had a special hack to support CPython's need to measure
    the coverage of the standard library tests. This code was not installed by
    kitted versions of coverage.py. Now it is.

.. _issue 79: https://bitbucket.org/ned/coveragepy/issues/79/save-prevents-harvesting-on-stop
.. _issue 96: https://bitbucket.org/ned/coveragepy/issues/96/unhelpful-warnings-produced-when-using
.. _issue 355: https://bitbucket.org/ned/coveragepy/issues/355/warnings-should-be-suppressable
.. _issue 448: https://bitbucket.org/ned/coveragepy/issues/448/save-and-html_report-prevent-further
.. _issue 570: https://bitbucket.org/ned/coveragepy/issues/570/cobertura-coverage-04dtd-support

.. _changes_434:

4.3.4


  • Fixing 2.6 in version 4.3.3 broke other things, because the too-tricky
    exception wasn't properly derived from Exception, described in issue 556_.
    A newb mistake; it hasn't been a good few days.

.. _issue 556: https://bitbucket.org/ned/coveragepy/issues/556/43-fails-if-there-are-html-files-in-the

.. _changes_433:

4.3.3


  • Python 2.6 support was broken due to a testing exception imported for the
    benefit of the coverage.py test suite. Properly conditionalizing it fixed
    issue 554_ so that Python 2.6 works again.

.. _issue 554: https://bitbucket.org/ned/coveragepy/issues/554/traceback-on-python-26-starting-with-432

.. _changes_432:

4.3.2


  • Using the --skip-covered option on an HTML report with 100% coverage
    would cause a "No data to report" error, as reported in issue 549_. This is
    now fixed; thanks, Loïc Dachary.
  • If-statements can be optimized away during compilation, for example, if 0:
    or if __debug__:. Coverage.py had problems properly understanding these
    statements which existed in the source, but not in the compiled bytecode.
    This problem, reported in issue 522_, is now fixed.
  • If you specified --source as a directory, then coverage.py would look for
    importable Python files in that directory, and could identify ones that had
    never been executed at all. But if you specified it as a package name, that
    detection wasn't performed. Now it is, closing issue 426_. Thanks to Loïc
    Dachary for the fix.
  • If you started and stopped coverage measurement thousands of times in your
    process, you could crash Python with a "Fatal Python error: deallocating
    None" error. This is now fixed. Thanks to Alex Groce for the bug report.
  • On PyPy, measuring coverage in subprocesses could produce a warning: "Trace
    function changed, measurement is likely wrong: None". This was spurious, and
    has been suppressed.
  • Previously, coverage.py couldn't start on Jython, due to that implementation
    missing the multiprocessing module (issue 551). This problem has now been
    fixed. Also, issue 322
    about not being able to invoke coverage
    conveniently, seems much better: jython -m coverage run myprog.py works
    properly.
  • Let's say you ran the HTML report over and over again in the same output
    directory, with --skip-covered. And imagine due to your heroic
    test-writing efforts, a file just acheived the goal of 100% coverage. With
    coverage.py 4.3, the old HTML file with the less-than-100% coverage would be
    left behind. This file is now properly deleted.

.. _issue 322: https://bitbucket.org/ned/coveragepy/issues/322/cannot-use-coverage-with-jython
.. issue 426: https://bitbucket.org/ned/coveragepy/issues/426/difference-between-coverage-results-with
.. issue 522: https://bitbucket.org/ned/coveragepy/issues/522/incorrect-branch-reporting-with-__debug

.. _issue 549: https://bitbucket.org/ned/coveragepy/issues/549/skip-covered-with-100-coverage-throws-a-no
.. _issue 551: https://bitbucket.org/ned/coveragepy/issues/551/coveragepy-cannot-be-imported-in-jython27

.. _changes_431:

4.3.1


  • Some environments couldn't install 4.3, as described in issue 540_. This is
    now fixed.
  • The check for conflicting --source and --include was too simple in a
    few different ways, breaking a few perfectly reasonable use cases, described
    in issue 541. The check has been reverted while we re-think the fix for
    issue 265
    .

.. _issue 540: https://bitbucket.org/ned/coveragepy/issues/540/cant-install-coverage-v43-into-under
.. _issue 541: https://bitbucket.org/ned/coveragepy/issues/541/coverage-43-breaks-nosetest-with-coverage

.. _changes_43:

4.3


Special thanks to Loïc Dachary, who took an extraordinary interest in
coverage.py and contributed a number of improvements in this release.

  • Subprocesses that are measured with automatic subprocess measurement_ used
    to read in any pre-existing data file. This meant data would be incorrectly
    carried forward from run to run. Now those files are not read, so each
    subprocess only writes its own data. Fixes issue 510_.
  • The coverage combine command will now fail if there are no data files to
    combine. The combine changes in 4.2 meant that multiple combines could lose
    data, leaving you with an empty .coverage data file. Fixes
    issue 525, issue 412, issue 516, and probably issue 511.
  • Coverage.py wouldn't execute sys.excepthook_ when an exception happened in
    your program. Now it does, thanks to Andrew Hoos. Closes issue 535_.
  • Branch coverage fixes:
  • Branch coverage could misunderstand a finally clause on a try block that
    never continued on to the following statement, as described in issue 493_. This is now fixed. Thanks to Joe Doherty for the report and Loïc
    Dachary for the fix.
  • A while loop with a constant condition (while True) and a continue
    statement would be mis-analyzed, as described in issue 496_. This is now
    fixed, thanks to a bug report by Eli Skeggs and a fix by Loïc Dachary.
  • While loops with constant conditions that were never executed could result
    in a non-zero coverage report. Artem Dayneko reported this in issue 502_, and Loïc Dachary provided the fix.
  • The HTML report now supports a --skip-covered option like the other
    reporting commands. Thanks, Loïc Dachary for the implementation, closing
    issue 433_.
  • Options can now be read from a tox.ini file, if any. Like setup.cfg, sections
    are prefixed with "coverage:", so [run] options will be read from the
    [coverage:run] section of tox.ini. Implements part of issue 519_.
    Thanks, Stephen Finucane.
  • Specifying both --source and --include no longer silently ignores the
    include setting, instead it fails with a message. Thanks, Nathan Land and
    Loïc Dachary. Closes issue 265_.
  • The Coverage.combine method has a new parameter, strict=False, to
    support failing if there are no data files to combine.
  • When forking subprocesses, the coverage data files would have the same random
    number appended to the file name. This didn't cause problems, because the
    file names had the process id also, making collisions (nearly) impossible.
    But it was disconcerting. This is now fixed.
  • The text report now properly sizes headers when skipping some files, fixing
    issue 524_. Thanks, Anthony Sottile and Loïc Dachary.
  • Coverage.py can now search .pex files for source, just as it can .zip and
    .egg. Thanks, Peter Ebden.
  • Data files are now about 15% smaller.
  • Improvements in the [run] debug setting:
  • The "dataio" debug setting now also logs when data files are deleted during
    combining or erasing.
  • A new debug option, "multiproc", for logging the behavior of
    concurrency=multiprocessing.
  • If you used the debug options "config" and "callers" together, you'd get a
    call stack printed for every line in the multi-line config output. This is
    now fixed.
  • Fixed an unusual bug involving multiple coding declarations affecting code
    containing code in multi-line strings: issue 529_.
  • Coverage.py will no longer be misled into thinking that a plain file is a
    package when interpreting --source options. Thanks, Cosimo Lupo.
  • If you try to run a non-Python file with coverage.py, you will now get a more
    useful error message. Issue 514_.
  • The default pragma regex changed slightly, but this will only matter to you
    if you are deranged and use mixed-case pragmas.
  • Deal properly with non-ASCII file names in an ASCII-only world, issue 533_.
  • Programs that set Unicode configuration values could cause UnicodeErrors when
    generating HTML reports. Pytest-cov is one example. This is now fixed.
  • Prevented deprecation warnings from configparser that happened in some
    circumstances, closing issue 530_.
  • Corrected the name of the jquery.ba-throttle-debounce.js library. Thanks,
    Ben Finney. Closes issue 505_.
  • Testing against PyPy 5.6 and PyPy3 5.5.
  • Switched to pytest from nose for running the coverage.py tests.
  • Renamed AUTHORS.txt to CONTRIBUTORS.txt, since there are other ways to
    contribute than by writing code. Also put the count of contributors into the
    author string in setup.py, though this might be too cute.

.. _sys.excepthook: https://docs.python.org/3/library/sys.htmlsys.excepthook
.. _issue 265: https://bitbucket.org/ned/coveragepy/issues/265/when-using-source-include-is-silently
.. _issue 412: https://bitbucket.org/ned/coveragepy/issues/412/coverage-combine-should-error-if-no
.. _issue 433: https://bitbucket.org/ned/coveragepy/issues/433/coverage-html-does-not-suport-skip-covered
.. _issue 493: https://bitbucket.org/ned/coveragepy/issues/493/confusing-branching-failure
.. _issue 496: https://bitbucket.org/ned/coveragepy/issues/496/incorrect-coverage-with-branching-and
.. _issue 502: https://bitbucket.org/ned/coveragepy/issues/502/incorrect-coverage-report-with-cover
.. _issue 505: https://bitbucket.org/ned/coveragepy/issues/505/use-canonical-filename-for-debounce
.. _issue 514: https://bitbucket.org/ned/coveragepy/issues/514/path-to-problem-file-not-reported-when
.. _issue 510: https://bitbucket.org/ned/coveragepy/issues/510/erase-still-needed-in-42
.. _issue 511: https://bitbucket.org/ned/coveragepy/issues/511/version-42-coverage-combine-empties
.. _issue 516: https://bitbucket.org/ned/coveragepy/issues/516/running-coverage-combine-twice-deletes-all
.. _issue 519: https://bitbucket.org/ned/coveragepy/issues/519/coverage-run-sections-in-toxini-or-as
.. _issue 524: https://bitbucket.org/ned/coveragepy/issues/524/coverage-report-with-skip-covered-column
.. _issue 525: https://bitbucket.org/ned/coveragepy/issues/525/coverage-combine-when-not-in-parallel-mode
.. _issue 529: https://bitbucket.org/ned/coveragepy/issues/529/encoding-marker-may-only-appear-on-the
.. _issue 530: https://bitbucket.org/ned/coveragepy/issues/530/deprecationwarning-you-passed-a-bytestring
.. _issue 533: https://bitbucket.org/ned/coveragepy/issues/533/exception-on-unencodable-file-name
.. _issue 535: https://bitbucket.org/ned/coveragepy/issues/535/sysexcepthook-is-not-called

.. _changes_42:

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

.. _changes_41:

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

.. _changes_403:

six -> 1.10.0

1.10.0


  • Issue 122: Improve the performance of six.int2byte on Python 3.
  • Pull request 55 and issue 99: Don't add the winreg module to six.moves
    on non-Windows platforms.
  • Pull request 60 and issue 108: Add six.moves.getcwd and
    six.moves.getcwdu.
  • Pull request 64: Add create_unbound_method to create unbound methods.

1.9.0


  • Issue 106: Support the flush parameter to six.print_.
  • Pull request 48 and issue 15: Add the python_2_unicode_compatible
    decorator.
  • Pull request 57 and issue 50: Add several compatibility methods for unittest
    assertions that were renamed between Python 2 and 3.
  • Issue 105 and pull request 58: Ensure six.wraps respects the updated and
    assigned arguments.
  • Issue 102: Add raise_from to abstract out Python 3's raise from syntax.
  • Issue 97: Optimize six.iterbytes on Python 2.
  • Issue 98: Fix six.moves race condition in multi-threaded code.
  • Pull request 51: Add six.view(keys|values|itmes), which provide dictionary
    views on Python 2.7+.
  • Issue 112: six.moves.reload_module now uses the importlib module on
    Python 3.4+.

1.8.0


  • Issue 90: Add six.moves.shlex_quote.
  • Issue 59: Add six.moves.intern.
  • Add six.urllib.parse.uses_(fragment|netloc|params|query|relative).
  • Issue 88: Fix add_metaclass when the class has __slots__ containing
    __weakref__ or __dict__.
  • Issue 89: Make six use absolute imports.
  • Issue 85: Always accept updated and assigned arguments for wraps().
  • Issue 86: In reraise(), instantiate the exception if the second argument is
    None.
  • Pull request 45: Add six.moves.email_mime_nonmultipart.
  • Issue 81: Add six.urllib.request.splittag mapping.
  • Issue 80: Add six.urllib.request.splituser mapping.

1.7.3


  • Issue 77: Fix import six on Python 3.4 with a custom loader.
  • Issue 74: six.moves.xmlrpc_server should map to SimpleXMLRPCServer on Python
    2 as documented not xmlrpclib.

1.7.2


  • Issue 72: Fix installing on Python 2.

1.7.1


  • Issue 71: Make the six.moves meta path importer handle reloading of the six
    module gracefully.

1.7.0


  • Pull request 30: Implement six.moves with a PEP 302 meta path hook.
  • Pull request 32: Add six.wraps, which is like functools.wraps but always sets
    the wrapped attribute.
  • Pull request 35: Improve add_metaclass, so that it doesn't end up inserting
    another class into the hierarchy.
  • Pull request 34: Add import mappings for dummy_thread.
  • Pull request 33: Add import mappings for UserDict and UserList.
  • Pull request 31: Select the implementations of dictionary iterator routines
    at import time for a 20% speed boost.

1.6.1


  • Raise an AttributeError for six.moves.X when X is a module not available in
    the current interpreter.

1.6.0


  • Raise an AttributeError for every attribute of unimportable modules.
  • Issue 56: Make the fake modules six.moves puts into sys.modules appear not to
    have a path unless they are loaded.
  • Pull request 28: Add support for SplitResult.
  • Issue 55: Add move mapping for xmlrpc.server.
  • Pull request 29: Add move for urllib.parse.splitquery.

1.5.2


  • Issue 53: Make the fake modules six.moves puts into sys.modules appear not to
    have a name unless they are loaded.

1.5.1


  • Issue 51: Hack around the Django autoreloader after recent six.moves changes.

1.5.0


  • Removed support for Python 2.4. This is because py.test no longer supports
    2.4.
  • Fix various import problems including issues 19 and 41. six.moves modules
    are now lazy wrappers over the underlying modules instead of the actual
    modules themselves.
  • Issue 49: Add six.moves mapping for tkinter.ttk.
  • Pull request 24: Add dir special method to six.moves modules.
  • Issue 47: Fix add_metaclass on classes with a string for the slots
    variable.
  • Issue 44: Fix interpretation of backslashes on Python 2 in the u() function.
  • Pull request 21: Add import mapping for urllib's proxy_bypass function.
  • Issue 43: Add import mapping for the Python 2 xmlrpclib module.
  • Issue 39: Add import mapping for the Python 2 thread module.
  • Issue 40: Add import mapping for the Python 2 gdbm module.
  • Issue 35: On Python versions less than 2.7, print_ now encodes unicode
    strings when outputing to standard streams. (Python 2.7 handles this
    automatically.)

1.4.1


  • Issue 32: urllib module wrappings don't work when six is not a toplevel file.

1.4.0


  • Issue 31: Add six.moves mapping for UserString.
  • Pull request 12: Add six.add_metaclass, a decorator for adding a metaclass to
    a class.
  • Add six.moves.zip_longest and six.moves.filterfalse, which correspond
    respectively to itertools.izip_longest and itertools.ifilterfalse on Python 2
    and itertools.zip_longest and itertools.filterfalse on Python 3.
  • Issue 25: Add the unichr function, which returns a string for a Unicode
    codepoint.
  • Issue 26: Add byte2int function, which complements int2byte.
  • Add a PY2 constant with obvious semantics.
  • Add helpers for indexing and iterating over bytes: iterbytes and indexbytes.
  • Add create_bound_method() wrapper.
  • Issue 23: Allow multiple base classes to be passed to with_metaclass.
  • Issue 24: Add six.moves.range alias. This exactly the same as the current
    xrange alias.
  • Pull request 5: Create six.moves.urllib, which contains abstractions for a
    bunch of things which are in urllib in Python 3 and spread out across urllib,
    urllib2, and urlparse in Python 2.

1.3.0


  • Issue 21: Add methods to access the closure and globals of a function.
  • In six.iter(items/keys/values/lists), passed keyword arguments through to the
    underlying method.
  • Add six.iterlists().
  • Issue 20: Fix tests if tkinter is not available.
  • Issue 17: Define callable to be builtin callable when it is available again
    in Python 3.2+.
  • Issue 16: Rename Python 2 exec_'s arguments, so casually calling exec_ with
    keyword arguments will raise.
  • Issue 14: Put the six.moves package in sys.modules based on the name six is
    imported under.
  • Fix Jython detection.
  • Pull request 4: Add email_mime_multipart, email_mime_text, and
    email_mime_base to six.moves.

1.2.0


  • Issue 13: Make iterkeys/itervalues/iteritems return iterators on Python 3
    instead of iterables.
  • Issue 11: Fix maxsize support on Jython.
  • Add six.next() as an alias for six.advance_iterator().
  • Use the builtin next() function for advance_iterator() where is available
    (2.6+), not just Python 3.
  • Add the Iterator class for writing portable iterators.

1.1.0


  • Add the int2byte function.
  • Add compatibility mappings for iterators over the keys, values, and items of a
    dictionary.
  • Fix six.MAXSIZE on platforms where sizeof(long) != sizeof(Py_ssize_t).
  • Issue 3: Add six.moves mappings for filter, map, and zip.

1.0


  • Reworked six into one .py file. This breaks imports. Please tell me if you
    are interested in an import compatibility layer.

1.0.0


  • Issue 2: u() on Python 2.x now resolves unicode escapes.
  • Expose an API for adding mappings to six.moves.

jira -> 1.0.10

1.0.10

requests -> 2.18.3

2.18.3

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

Improvements

  • Running $ python -m requests.help now includes the installed version of idna.

Bugfixes

  • Fixed issue where Requests would raise ConnectionError instead of
    SSLError when encoutering SSL problems when using urllib3 v1.22.

2.18.2

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

Bugfixes

  • requests.help no longer fails on Python 2.6 due to the absence of
    ssl.OPENSSL_VERSION_NUMBER.

Dependencies

  • We now support urllib3 v1.22.

2.18.1

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

Bugfixes

  • Fix an error in the packaging whereby the *.whl contained incorrect data that
    regressed the fix in v2.17.3.

2.18.0

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

Improvements

  • Response is now a context manager, so can be used directly in a with statement
    without first having to be wrapped by contextlib.closing().

Bugfixes

  • Resolve installation failure if multiprocessing is not available
  • Resolve tests crash if multiprocessing is not able to determine the number of CPU cores
  • Resolve error swallowing in utils set_environ generator

2.17.3

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

Improvements

  • Improved packages namespace identity support, for monkeypatching libraries.

2.17.2

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

Improvements

  • Improved packages namespace identity support, for monkeypatching libraries.

2.17.1

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

Improvements

  • Improved packages namespace identity support, for monkeypatching libraries.

2.17.0

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

Improvements

  • Removal of the 301 redirect cache. This improves thread-safety.

2.16.5

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

  • Improvements to $ python -m requests.help.

2.16.4

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

  • Introduction of the $ python -m requests.help command, for debugging with maintainers!

2.16.3

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

  • Further restored the requests.packages namespace for compatibility reasons.

2.16.2

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

  • Further restored the requests.packages namespace for compatibility reasons.

No code modification (noted below) should be neccessary any longer.

2.16.1

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

  • Restored the requests.packages namespace for compatibility reasons.
  • Bugfix for urllib3 version parsing.

Note: code that was written to import against the requests.packages
namespace previously will have to import code that rests at this module-level
now.

For example::

from requests.packages.urllib3.poolmanager import PoolManager

Will need to be re-written to be::

from requests.packages import urllib3
urllib3.poolmanager.PoolManager

Or, even better::

from urllib3.poolmanager import PoolManager

2.16.0

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

  • Unvendor ALL the things!

2.15.1

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

  • Everyone makes mistakes.

2.15.0

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

Improvements

  • Introduction of the Response.next property, for getting the next
    PreparedResponse from a redirect chain (when allow_redirects=False).
  • Internal refactoring of __version__ module.

Bugfixes

  • Restored once-optional parameter for requests.utils.get_environ_proxies().

2.14.2

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

Bugfixes

  • Changed a less-than to an equal-to and an or in the dependency markers to
    widen compatibility with older setuptools releases.

2.14.1

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

Bugfixes

  • Changed the dependency markers to widen compatibility with older pip
    releases.

2.14.0

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

Improvements

  • It is now possible to pass no_proxy as a key to the proxies
    dictionary to provide handling similar to the NO_PROXY environment
    variable.
  • When users provide invalid paths to certificate bundle files or directories
    Requests now raises IOError, rather than failing at the time of the HTTPS
    request with a fairly inscrutable certificate validation error.
  • The behavior of SessionRedirectMixin was slightly altered.
    resolve_redirects will now detect a redirect by calling
    get_redirect_target(response) instead of directly
    querying Response.is_redirect and Response.headers['location'].
    Advanced users will be able to process malformed redirects more easily.
  • Changed the internal calculation of elapsed request time to have higher
    resolution on Windows.
  • Added win_inet_pton as conditional dependency for the [socks] extra
    on Windows with Python 2.7.
  • Changed the proxy bypass implementation on Windows: the proxy bypass
    check doesn't use forward and reverse DNS requests anymore
  • URLs with schemes that begin with http but are not http or https
    no longer have their host parts forced to lowercase.

Bugfixes

  • Much improved handling of non-ASCII Location header values in redirects.
    Fewer UnicodeDecodeErrors are encountered on Python 2, and Python 3 now
    correctly understands that Latin-1 is unlikely to be the correct encoding.
  • If an attempt to seek file to find out its length fails, we now
    appropriately handle that by aborting our content-length calculations.
  • Restricted HTTPDigestAuth to only respond to auth challenges made on 4XX
    responses, rather than to all auth challenges.
  • Fixed some code that was firing DeprecationWarning on Python 3.6.
  • The dismayed person emoticon (/o\\) no longer has a big head. I'm sure
    this is what you were all worrying about most.

Miscellaneous

  • Updated bundled urllib3 to v1.21.1.
  • Updated bundled chardet to v3.0.2.
  • Updated bundled idna to v2.5.
  • Updated bundled certifi to 2017.4.17.

2.13.0

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

Features

  • Only load the idna library when we've determined we need it. This will
    save some memory for users.

Miscellaneous

  • Updated bundled urllib3 to 1.20.
  • Updated bundled idna to 2.2.

2.12.5

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

Bugfixes

  • Fixed an issue with JSON encoding detection, specifically detecting
    big-endian UTF-32 with BOM.

2.12.4

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

Bugfixes

  • Fixed regression from 2.12.2 where non-string types were rejected in the
    basic auth parameters. While support for this behaviour has been readded,
    the behaviour is deprecated and will be removed in the future.

2.12.3

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

Bugfixes

  • Fixed regression from v2.12.1 for URLs with schemes that begin with "http".
    These URLs have historically been processed as though they were HTTP-schemed
    URLs, and so have had parameters added. This was removed in v2.12.2 in an
    overzealous attempt to resolve problems with IDNA-encoding those URLs. This
    change was reverted: the other fixes for IDNA-encoding have been judged to
    be sufficient to return to the behaviour Requests had before v2.12.0.

2.12.2

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

Bugfixes

  • Fixed several issues with IDNA-encoding URLs that are technically invalid but
    which are widely accepted. Requests will now attempt to IDNA-encode a URL if
    it can but, if it fails, and the host contains only ASCII characters, it will
    be passed through optimistically. This will allow users to opt-in to using
    IDNA2003 themselves if they want to, and will also allow technically invalid
    but still common hostnames.
  • Fixed an issue where URLs with leading whitespace would raise
    InvalidSchema errors.
  • Fixed an issue where some URLs without the HTTP or HTTPS schemes would still
    have HTTP URL preparation applied to them.
  • Fixed an issue where Unicode strings could not be used in basic auth.
  • Fixed an issue encountered by some Requests plugins where constructing a
    Response object would cause Response.content to raise an
    AttributeError.

2.12.1

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

Bugfixes

  • Updated setuptools 'security' extra for the new PyOpenSSL backend in urllib3.

Miscellaneous

  • Updated bundled urllib3 to 1.19.1.

2.12.0

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

Improvements

  • Updated support for internationalized domain names from IDNA2003 to IDNA2008.
    This updated support is required for several forms of IDNs and is mandatory
    for .de domains.
  • Much improved heuristics for guessing content lengths: Requests will no
    longer read an entire StringIO into memory.
  • Much improved logic for recalculating Content-Length headers for
    PreparedRequest objects.
  • Improved tolerance for file-like objects that have no tell method but
    do have a seek method.
  • Anything that is a subclass of Mapping is now treated like a dictionary
    by the data= keyword argument.
  • Requests now tolerates empty passwords in proxy credentials, rather than
    stripping the credentials.
  • If a request is made with a file-like object as the body and that request is
    redirected with a 307 or 308 status code, Requests will now attempt to
    rewind the body object so it can be replayed.

Bugfixes

  • When calling response.close, the call to close will be propagated
    through to non-urllib3 backends.
  • Fixed issue where the ALL_PROXY environment variable would be preferred
    over scheme-specific variables like HTTP_PROXY.
  • Fixed issue where non-UTF8 reason phrases got severely mangled by falling
    back to decoding using ISO 8859-1 instead.
  • Fixed a bug where Requests would not correctly correlate cookies set when
    using custom Host headers if those Host headers did not use the native
    string type for the platform.

Miscellaneous

  • Updated bundled urllib3 to 1.19.
  • Updated bundled certifi certs to 2016.09.26.

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.

2.8.1

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

Bugfixes

  • Update certificate bundle to match certifi 2015.9.6.2's weak certificate
    bundle.
  • Fix a bug in 2.8.0 where requests would raise ConnectTimeout instead of
    ConnectionError
  • When using the PreparedRequest flow, requests will now correctly respect the
    json parameter. Broken in 2.8.0.
  • When using the PreparedRequest flow, requests will now correctly handle a
    Unicode-string method name on Python 2. Broken in 2.8.0.

2.8.0

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

Minor Improvements (Backwards Compatible)

  • Requests now supports per-host proxies. This allows the proxies
    dictionary to have entries of the form
    {'<scheme>://<hostname>': '<proxy>'}. Host-specific proxies will be used
    in preference to the previously-supported scheme-specific ones, but the
    previous syntax will continue to work.
  • Response.raise_for_status now prints the URL that failed as part of the
    exception message.
  • requests.utils.get_netrc_auth now takes an raise_errors kwarg,
    defaulting to False. When True, errors parsing .netrc files cause
    exceptions to be thrown.
  • Change to bundled projects import logic to make it easier to unbundle
    requests downstream.
  • Changed the default User-Agent string to avoid leaking data on Linux: now
    contains only the requests version.

Bugfixes

  • The json parameter to post() and friends will now only be used if
    neither data nor files are present, consistent with the
    documentation.
  • We now ignore empty fields in the NO_PROXY environment variable.
  • Fixed problem where httplib.BadStatusLine would get raised if combining
    stream=True with contextlib.closing.
  • Prevented bugs where we would attempt to return the same connection back to
    the connection pool twice when sending a Chunked body.
  • Miscellaneous minor internal changes.
  • Digest Auth support is now thread safe.

Updates

  • Updated urllib3 to 1.12.

2.7.0

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

This is the first release that follows our new release process. For more, see
our documentation <http://docs.python-requests.org/en/latest/community/release-process/>_.

Bugfixes

  • Updated urllib3 to 1.10.4, resolving several bugs involving chunked transfer
    encoding and response framing.

2.6.2

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

Bugfixes

  • Fix regression where compressed data that was sent as chunked data was not
    properly decompressed. (2561)

2.6.1

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

Bugfixes

  • Remove VendorAlias import machinery introduced in v2.5.2.
  • Simplify the PreparedRequest.prepare API: We no longer require the user to
    pass an empty list to the hooks keyword argument. (c.f. 2552)
  • Resolve redirects now receives and forwards all of the original arguments to
    the adapter. (2503)
  • Handle UnicodeDecodeErrors when trying to deal with a unicode URL that
    cannot be encoded in ASCII. (2540)
  • Populate the parsed path of the URI field when performing Digest
    Authentication. (2426)
  • Copy a PreparedRequest's CookieJar more reliably when it is not an instance
    of RequestsCookieJar. (2527)

2.6.0

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

Bugfixes

  • CVE-2015-2296: Fix handling of cookies on redirect. Previously a cookie
    without a host value set would use the hostname for the redirected URL
    exposing requests users to session fixation attacks and potentially cookie
    stealing. This was disclosed privately by Matthew Daley of
    BugFuzz <https://bugfuzz.com>_. This affects all versions of requests from
    v2.1.0 to v2.5.3 (inclusive on both ends).
  • Fix error when requests is an install_requires dependency and python setup.py test is run. (2462)
  • Fix error when urllib3 is unbundled and requests continues to use the
    vendored import location.
  • Include fixes to urllib3's header handling.
  • Requests' handling of unvendored dependencies is now more restrictive.

Features and Improvements

  • Support bytearrays when passed as parameters in the files argument.
    (2468)
  • Avoid data duplication when creating a request with str, bytes, or
    bytearray input to the files argument.

2.5.3

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

Bugfixes

2.5.2

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

Features and Improvements

  • Add sha256 fingerprint support. (shazow/urllib3540_)
  • Improve the performance of headers. (shazow/urllib3544_)

Bugfixes

  • Copy pip's import machinery. When downstream redistributors remove
    requests.packages.urllib3 the import machinery will continue to let those
    same symbols work. Example usage in requests' documentation and 3rd-party
    libraries relying on the vendored copies of urllib3 will work without having
    to fallback to the system urllib3.
  • Attempt to quote parts of the URL on redirect if unquoting and then quoting
    fails. (2356)
  • Fix filename type check for multipart form-data uploads. (2411)
  • Properly handle the case where a server issuing digest authentication
    challenges provides both auth and auth-int qop-values. (2408)
  • Fix a socket leak. (shazow/urllib3549_)
  • Fix multiple Set-Cookie headers properly. (shazow/urllib3534_)
  • Disable the built-in hostname verification. (shazow/urllib3526_)
  • Fix the behaviour of decoding an exhausted stream. (shazow/urllib3535_)

Security

  • Pulled in an updated cacert.pem.
  • Drop RC4 from the default cipher list. (shazow/urllib3551_)

.. _shazow/urllib3551: urllib3/urllib3#551
.. _shazow/urllib3549: urllib3/urllib3#549
.. _shazow/urllib3544: urllib3/urllib3#544
.. _shazow/urllib3540: urllib3/urllib3#540
.. _shazow/urllib3535: urllib3/urllib3#535
.. _shazow/urllib3534: urllib3/urllib3#534
.. _shazow/urllib3526: urllib3/urllib3#526

2.5.1

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

Behavioural Changes

  • Only catch HTTPErrors in raise_for_status (2382)

Bugfixes

  • Handle LocationParseError from urllib3 (2344)
  • Handle file-like object filenames that are not strings (2379)
  • Unbreak HTTPDigestAuth handler. Allow new nonces to be negotiated (2389)

2.5.0

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

Improvements

  • Allow usage of urllib3's Retry object with HTTPAdapters (2216)
  • The iter_lines method on a response now accepts a delimiter with which
    to split the content (2295)

Behavioural Changes

  • Add deprecation warnings to functions in requests.utils that will be removed
    in 3.0 (2309)
  • Sessions used by the functional API are always closed (2326)
  • Restrict requests to HTTP/1.1 and HTTP/1.0 (stop accepting HTTP/0.9) (2323)

Bugfixes

  • Only parse the URL once (2353)
  • Allow Content-Length header to always be overridden (2332)
  • Properly handle files in HTTPDigestAuth (2333)
  • Cap redirect_cache size to prevent memory abuse (2299)
  • Fix HTTPDigestAuth handling of redirects after authenticating successfully
    (2253)
  • Fix crash with custom method parameter to Session.request (2317)
  • Fix how Link headers are parsed using the regular expression library (2271)

Documentation

  • Add more references for interlinking (2348)
  • Update CSS for theme (2290)
  • Update width of buttons and sidebar (2289)
  • Replace references of Gittip with Gratipay (2282)
  • Add link to changelog in sidebar (2273)

2.4.3

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

Bugfixes

  • Unicode URL improvements for Python 2.
  • Re-order JSON param for backwards compat.
  • Automatically defrag authentication schemes from host/pass URIs. (2249 <https://github.com/requests/requests/issues/2249>_)

2.4.2

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

Improvements

  • FINALLY! Add json parameter for uploads! (2258 <https://github.com/requests/requests/pull/2258>_)
  • Support for bytestring URLs on Python 3.x (2238 <https://github.com/requests/requests/pull/2238>_)

Bugfixes

  • Avoid getting stuck in a loop (2244 <https://github.com/requests/requests/pull/2244>_)
  • Multiple calls to iter* fail with unhelpful error. (2240 <https://github.com/requests/requests/issues/2240>, 2241 <https://github.com/requests/requests/issues/2241>)

Documentation

  • Correct redirection introduction (2245 <https://github.com/requests/requests/pull/2245/>_)
  • Added example of how to send multiple files in one request. (2227 <https://github.com/requests/requests/pull/2227/>_)
  • Clarify how to pass a custom set of CAs (2248 <https://github.com/requests/requests/pull/2248/>_)

2.4.1

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

  • Now has a "security" package extras set, $ pip install requests[security]
  • Requests will now use Certifi if it is available.
  • Capture and re-raise urllib3 ProtocolError
  • Bugfix for responses that attempt to redirect to themselves forever (wtf?).

2.4.0

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

Behavioral Changes

  • Connection: keep-alive header is now sent automatically.

Improvements

  • Support for connect timeouts! Timeout now accepts a tuple (connect, read) which is used to set individual connect and read timeouts.
  • Allow copying of PreparedRequests without headers/cookies.
  • Updated bundled urllib3 version.
  • Refactored settings loading from environment -- new Session.merge_environment_settings.
  • Handle socket errors in iter_content.

2.3.0

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

API Changes

  • New Response property is_redirect, which is true when the
    library could have processed this response as a redirection

This change is Reviewable

@codecov-io
Copy link

codecov-io commented Aug 3, 2017

Codecov Report

Merging #60 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #60   +/-   ##
=======================================
  Coverage   55.34%   55.34%           
=======================================
  Files          10       10           
  Lines        1057     1057           
  Branches      245      245           
=======================================
  Hits          585      585           
  Misses        425      425           
  Partials       47       47

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fb450cc...8095c49. Read the comment docs.

@alisaifee alisaifee closed this Nov 23, 2020
@alisaifee alisaifee deleted the pyup-initial-update branch November 23, 2020 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants