Add shared-memory-dict

[maxb2]

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.

[conda-forge-linter]

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/shared-memory-dict) and found some lint.

Here's what I've got...

For recipes/shared-memory-dict:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'test', 'outputs', 'about', 'extra'].

[maxb2]

I'm willing to be listed as a maintainer

[conda-forge-linter]

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/shared-memory-dict) and found it was in an excellent condition.

[maxb2]

@conda-forge/help-python, ready for review!

[maxb2]

@conda-forge/staged-recipes, ready for review!

[conda-forge-linter]

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/shared-memory-dict) and found some lint.

Here's what I've got...

For recipes/shared-memory-dict:

• requirements: run: aiocache>=0.11.1,<0.12.0 must contain a space between the name and the pin, i.e. aiocache >=0.11.1,<0.12.0
• requirements: run: aiocache>=0.11.1,<0.12.0 must contain a space between the name and the pin, i.e. aiocache >=0.11.1,<0.12.0
• requirements: run: django>=3.0.8,<4.0.0 must contain a space between the name and the pin, i.e. django >=3.0.8,<4.0.0
• requirements: run: django>=3.0.8,<4.0.0 must contain a space between the name and the pin, i.e. django >=3.0.8,<4.0.0

[conda-forge-linter]

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/shared-memory-dict) and found it was in an excellent condition.

[conda-forge-linter]

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/shared-memory-dict) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/shared-memory-dict:

• It looks like the 'shared-memory-dict-all' output doesn't have any tests.

[conda-forge-linter]

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/shared-memory-dict) and found it was in an excellent condition.

[conda-forge-linter]

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/shared-memory-dict) and found some lint.

Here's what I've got...

For recipes/shared-memory-dict:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'requirements', 'test', 'outputs', 'about', 'extra'].

[conda-forge-linter]

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/shared-memory-dict) and found it was in an excellent condition.

[maxb2]

@BastianZim, I updated the recipe to follow sagemaker-inference-toolkit-feedstock like you suggested, but the import test in subsequent packages keeps failing. I don't know what else to try.

[BastianZim]

I'm currently on my phone but I'll have a look in an hour or so.

[BastianZim]

I can't see the error either but let's make sure that everything is in order and then I can try tracking it down.

[BastianZim]

I have added two small comments.

For the overall problem: I don't know unfortunately what is causing it but one thing I noticed in the logs is that pip installs the build tools (poetry etc) since they are not specified here. Upstream doesn't do that either though so I would first recommend asking them to add the build tools to their pyproject.toml.

You can also add --no-index to the build script which will maybe make it fail sooner.

Unfortunately, multi-output scripts are very finicky, so the error might be somewhere else.

@ocefpaf Have you seen this before and maybe have an idea?

[maxb2]

For the overall problem: I don't know unfortunately what is causing it but one thing I noticed in the logs is that pip installs the build tools (poetry etc) since they are not specified here. Upstream doesn't do that either though so I would first recommend asking them to add the build tools to their pyproject.toml.

Upstream does have poetry set as the build backend, but it is using the old way to do it. I submitted a PR to update it.

[BastianZim]

Ahh true — must've missed that. Please add poetry to host then.

[carterbox]

Needed to add all of the special pip args that are set automatically in the top package.

[maxb2]

Thanks for all the help getting this merged!