[MacPorts] #69434: py311-plotly @5.15.0_0: wheel build fails with up-to-date `py311-jupyterlab`
MacPorts
noreply at macports.org
Sat Mar 2 15:54:53 UTC 2024
#69434: py311-plotly @5.15.0_0: wheel build fails with up-to-date
`py311-jupyterlab`
---------------------------+------------------------
Reporter: jmon12 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.9.1
Resolution: | Keywords: jupyterlab
Port: py311-plotly |
---------------------------+------------------------
Description changed by jmon12:
Old description:
> During a routine `port upgrade outdated`, the build of `py311-plotly`
> failed with the error:
> {{{
> ERROR Missing dependencies:
> jupyterlab~=3.0; python_version >= "3.6"
> }}}
>
> Digging around, I found out that [plotly doesn't support
> jupyterlab4](https://community.plotly.com/t/does-plotly-work-with-
> jupyterlab-4/76095). Luckily enough, I could downgrade jupyterlab and its
> related components (only jupyterlab is not enough) to a supported
> version. So in my case, I had to manually `port activate` the following
> ports:
> - `py311-jupyterlab @3.0.13_0` instead of `py311-jupyterlab @4.1.2_0`
> - `py311-jupyterlab_pygments @0.1.2_0` instead of
> `py311-jupyterlab_pygments @0.3.0_0`
> - `py311-jupyterlab_server @2.4.0_0` instead of `py311-jupyterlab_server
> @2.25.3_0`
>
> I'm not proficient enough to propose a proper solution to that issue, but
> is seems like there should be two separated ports for jupyterlab: `py-
> jupyterlab3` and `py-jupyterlab4`.
>
> With a proper guidance (point to a port with an analog issue), I would be
> glad to propose a long term solution.
New description:
During a routine `port upgrade outdated`, the build of `py311-plotly`
failed with the error:
{{{
ERROR Missing dependencies:
jupyterlab~=3.0; python_version >= "3.6"
}}}
Digging around, I found out that [plotly doesn't support
jupyterlab4](https://community.plotly.com/t/does-plotly-work-with-
jupyterlab-4/76095). Luckily enough, I could downgrade jupyterlab and its
related components (only jupyterlab is not enough) to a supported version.
So in my case, I had to manually `port activate` the following ports:
- `py311-jupyterlab @3.0.13_0` instead of `py311-jupyterlab @4.1.2_0`
- `py311-jupyterlab_pygments @0.1.2_0` instead of
`py311-jupyterlab_pygments @0.3.0_0`
- `py311-jupyterlab_server @2.4.0_0` instead of `py311-jupyterlab_server
@2.25.3_0`
- `py311-jupyter_server` instead of `py311-jupyter_server @2.12.5_0`
I'm not proficient enough to propose a proper solution to that issue, but
is seems like there should be two separated ports for jupyterlab: `py-
jupyterlab3` and `py-jupyterlab4`.
With a proper guidance (point to a port with an analog issue), I would be
glad to propose a long term solution.
--
--
Ticket URL: <https://trac.macports.org/ticket/69434#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list