Date: Mon, 28 Jan 2019 08:04:38 -0500 From: Steve Wills <steve@mouf.net> To: Yuri <yuri@rawbw.com>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r486676 - in head/devel: . py-prompt_toolkit2 Message-ID: <e01e9679-8196-bd5f-b331-9f7813158d18@mouf.net> In-Reply-To: <9e6b307c-9908-d13f-a9aa-324c1069f987@rawbw.com> References: <201812051434.wB5EYT7n010129@repo.freebsd.org> <9e6b307c-9908-d13f-a9aa-324c1069f987@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e01e9679-8196-bd5f-b331-9f7813158d18>