Danny Milosavljevic <dannym@scratchpost.org> writes:

> * gnu/packages/python.scm (python-pep8, python2-pep8):
>   Add replacement.
> ---
>  gnu/packages/python.scm | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 5b5287e..c6ec6d3 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -5645,6 +5645,7 @@ applications.")
>  (define-public python-pep8
>    (package
>      (name "python-pep8")
> +    (replacement python-pycodestyle)

This will graft python-pycodestyle in place of python-pep8. Are they
fully API compatible?

I think grafting is something that should be reserved for critical
problems affecting a large number of packages, e.g. security fixes for
central libraries. Since there are only 10 direct dependents of pep8
according to `guix refresh -l` (21 rebuilds in total), a "megapatch"
replacing all inputs should be okay.

We should probably also add a "superseded" property to the pep8 package
so any downstream users gets the message.