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

Dependency Updates (via pyup) #850

Merged
merged 1 commit into from
Apr 5, 2019
Merged

Dependency Updates (via pyup) #850

merged 1 commit into from
Apr 5, 2019

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Apr 5, 2019

This PR sets up pyup.io on this repo and updates all dependencies at once, in a single branch.

Subsequent pull requests will update one dependency at a time, each in their own branch. If you want to start with that right away, simply close this PR.

Update astroid from 2.0.4 to 2.2.5.

Changelog

2.2.0

============================
Release Date: 2019-02-27


* Fix a bug concerning inference of calls to numpy function that should not return Tuple or List instances.

Close PyCQA/pylint2436

* Fix a bug where a method, which is a lambda built from a function, is not inferred as ``BoundMethod``

Close PyCQA/pylint2594

* ``typed_ast`` gets installed for Python 3.7, meaning type comments can now work on 3.7.

* Fix a bug concerning inference of unary operators on numpy types.

Close PyCQA/pylint2436 (first part)

* Fix a crash with ``typing.NamedTuple`` and empty fields. Close PyCQA/pylint2745

* Add a proper ``strerror`` inference to the ``OSError`` exceptions.

Close PyCQA/pylint2553

* Support non-const nodes as values of Enum attributes.

Close 612

* Fix a crash in the ``enum`` brain tip caused by non-assign members in class definitions.

Close PyCQA/pylint2719

* ``brain_numpy`` returns an undefined type for ``numpy`` methods to avoid ``assignment-from-no-return``

Close PyCQA/pylint2694

* Fix a bug where a call to a function that has been previously called via
functools.partial was wrongly inferred

Close PyCQA/pylint2588

* Fix a recursion error caused by inferring the ``slice`` builtin.

Close PyCQA/pylint2667

* Remove the restriction that "old style classes" cannot have a MRO.

This does not make sense any longer given that we run against Python 3
code.
Close PyCQA/pylint2701

* Added more builtin exceptions attributes. Close 580

* Add a registry for builtin exception models. Close PyCQA/pylint1432

* Add brain tips for `http.client`. Close PyCQA/pylint2687

* Prevent crashing when processing ``enums`` with mixed single and double quotes.

Close PyCQA/pylint2676

* ``typing`` types have the `__args__` property. Close PyCQA/pylint2419

* Fix a bug where an Attribute used as a base class was triggering a crash

Close 626

* Added special support for `enum.IntFlag`

Close PyCQA/pylint2534

* Extend detection of data classes defined with attr

Close 628

* Fix typo in description for brain_attrs

2.1.0

============================
Release Date: 2018-11-25

* ``threading.Lock.acquire`` has the ``timeout`` parameter now.

  Close PyCQA/pylint2457

* Pass parameters by keyword name when inferring sequences.

  Close PyCQA/pylint2526

* Correct line numbering for f-strings for complex embedded expressions

  When a f-string contained a complex expression, such as an attribute access,
  we weren't cloning all the subtree of the f-string expression for attaching the correct
  line number. This problem is coming from the builtin AST parser which gives for the f-string
  and for its underlying elements the line number 1, but this is causing all sorts of bugs and
  problems in pylint, which expects correct line numbering.

  Close PyCQA/pylint2449

* Add support for `argparse.Namespace`

  Close PyCQA/pylint2413

* `async` functions are now inferred as `AsyncGenerator` when inferring their call result.

* Filter out ``Uninferable`` when inferring the call result result of a class with an uninferable ``__call__`` method.

  Close PyCQA/pylint2434

* Make compatible with AST changes in Python 3.8.

* Subscript inference (e.g. "`a[i]`") now pays attention to multiple inferred values for value
  (e.g. "`a`") and slice (e.g. "`i`")

  Close 614
Links

Update cffi from 1.11.5 to 1.12.2.

Changelog

1.12.1

=======

* CPython 3 on Windows: we again no longer compile with ``Py_LIMITED_API``
by default because such modules *still* cannot be used with virtualenv.
The problem is that it doesn't work in CPython <= 3.4, and for
technical reason we can't enable this flag automatically based on the
version of Python.

Like before, `Issue 350`_ mentions a workaround if you still want
the ``Py_LIMITED_API`` flag and *either* you are not concerned about
virtualenv *or* you are sure your module will not be used on CPython
<= 3.4: pass ``define_macros=[("Py_LIMITED_API", None)]`` to the
``ffibuilder.set_source()`` call.

1.12

=====

* `Direct support for pkg-config`__.

* ``ffi.from_buffer()`` takes a new optional *first* argument that gives
the array type of the result.  It also takes an optional keyword argument
``require_writable`` to refuse read-only Python buffers.

* ``ffi.new()``, ``ffi.gc()`` or ``ffi.from_buffer()`` cdata objects
can now be released at known times, either by using the ``with``
keyword or by calling the new ``ffi.release()``.

* Windows, CPython 3.x: cffi modules are linked with ``python3.dll``
again.  This makes them independant on the exact CPython version,
like they are on other platforms.  **It requires virtualenv 16.0.0.**

* Accept an expression like ``ffi.new("int[4]", p)`` if ``p`` is itself
another cdata ``int[4]``.

* CPython 2.x: ``ffi.dlopen()`` failed with non-ascii file names on Posix

* CPython: if a thread is started from C and then runs Python code (with
callbacks or with the embedding solution), then previous versions of
cffi would contain possible crashes and/or memory leaks.  Hopefully,
this has been fixed (see `issue 362`_).

* Support for ``ffi.cdef(..., pack=N)`` where N is a power of two.
Means to emulate ``pragma pack(N)`` on MSVC.  Also, the default on
Windows is now ``pack=8``, like on MSVC.  This might make a difference
in corner cases, although I can't think of one in the context of CFFI.
The old way ``ffi.cdef(..., packed=True)`` remains and is equivalent
to ``pack=1`` (saying e.g. that fields like ``int`` should be aligned
to 1 byte instead of 4).

.. __: cdef.htmlpkgconfig
.. _`issue 362`: https://bitbucket.org/cffi/cffi/issues/362/


Older Versions
==============
Links

Update configparser from 3.5.0 to 3.7.4.

Changelog

3.7.4

=====

* Project is now officially supported through
`Tidelift <https://tidelift.com/subscription/pkg/pypi-configparser?utm_source=pypi-configparser&utm_medium=readme>`_.

3.7.3

=====

* Issue 34: Temporarily degrade to use ASCII for author's name.

3.7.2

=====

3.7.1

=====

* Issue 30: Fixed issue on Python 2.x when future is present.

3.7.0

=====

* Merge functionality from Python 3.7.2. Now ConfigParser accepts bytes
paths as well as any
`PathLike <https://docs.python.org/3/library/os.htmlos.PathLike>`_
object, including those found in the `pathlib2 backport
<https://pypi.org/project/pathlib2/>`.

3.5.3

=====

* Issue 27: Reverted the limit on DeprecationWarning, as it had unintended
consequences.

3.5.2

=====

* Issue 23: Use environment markers to indicate the 'ordereddict' dependency
for Python 2.6.

* Issue 24: Limit DeprecationWarning when a filename is indicated as a
bytestring on Python 2. Now the warning is only emitted when py3kwarning
is indicated.

3.5.1

=====

* jaraco adopts the package.

* Moved hosting to GitHub.

* Issue 21: Updated ``backports`` namespace package to conform with other
packages sharing the namespace.
Links

Update cryptography from 2.4.2 to 2.6.1.

Changelog

2.6.1

~~~~~~~~~~~~~~~~~~

* Resolved an error in our build infrastructure that broke our Python3 wheels
for macOS and Linux.

.. _v2-6:

2.6

~~~~~~~~~~~~~~~~

* **BACKWARDS INCOMPATIBLE:** Removed
``cryptography.hazmat.primitives.asymmetric.utils.encode_rfc6979_signature``
and
``cryptography.hazmat.primitives.asymmetric.utils.decode_rfc6979_signature``,
which had been deprecated for nearly 4 years. Use
:func:`~cryptography.hazmat.primitives.asymmetric.utils.encode_dss_signature`
and
:func:`~cryptography.hazmat.primitives.asymmetric.utils.decode_dss_signature`
instead.
* **BACKWARDS INCOMPATIBLE**: Removed ``cryptography.x509.Certificate.serial``,
which had been deprecated for nearly 3 years. Use
:attr:`~cryptography.x509.Certificate.serial_number` instead.
* Updated Windows, macOS, and ``manylinux1`` wheels to be compiled with
OpenSSL 1.1.1b.
* Added support for :doc:`/hazmat/primitives/asymmetric/ed448` when using
OpenSSL 1.1.1b or newer.
* Added support for :doc:`/hazmat/primitives/asymmetric/ed25519` when using
OpenSSL 1.1.1b or newer.
* :func:`~cryptography.hazmat.primitives.serialization.load_ssh_public_key` can
now load ``ed25519`` public keys.
* Add support for easily mapping an object identifier to its elliptic curve
class via
:func:`~cryptography.hazmat.primitives.asymmetric.ec.get_curve_for_oid`.
* Add support for OpenSSL when compiled with the ``no-engine``
(``OPENSSL_NO_ENGINE``) flag.

.. _v2-5:

2.5

~~~~~~~~~~~~~~~~

* **BACKWARDS INCOMPATIBLE:** :term:`U-label` strings were deprecated in
version 2.1, but this version removes the default ``idna`` dependency as
well. If you still need this deprecated path please install cryptography
with the ``idna`` extra: ``pip install cryptography[idna]``.
* **BACKWARDS INCOMPATIBLE:** The minimum supported PyPy version is now 5.4.
* Numerous classes and functions have been updated to allow :term:`bytes-like`
types for keying material and passwords, including symmetric algorithms, AEAD
ciphers, KDFs, loading asymmetric keys, and one time password classes.
* Updated Windows, macOS, and ``manylinux1`` wheels to be compiled with
OpenSSL 1.1.1a.
* Added support for :class:`~cryptography.hazmat.primitives.hashes.SHA512_224`
and :class:`~cryptography.hazmat.primitives.hashes.SHA512_256` when using
OpenSSL 1.1.1.
* Added support for :class:`~cryptography.hazmat.primitives.hashes.SHA3_224`,
:class:`~cryptography.hazmat.primitives.hashes.SHA3_256`,
:class:`~cryptography.hazmat.primitives.hashes.SHA3_384`, and
:class:`~cryptography.hazmat.primitives.hashes.SHA3_512` when using OpenSSL
1.1.1.
* Added support for :doc:`/hazmat/primitives/asymmetric/x448` when using
OpenSSL 1.1.1.
* Added support for :class:`~cryptography.hazmat.primitives.hashes.SHAKE128`
and :class:`~cryptography.hazmat.primitives.hashes.SHAKE256` when using
OpenSSL 1.1.1.
* Added initial support for parsing PKCS12 files with
:func:`~cryptography.hazmat.primitives.serialization.pkcs12.load_key_and_certificates`.
* Added support for :class:`~cryptography.x509.IssuingDistributionPoint`.
* Added ``rfc4514_string()`` method to
:meth:`x509.Name <cryptography.x509.Name.rfc4514_string>`,
:meth:`x509.RelativeDistinguishedName
<cryptography.x509.RelativeDistinguishedName.rfc4514_string>`, and
:meth:`x509.NameAttribute <cryptography.x509.NameAttribute.rfc4514_string>`
to format the name or component an :rfc:`4514` Distinguished Name string.
* Added
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.from_encoded_point`,
which immediately checks if the point is on the curve and supports compressed
points. Deprecated the previous method
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicNumbers.from_encoded_point`.
* Added :attr:`~cryptography.x509.ocsp.OCSPResponse.signature_hash_algorithm`
to ``OCSPResponse``.
* Updated :doc:`/hazmat/primitives/asymmetric/x25519` support to allow
additional serialization methods. Calling
:meth:`~cryptography.hazmat.primitives.asymmetric.x25519.X25519PublicKey.public_bytes`
with no arguments has been deprecated.
* Added support for encoding compressed and uncompressed points via
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.public_bytes`. Deprecated the previous method
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicNumbers.encode_point`.


.. _v2-4-2:
Links

Update isort from 4.3.4 to 4.3.16.

Changelog

4.3.15

- Fixed a regression with handling streaming input from pipes (Issue 895)
- Fixed handling of \x0c whitespace character (Issue 811)
- Improved CLI documentation

4.3.14

- Fixed a regression with */directory/*.py style patterns

4.3.13

- Fixed the inability to accurately determine import section when a mix of conda and virtual environments are used.
- Fixed some output being printed even when --quiet mode is enabled.
- Fixed issue 890 interoperability with PyCharm by allowing case sensitive non type grouped sorting.
- Fixed issue 889 under some circumstances isort will incorrectly add a new line at the beginning of a file.
- Fixed issue 885 many files not being skipped according to set skip settings.
- Fixed issue 842 streaming encoding improvements.

4.3.12

- Fix error caused when virtual environment not detected

4.3.11

- Fixed issue 876: confused by symlinks pointing to virtualenv gives FIRSTPARTY not THIRDPARTY
- Fixed issue 873: current version skips every file on travis
- Additional caching to reduce performance regression introduced in 4.3.5

4.3.10

- Fixed Windows incompatibilities (Issue 835)
- Fixed relative import sorting bug (Issue 417)
- Fixed "no_lines_before" to also be respected from previous empty sections.
- Fixed slow-down introduced by finders mechanism by adding a LRU cache (issue 848)
- Fixed issue 842 default encoding not-set in Python2
- Restored Windows automated testing
- Added Mac automated testing

4.3.9

- Fixed a bug that led to an incompatibility with black: 831

4.3.8

- Fixed a bug that led to the recursive option not always been available from the command line.

4.3.7

- Expands the finder failsafe to occur on the creation of the finder objects.

4.3.6

- Fixes a fatal error that occurs if a single finder throws an exception. Important as we add more finders that utilize third party libraries.

4.3.5 - February 24, 2019 - last Python 2.7 Maintenance Release

This is the final Python 2.x release of isort, and includes the following major changes:

Potentially Interface Breaking:
- The `-r` option for removing imports has been renamed `-rm` to avoid accidental deletions and confusion with the `-rc` recursive option.
- `__init__.py` has been removed from the default ignore list. The default ignore list is now empty - with all items needing to be explicitly ignored.
- Isort will now by default ignore .tox / venv folders in an effort to be "safe". You can disable this behaviour by setting the "--unsafe" flag, this is separate from any skip or not skip rules you may have in place.
- Isort now allows for files missing closing newlines in whitespace check
- `distutils` support has been removed to simplify setup.py

New:
- Official Python 3.7 Compatibility.
- Support for using requirements files to auto determine third-paty section if pipreqs & requirementslib are installed.
- Added support for using pyproject.toml if toml is installed.
- Added support for XDG_HOME if appdirs is installed.
- An option has been added to enable ignoring trailing comments ('ignore_comments') defaulting to False.
- Added support to enable line length sorting for only specific sections
- Added a `correctly_sorted` property on the SortsImport to enable more intuitive programmatic checking.

Fixes:
- Improved black compatibility.
- Isort will no detect files in the CWD as first-party.
- Fixed several cases where '-ns' or 'not_skip' was being incorrectly ignored.
- Fixed sorting of relative path imports ('.', '..', '...', etc).
- Fixed bugs caused by a failure to maintain order when loading iterables from config files.
- Correctly handle CPython compiled imports and others that need EXT_SUFFIX to correctly identify.
- Fixed handling of Symbolic Links to follow them when walking the path.
- Fixed handling of relative known_paths.
- Fixed lack of access to all wrap modes from the CLI.
- Fixed handling of FIFO files.
- Fixed a bug that could result in multiple imports being inserted on the same line.
Links

Update pbr from 5.1.1 to 5.1.3.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

Update pluggy from 0.8.0 to 0.9.0.

Changelog

0.9.0

=========================

Features
--------

- `189 <https://github.com/pytest-dev/pluggy/issues/189>`_: ``PluginManager.load_setuptools_entrypoints`` now accepts a ``name`` parameter that when given will
load only entry points with that name.

``PluginManager.load_setuptools_entrypoints`` also now returns the number of plugins loaded by the
call, as opposed to the number of all plugins loaded by all calls to this method.



Bug Fixes
---------

- `187 <https://github.com/pytest-dev/pluggy/issues/187>`_: Fix internal ``varnames`` function for PyPy3.

0.8.1

=========================

Trivial/Internal Changes
------------------------

- `166 <https://github.com/pytest-dev/pluggy/issues/166>`_: Add ``stacklevel=2`` to implprefix warning so that the reported location of warning is the caller of PluginManager.
Links

Update py from 1.7.0 to 1.8.0.

Changelog

1.8.0

==================

- add ``"importlib"`` pyimport mode for python3.5+, allowing unimportable test suites
to contain identically named modules.

- fix ``LocalPath.as_cwd()`` not calling ``os.chdir()`` with ``None``, when
being invoked from a non-existing directory.
Links

Update pylint from 2.1.1 to 2.3.1.

Changelog

2.3.0

===========================

Release date: 2019-02-27

* Protect against `NonDeducibleTypeHierarchy` when calling semi-private `is_subtype`

`astroid.helpers.is_subtype` raises `NonDeducibleTypeHierarchy` when it cannot infer
the base classes of the given types, but that makes sense in its context given that
the method is mostly used to inform the inference process about the hierarchy of classes.
Doesn't make that much sense for ``pylint`` itself, which is why we're handling the
exception here, rather than in ``astroid``

Close PyCQA/astroid644

* Added a new command line option ``list-groups`` for listing all the check groups ``pylint`` knows about.

* Allow ``BaseException`` for emitting ``broad-except``, just like ``Exception``.

Close 2741

* Fixed a crash that occurred for ``bad-str-strip-call`` when ``strip()`` received ``None``

Close 2743

* Don't emit ``*-not-iterating`` checks for builtins consumed by ``itertools``

Close 2731

* Fix a crash caused by iterating over ``Uninferable`` in a string formatting check.

Close 2727

* Fixed false positives for ``no-self-argument`` and ``unsubscriptable-object`` when using ``__class_getitem__`` (new in Python 3.7)

Close 2416

* Support ``Ellipsis`` as a synonym for ``pass`` statements.

Close 2718

* ``fixme`` gets triggered only on comments.

Close 2321

* Fixed a false positive for ``unused-variable`` and ``nonlocal`` assignments

Close 2671

* Added ``load_configuration()`` hook for plugins

New optional hook for plugins is added: ``load_configuration()``.
This hook is executed after configuration is loaded to prevent
overwriting plugin specific configuration via user-based
configuration.

Close 2635

* Fix missing-raises-doc false positive (W9006)

Close 1502

* Exempt starred unpacking from ``*-not-iterating`` Python 3 checks

Close 2651

* Make ``compare-to-zero`` less zealous by checking against equality and identity

Close 2645

* Add ``no-else-raise`` warning (R1720)

Close 2558

* Exempt ``yield from`` from ``*-not-iterating`` Python 3 checks.

Close 2643

* Fix incorrect generation of ``no-else-return`` warnings (R1705)

Fixed issue where ``if`` statements with nested ``if`` statements
were incorrectly being flagged as ``no-else-return`` in some cases and
not being flagged as ``no-else-return`` in other cases.  Added tests
for verification and updated pylint source files to eliminate newly
exposed warnings.

* Fix false positive with `not-async-context-manager` caused by not understanding `contextlib.asynccontextmanager`

Close 2440

* Refactor ``bad-reversed-sequence`` to account for more objects that can define ``__reversed__``

One such object would be an enum class, for which ``__reversed__`` yields each individual enum.
As such, the check for ``bad-reversed-sequence`` needs to not differentiate between classes
and instances when it comes for checking of ``__reversed__`` presence.

Close 2598

* Added ``wrong-exception-operation``

Used when an operation is done against an exception, but the operation
is not valid for the exception in question. Usually emitted when having
binary operations between exceptions in except handlers.

Close 2494

* ``no-member`` is emitted for enums when they lack a member

Previously we weren't doing this because we detected a
``__getattr__`` implementation on the ``Enum`` class
(and this check is skipped for classes with ``__getattr__``),
but that is fine for Enums, given that they are inferred in a customised
way in astroid.

Close 2565

* Generalize ``chained-comparison``

Previous version incorrectly detects `a < b < c and b < d` and fails to
detect `a < b < c and c < d`.

* Avoid popping __main__ when using multiple jobs

Close 2689

* Add a new option 'check-str-concat-over-line-jumps' to check 'implicit-str-concat-in-sequence'

* Fixes for the new style logging format linter.

The number of arguments was not handled properly, leading to an always
successful check.

* Fix false positive ``not-callable`` for uninferable properties.

* Fix false positive ``useless-else-on-loop`` if the break is deep in the else
of an inner loop.

2.2.2

===========================

Release date: 2018-11-28

* Change the ``logging-format-style`` to use name identifier instead of their
corresponding Python identifiers

This is to prevent users having to think about escaping the default value for
``logging-format-style`` in the generated config file. Also our config parsing
utilities don't quite support escaped values when it comes to ``choices`` detection,
so this would have needed various hacks around that.

Closes 2614

2.2.1

===========================

Release date: 2018-11-27

* Fix a crash caused by `implicit-str-concat-in-sequence` and multi-bytes characters.

Closes 2610

2.2

=========================

Release date: 2018-11-25

* Consider ``range()`` objects for ``undefined-loop-variable`` leaking from iteration.

  Close 2533

* ``deprecated-method`` can use the attribute name for identifying a deprecated method

  Previously we were using the fully qualified name, which we still do, but the fully
  qualified name for some ``unittest`` deprecated aliases leads to a generic
  deprecation function. Instead on relying on that, we now also rely on the attribute
  name, which should solve some false positives.

  Close 1653
  Close 1946

* Fix compatibility with changes to stdlib tokenizer.

* ``pylint`` is less eager to consume the whole line for pragmas

  Close 2485

* Obtain the correct number of CPUs for virtualized or containerized environments.

  Close 2519

* Change ``unbalanced-tuple-unpacking`` back to a warning.

  It used to be a warning until a couple of years ago, after it was promoted to
  an error. But the check might be suggesting the wrong thing in some cases,
  for instance when checking against ``sys.argv`` which cannot be known at static
  analysis time. Given it might rely on potential unknown data, it's best to
  have it as a warning.

  Close 2522

* Remove ``enumerate`` usage suggestion when defining ``__iter__`` (C0200)

  Close 2477

* Emit ``too-many-starred-assignment`` only when the number of Starred nodes is per assignment elements

  Close 2513

* `try-except-raise` checker now handles multilevel inheritance hirerachy for exceptions correctly.

  Close 2484

* Add a new check, ``simplifiable-if-expression`` for expressions like ``True if cond else False``.

  Close 2487

* ``too-few-public-methods`` is not reported for ``typing.NamedTuple``

  Close 2459

* too-few-public-methods`` is not reported for dataclasses created with options.

  Close 2488

* Remove wrong modules from 'bad-python3-import'.

  Close 2453

* The ``json`` reporter prints an empty list when no messages are emitted

  Close 2446

* Add a new check, ``duplicate-string-formatting-argument``

  This new check is emitted whenever a duplicate string formatting argument
  is found.

  Close 497

* ``assignment-from-no-return`` is not emitted for coroutines.

  Close 1715

* Report format string type mismatches.

* ``consider-using-ternary`` and ``simplified-boolean-expression`` no longer emit for sequence based checks

  Close 2473

* Handle ``AstroidSyntaxError`` when trying to import a module.

  Close 2313

* Allow ``__module__`` to be redefined at a class level. Close 2451

* ``pylint`` used to emit a ``unused-variable`` error if unused import was found in the function. Now instead of
  ``unused-variable``, ``unused-import`` is emitted.

  Close 2421

* Handle asyncio.coroutine when looking for ``not-an-iterable`` check.

  Close 996

* The ``locally-enabled`` check is gone.

  Close 2442

* Infer decorated methods when looking for method-hidden

  Close 2369

* Pick the latest value from the inferred values when looking for ``raising-non-exception``

  Close 2431

* Extend the TYPE_CHECKING guard to TYPE_CHECKING name as well, not just the attribute

  Close 2411

* Ignore import x.y.z as z cases for checker `useless-import-alias`.

  Close 2309

* Fix false positive ``undefined-variable`` and ``used-before-assignment`` with nonlocal keyword usage.

  Close 2049

* Stop ``protected-access`` exception for missing class attributes

* Don't emit `assignment-from-no-return` for decorated function nodes

  Close 2385

* `unnecessary-pass` is now also emitted when a function or class contains only docstring and pass statement.

   In Python, stubbed functions often have a body that contains just a single `pass` statement,
   indicating that the function doesn't do anything. However, a stubbed function can also have just a
   docstring, and function with a docstring and no body also does nothing.

   Close 2208

* ``duplicate-argument-name`` is emitted for more than one duplicate argument per function

   Close 1712

* Allow double indentation levels for more distinguishable indentations

  Close 741

* Consider tuples in exception handler for ``try-except-raise``.
  Close 2389

* Fix astroid.ClassDef check in checkers.utils.is_subclass_of

* Fix wildcard imports being ignored by the import checker

* Fix external/internal distinction being broken in the import graph

* Fix wildcard import check not skipping `__init__.py`

  Close 2430

* Add new option to logging checker, ``logging_format_style``

* Fix --ignore-imports to understand multi-line imports

  Close 1422
  Close 2019

* Add a new check 'implicit-str-concat-in-sequence' to spot string concatenation inside lists, sets & tuples.

* ``literal-comparison`` is now emitted for 0 and 1 literals.
Links

Update pyyaml from 4.2b1 to 5.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

Update stevedore from 1.30.0 to 1.30.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

Update tox from 3.5.3 to 3.8.6.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

Update virtualenv from 16.1.0 to 16.4.3.

Changelog

16.4.1

--------------------

Bugfixes
^^^^^^^^

- Fix ``license()`` builtin by copying the ``LICENSE`` file into the virtualenv - by ``asottile``. (`1317 <https://github.com/pypa/virtualenv/issues/1317>`_)


Features
^^^^^^^^

- bump vendored pip to ``19.0.3`` and wheel to ``0.33.1`` (`1321 <https://github.com/pypa/virtualenv/issues/1321>`_)

16.4.0

--------------------

Bugfixes
^^^^^^^^

- fixes the scenario where the python base install is symlinked with relative symlinks (`490 <https://github.com/pypa/virtualenv/issues/490>`_)
- Use ``importlib`` over ``imp`` in ``virtualenv.py`` for ``python >= 3.4`` - by Anthony Sottile (`1293 <https://github.com/pypa/virtualenv/issues/1293>`_)
- Copy or link PyPy header files instead of include directory itself (`1302 <https://github.com/pypa/virtualenv/issues/1302>`_)
- Allow virtualenv creation with older pip not having ``config`` command
correspondingly disabling configuration related features (such as pip cert
setting) in this case. (`1303 <https://github.com/pypa/virtualenv/issues/1303>`_)


Features
^^^^^^^^

- upgrade to pip ``19.0.2`` and setuptools ``40.8.0`` (`1312 <https://github.com/pypa/virtualenv/issues/1312>`_)

16.3.0

--------------------

Bugfixes
^^^^^^^^

- Use ``importlib`` over deprecated ``imp` in ``distutils/__init__.py`` for python 3 - by Anthony Sottile (`955 <https://github.com/pypa/virtualenv/issues/955>`_)
- Preserve ``cert`` option defined in ``pip.conf`` or environment variable. (`1273 <https://github.com/pypa/virtualenv/issues/1273>`_)
- fixed a ``ResourceWarning: unclosed file`` in ``call_subprocess()`` - by Mickaël Schoentgen (`1277 <https://github.com/pypa/virtualenv/issues/1277>`_)
- pre-import some built-in modules in ``site.py`` on PyPy according to PyPy's ``site.py`` - by microdog (`1281 <https://github.com/pypa/virtualenv/issues/1281>`_)
- Copy files from ``sys.exec_prefix`` only if it is really different path than
used prefix, bugfix for 1270 (`1282 <https://github.com/pypa/virtualenv/issues/1282>`_)


Features
^^^^^^^^

- Enable virtualenv to be distributed as a ``zipapp`` or to be run as a
wheel with ``PYTHONPATH=virtualenv...any.whl python -mvirtualenv`` - by
Anthony Sottile (`1092 <https://github.com/pypa/virtualenv/issues/1092>`_)
- bump vendored pip from ``18.1`` to ``19.0.1`` (`1291 <https://github.com/pypa/virtualenv/issues/1291>`_)


Documentation
^^^^^^^^^^^^^

- discourage installation as ``root``, including ``sudo`` - by ``altendky`` (`1061 <https://github.com/pypa/virtualenv/issues/1061>`_)

16.2.0

--------------------

Bugfixes
^^^^^^^^

- ``copyfile`` handles relative symlinks and symlinks to symlinks, avoiding problems when Python was installed using ``stow`` or ``homebrew``. (`268 <https://github.com/pypa/virtualenv/issues/268>`_)
- Fix preserving of original path when using fish and a subshell. (`904 <https://github.com/pypa/virtualenv/issues/904>`_)
- Drop the source layout of the project, going back to how the source was laid out before ``16.1.0``. (`1241 <https://github.com/pypa/virtualenv/issues/1241>`_)
- Fix bootstrap script generation broken with ``16.0.0``. Support now both ``CPython``, ``pypy``, ``jython``. (`1244 <https://github.com/pypa/virtualenv/issues/1244>`_)
- ``lib64`` symlink is again relative (as was with ``< 16.1.0``). (`1248 <https://github.com/pypa/virtualenv/issues/1248>`_)


Features
^^^^^^^^

- ``fish`` version 3 support for the activation script. (`1275 <https://github.com/pypa/virtualenv/issues/1275>`_)
- ``powershell`` activator is no longer signed. (`816 <https://github.com/pypa/virtualenv/issues/816>`_)
- ``pyproject.toml`` with ``PEP-517`` and ``PEP-518`` is now provided. ``tox.ini`` is now packaged with the ``sdist``. Distributions repackaging the library should use ``tox -e py`` to run the test suite on the ``sdist``. (`909 <https://github.com/pypa/virtualenv/issues/909>`_)
- ``activate_this.py`` improvements: set ``VIRTUAL_ENV`` environment variable; ``pypy``, ``pypy3`` and ``jython`` support. (`1057 <https://github.com/pypa/virtualenv/issues/1057>`_)
- The `xonsh <http://xon.sh/index.html>`_ shell is now supported by generating the ``xon.sh`` activation script. (`1206 <https://github.com/pypa/virtualenv/issues/1206>`_)
- Support ``pip`` wheels with removed ``certifi's cacert.pem``. (`1252 <https://github.com/pypa/virtualenv/issues/1252>`_)
- Upgrade setuptools from ``40.5.0`` to ``40.6.3`` and wheel from ``0.32.2`` to ``0.32.3``. (`1257 <https://github.com/pypa/virtualenv/issues/1257>`_)
- ``powershell`` now also provides the ``pydoc`` function that uses the virtual environments ``pydoc``. (`1258 <https://github.com/pypa/virtualenv/issues/1258>`_)
- Migrate to a ``setup.cfg`` based build. Minimum ``setuptools`` required to build is ``setuptools >= 40.6.3``, this is automatically acquired for all PEP-518 builders (recommended), or acquired via the old ``setup_requires`` method otherwise. Move exclusively to a ``setuptools`` generated console entry point script, this now does make ``setuptools >= 18.0.0`` a runtime dependency (install requires). Source and issue tracker now is shown on PyPi (supplied as package metadata) beside the homepage. (`1259 <https://github.com/pypa/virtualenv/issues/1259>`_)


Deprecations (removal in next major release)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Using ``python setup.py test`` is now marked as deprecated and will be removed in next release. Use ``tox`` instead, always. (`909 <https://github.com/pypa/virtualenv/issues/909>`_)
- Using the project directly from the source layout is now deprecated. Going ahead people wanting to use the project without installing the virtualenv are encouraged to download the wheel from PyPi and extract it to access the ``virtualenv.py`` file. We'll be switching to a ``src`` layout with next release. (`1241 <https://github.com/pypa/virtualenv/issues/1241>`_)
- No longer support ``distutils`` build/installation, now ``setuptools >= 40.6.3`` is required. (`1259 <https://github.com/pypa/virtualenv/issues/1259>`_)


Documentation
^^^^^^^^^^^^^

- ``activate_this.py`` recommend ``exec(open(this_file).read(), {'__file__': this_file})`` as it works both on Python 2 and 3. (`1057 <https://github.com/pypa/virtualenv/issues/1057>`_)
- Clarify how this project relates to the standard libraries ``venv`` and when one would still want to use this tool. (`1086 <https://github.com/pypa/virtualenv/issues/1086>`_)
- Move to a ``towncrier`` generated changelog to avoid merge conflicts, generate draft changelog documentation. Prefix version string in changelog with ``v`` to make the hyperlinks stable. (`1234 <https://github.com/pypa/virtualenv/issues/1234>`_)
Links

Update wrapt from 1.10.11 to 1.11.1.

Changelog

1.11.1

---------------

**Bugs Fixed**

* Fixed memory leak in C extension variant of ``PartialCallableObjectProxy``
class introduced in 1.11.0, when it was being used to perform binding,
when a call of an instance method was made through the class type, and
the self object passed explicitly as first argument.

* The C extension variant of the ``PartialCallableObjectProxy`` class
introduced in 1.11.0, which is a version of ``functools.partial``
which correctly handles binding when applied to methods of classes,
couldn't be used when no positional arguments were supplied.

* When the C extension variant of ``PartialCallableObjectProxy`` was
used and multiple positional arguments were supplied, the first
argument would be replicated and used to all arguments, instead of
correct values, when the partial was called.

* When the C extension variant of ``PartialCallableObjectProxy`` was
used and keyword arguments were supplied, it would fail as was
incorrectly using the positional arguments where the keyword arguments
should have been used.

1.11.0

---------------

**Bugs Fixed**

* When using arithmetic operations through a proxy object, checks about
the types of arguments were not being performed correctly, which could
result in an exception being raised to indicate that a proxy object had
not been initialised when in fact the argument wasn't even an instance
of a proxy object.

Because an incorrect cast in C level code was being performed and
an attribute in memory checked on the basis of it being a type different
to what it actually was, technically it may have resulted in a process
crash if the size of the object was smaller than the type being casted
to.

* The ``__complex__()`` special method wasn't implemented and using
``complex()`` on a proxy object would give wrong results or fail.

* When using the C extension, if an exception was raised when using inplace
or, ie., ``|=``, the error condition wasn't being correctly propagated
back which would result in an exception showing up as wrong location
in subsequent code.

* Type of ``long`` was used instead of ``Py_hash_t`` for Python 3.3+. This
caused compiler warnings on Windows, which depending on what locale was
set to, would cause pip to fail when installing the package.

* If calling ``Class.instancemethod`` and passing ``self`` explicitly, the
ability to access ``__name__`` and ``__module__`` on the final bound
method were not preserved. This was due to a ``partial`` being used for
this special case, and it doesn't preserve introspection.

* Fixed typo in the getter property of ``ObjectProxy`` for accessing
``__annotations__``. Appeared that it was still working as would fall back
to using generic ``__getattr__()`` to access attribute on wrapped object.

**Features Changed**

* Dropped support for Python 2.6 and 3.3.

* If ``copy.copy()`` or ``copy.deepcopy()`` is used on an instance of the
``ObjectProxy`` class, a ``NotImplementedError`` exception is raised, with
a message indicating that the object proxy must implement the
``__copy__()`` or ``__deepcopy__()`` method. This is in place of the
default ``TypeError`` exception with message indicating a pickle error.

* If ``pickle.dump()`` or ``pickle.dumps()`` is used on an instance of the
``ObjectProxy`` class, a ``NotImplementedError`` exception is raised, with
a message indicating that the object proxy must implement the
``__reduce_ex__()`` method. This is in place of the default ``TypeError``
exception with message indicating a pickle error.
Links

Update certifi from 2018.11.29 to 2019.3.9.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

Update astroid from 2.0.4 to 2.2.5
Update cffi from 1.11.5 to 1.12.2
Update cffi from 1.11.5 to 1.12.2
Update configparser from 3.5.0 to 3.7.4
Update cryptography from 2.4.2 to 2.6.1
Update cryptography from 2.4.2 to 2.6.1
Update isort from 4.3.4 to 4.3.16
Update pbr from 5.1.1 to 5.1.3
Update pluggy from 0.8.0 to 0.9.0
Update py from 1.7.0 to 1.8.0
Update pylint from 2.1.1 to 2.3.1
Update pyyaml from 4.2b1 to 5.1
Update stevedore from 1.30.0 to 1.30.1
Update tox from 3.5.3 to 3.8.6
Update virtualenv from 16.1.0 to 16.4.3
Update wrapt from 1.10.11 to 1.11.1
Update certifi from 2018.11.29 to 2019.3.9

Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
@awwad
Copy link
Contributor

awwad commented Apr 5, 2019

Rebased: squashed into one commit and added sign-off.

I checked all the hashes produced and confirmed that I get the same hashes locally using pip-tools (when run in both Python2 and Python3).

@awwad awwad changed the title Initial Update Dependency Updates (via pyup) Apr 5, 2019
@awwad awwad merged commit e82ce35 into develop Apr 5, 2019
@awwad awwad deleted the pyup-initial-update branch May 2, 2019 16:52
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.

2 participants