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

Update sphinx-autodoc-typehints to 1.6.0 #15

Merged
merged 2 commits into from Jan 2, 2019

Conversation

pyup-bot
Copy link
Collaborator

This PR updates sphinx-autodoc-typehints from 1.3.0 to 1.6.0.

Changelog

1.6.0

=====

* Fixed ``TypeError`` when formatting annotations from a class that inherits from a concrete
generic type (report and tests by bpeake-illuscio)
* Added support for ``typing_extensions.Protocol`` (PR by Ian Good)
* Added support for ``typing.NewType`` (PR by George Leslie-Waksman)

1.5.2

=====

* Emit a warning instead of crashing when an unresolvable forward reference is encountered in type
annotations

1.5.1

=====

* Fixed escape characters in parameter default values getting lost during signature processing
* Replaced use of the ``config-inited`` event (which inadvertently required Sphinx 1.8) with the
``builder-inited`` event

1.5.0

=====

* The setting of the ``typing.TYPECHECKING`` flag is now configurable using the
``set_type_checking_flag`` option

1.4.0

=====

* The extension now sets ``typing.TYPECHECKING`` to ``True`` during setup to include conditional
imports which may be used in type annotations
* Fixed parameters with trailing underscores (PR by Daniel Knell)
* Fixed KeyError with private methods (PR by Benito Palacios Sánchez)
* Fixed deprecation warning about the use of formatargspec (PR by Y. Somda)
* The minimum Sphinx version is now v1.7.0

1.3.1

=====

* Fixed rendering of generic types outside the typing module (thanks to Tim Poterba for the PR)
Links

@sjoerdk sjoerdk merged commit 2147a35 into master Jan 2, 2019
@sjoerdk sjoerdk deleted the pyup-update-sphinx-autodoc-typehints-1.3.0-to-1.6.0 branch January 30, 2020 14:27
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.

None yet

2 participants