Skip to content

README.rst: compatability => compatibility #5

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.

Sign up for GitHub

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

Open
msabramo wants to merge 1 commit into
base: master
Choose a base branch
from
Open

README.rst: compatability => compatibility #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ To obtain a signature object, pass the target function to the
For the details of the signature object, refer to the either the package of
standard library documentation.

Compatability
Compatibility
-------------

The ``funcsigs`` backport has been tested against:
Expand All @@ -41,10 +41,10 @@ The ``funcsigs`` backport has been tested against:

Continuous integration testing is provided by `Travis CI`_.

Under Python 2.x there is a compatability issue when a function is assigned to
Under Python 2.x there is a compatibility issue when a function is assigned to
the ``__wrapped__`` property of a class after it has been constructed.
Similiarily there under PyPy directly passing the ``__call__`` method of a
builtin is also a compatability issues. Otherwise the functionality is
builtin is also a compatibility issues. Otherwise the functionality is
believed to be uniform between both Python2 and Python3.

Issues
Expand Down