Hi, I really don't understand, how to properly create this deactivate hack due to reverse nature of dependency chain. py-ipython is a prerequisite for py-ipyparallel, but not vise versa. I think that the real root of this problem is the ugly shortcut variant named 'parallel', which creates circular dependency for old 'py-ipython +parallel' (was provided as attempt to simplify transition from ipython 3.x to ipython 4.x).
Note: old overbloated ipython 3.x was splitted into several packages (ipyparallel, notebook and etc.), and now old py-ipython port is functionally more or less equivalent to new meta-port named py-jupyter. On Sun, Aug 23, 2015 at 7:01 PM, Clemens Lang <[email protected]> wrote: > Hi, > > ----- On 21 Aug, 2015, at 22:42, [email protected] wrote: > > > [139620] trunk/dports/python > > Revision 139620 > > Author [email protected] > > Date 2015-08-21 13:42:53 -0700 (Fri, 21 Aug 2015) > > Log Message py-ipython: update to version 4.0.0 (#48580) > > Because this update moves the file > > /opt/local/Library/Frameworks/Python.framework/Versions/${python.branch}/bin/ipcluster > from py-ipython to py-ipyparallel, it leads to the following error > during the upgrade: > > ---> Activating py27-ipyparallel @4.0.2_0 > Error: Failed to activate py27-ipyparallel: Image error: > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/ipcluster > is being used by the active py27-ipython port. Please deactivate this port > first, or use 'port -f activate py27-ipyparallel' to force the activation. > Error: See > /opt/local/var/macports/logs/_opt_dports_python_py-ipyparallel/py27-ipyparallel/main.log > for details. > > You will have to add the deactivate hack to py27-ipyparallel. Follow > http://trac.macports.org/wiki/PortfileRecipes#deactivatehack, which > explains the details. > > -- > Clemens Lang >
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
