svn commit: r486676 - in head/devel: . py-prompt_toolkit2

Steve Wills steve at mouf.net
Mon Jan 28 13:04:59 UTC 2019


Hi,

On 1/21/19 5:18 PM, Yuri wrote:
> On 12/5/18 6:34 AM, Steve Wills wrote:

> This commit introduced the conflict that prevents some packages from
> being created:
> 
> pkg-static: py36-prompt_toolkit-1.0.15 conflicts with
> py36-prompt_toolkit2-2.0.7 (installs files into the same place).
> Problematic file:
> /usr/local/lib/python3.6/site-packages/prompt_toolkit/__init__.py

Is there something depending on both?

> PyPI only has prompt_toolkit-2.0.7
> (https://pypi.org/project/prompt_toolkit/) which means versions 1.X and
> 2.X should be compatible. If they are really incompatible, the upstream
> should create a new python package with a different prefix. In case they
> are supposed to be incompatible, this is a faulty release because it
> conflicts with the older version.

As far as I can tell, all upstream has done is document the incompatibility:

https://github.com/prompt-toolkit/python-prompt-toolkit#notice-prompt_toolkit-20

In my experience python module developers don't typically create
separate packages when breaking compatibility. They rely on the ability
for users to pin particular versions, and follow semantic versioning, so
incompatible changes can be made across major version changes.

Steve


More information about the svn-ports-all mailing list