[MacPorts] #50513: py27-pep8: conflict with py27-pep8-157 on update

[MacPorts]

#50513: py27-pep8: conflict with py27-pep8-157 on update
----------------------------------+--------------------------------
  Reporter:  langlois@…           |      Owner:  macports-tickets@…
      Type:  defect               |     Status:  new
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:
Resolution:                       |   Keywords:
      Port:  py-pep8 py-pep8-157  |
----------------------------------+--------------------------------
Changes (by petr@…):

 * cc: eborisch@… (added)


Comment:

 I can confirm that port `py-pep8-157` was introduces to resolve an issue,
 regarding incompatibility with `py-flake8`, which remained unresolved
 upstream for quite some time. If pep 1.7.0 was finally released, this
 might now be fix and we could get back to one single port. Will look into
 this later.

 Anyway, the conflict between `py27-pep8` and `py27-pep8-157` is by design.
 It's actually the same package, just a different version. In order to
 minimize any conflicts to occur for users with an existing install base,
 in r141870 I replaces the hard `pep8` dependency with a path dependency.
 This way any of the two `pep8` ports should satisfy the dependency.
 However, apparently for some reason this does not work for you.

 I would suspect that some other port forces the installation of
 `py27-pep8-157` (py27-flake, is the only good candidate I could think of),
 this cases py27-pep8 to be deactivated. However, `py27-pep8` is part of
 the list of outdated ports. This is just a guess though, but if correct
 `py27-pep8` now should already be deactivated. Another `port upgrade
 outdated` would not consider `py27-pep8` and the upgrade will finish
 without error.

 I CC the maintainer of `py-spyder` as well.

-- 
Ticket URL: <https://trac.macports.org/ticket/50513#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X