Closed andrii-i closed 1 year ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
@conda-forge-admin, please rerender
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)Problem
Currently
main
branch of this feedstock repo has package namejupyter_scheduler
while 1.x branchjupyter-scheduler
.Github repo
jupyter-scheduler
says "This extension is composed of a Python package namedjupyter_scheduler
for the server extension and a NPM package named@jupyterlab/scheduler
for the frontend extension." and asks to usepip install jupyter_scheduler
to install the extension. It's not clear ifjupyter_scheduler
orjupyter-scheduler
is the name of the extension / package.Proposed solution
Use jupyter-scheduler as a Jupyter Scheduler package name, use
jupyter_scheduler
to refer to the server component. This would be in line with how package is named at PyPi website, how jupyter-ai package is named at conda-forge.This PR updates a
set name
in the recipe which will make 2.1.0 available at conda-forge underjupyter-scheduler
.Next steps after this PR is approved:
jupyter_scheduler
package as broken following steps outlined in the docsjupyter-scheduler
jupyter-scheduler
as a package name (for example, when providing pip install commands)