Adding catppuccin-jupyterlab

[xDazld]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

Catppuccin is a suite of pastel themes ported to a wide variety of programs (IDEs, browsers, desktops, etc.). This is the port for JupyterLab.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/catppuccin-jupyterlab) and found some lint.

Here's what I've got...

For recipes/catppuccin-jupyterlab:

• The home item is expected in the about section.

[conda-forge-webservices]

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 (recipes/catppuccin-jupyterlab) and found it was in an excellent condition.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/catppuccin-jupyterlab) and found some lint.

Here's what I've got...

For recipes/catppuccin-jupyterlab:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [33, 38]

[conda-forge-webservices]

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 (recipes/catppuccin-jupyterlab) and found it was in an excellent condition.

[xDazld]

@conda-forge-admin, please ping conda-forge/help-python

I think this is ready for initial review. My main question is with handling noarch python builds. Based on documentation for noarch, I would assume that there should only be one build running on Linux64, however CI is currently building on Linux, Mac, and Windows. Is that a limitation of staged-recipes behaving different from CI in the final feedstock, or did I make an error I am missing?

Additionally, the tests I am using are based off the ones catppuccin-jupyterlab uses in its GitHub Actions; However, that uses grep, which is unavailable on the Windows CI. To work around that, I currently am just skipping that test on Windows, but I am open to a better solution to that.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/help-python and so here I am doing that.